| [04:40:28] | * JustTB has quit (Ping timeout: 256 seconds) |
| [06:10:36] | * JustTB has joined #farmos |
| [07:55:50] | <skipper_is[m]> | The weight report generates some odd results... The daily live weight gain average compares it to the last average weight. So as an example: |
| [07:55:50] | <skipper_is[m]> | I weigh 10 kids on 1st of April, and I weigh the last to be born on the 1st of may. They're all 5kg at birth for this example. |
| [07:55:50] | <skipper_is[m]> | I then go and weigh them all one the 1st of June, the average weight for 11 kids is 20kg. The average daily live weight gain seems to calculate from the 1st May's 5kg to the 1st June's 20kg, so the average daily live weight gain comes out at .48kg, whereas in actual fact it is far lower, more like .24kg. |
| [08:06:24] | <mstenta[m]> | skipper_is: can you open a github issue and copy this into the description? |
| [08:23:08] | * JustTB has quit (Quit: Leaving.) |
| [08:24:55] | * JustTB has joined #farmos |
| [10:50:54] | <paul121[m]> | skipper_is: I think I see what's happening. The weight report assumes that all animals (or a random selection of animals from a herd/group) are all weighed on the same day, and thus weight observations on any day is an "accurate" representation of the entire group |
| [10:52:14] | <paul121[m]> | That assumption is OK for the initial use case of that module - but you're right, this should be expanded on! |
| [10:53:54] | <paul121[m]> | There's some thinking that needs to be done there... maybe group all weights within a window (15 days, 1 month) to ONE "average" calculation. Am I thinking right? |
| [10:54:54] | <paul121[m]> | or trying to be able to detect when "individual" weight observations are made and handle another way... hmmm |
| [10:55:02] | <paul121[m]> | please do create an issue! |
| [12:31:13] | * JustTB has quit (Quit: Leaving.) |
| [14:31:55] | * JustTB has joined #farmos |
| [15:22:23] | * IPGreenly has quit (Quit: Leaving) |