Hi Guys,
On my system the following tags do not match up:
[actual_rain0_total_mm] = 27.2
[month1_rain0_total_mm] = 27.40
[year1_rain0_total_mm] 27.40
Had a look at a few website of members here no else seems to have this problem from what I can tell.
Is there any way I can manually fix it, as a recompute did not do anything.
I thought of manually adding a rain record to the raw file and recompute but surely that will add to all the values leaving the same result!
Mark
[actual_rain0_total_mm] does not match other tags
Moderator: Mattk
Re: [actual_rain0_total_mm] does not match other tags
OK done a bit more checking because I assumed that the problem happened when MH was offline whilst I made a new card up, and then when I plugged it back in it got the missing data from the davis logger.
So today the values are:
[actual_rain0_total_mm] 27.4
[month1_rain0_total_mm] 27.60
[year1_rain0_total_mm] 27.60
The VP2 console reports 27.4
And last entry in raw file is: 20120117085148 rain0 0 0 274
So 27.4 is the correct value. Not 27.6
I'm assuming that:
[year1_rain0_total_mm] comes form hist-year1,
[month1_rain0_total_mm] comes from hist-month1
Both these have the wrong value of 27.60 for rain0
So my question is; that if I stop logging and amend these values that restart logging, will this correct the difference in the values?
Will that stay corrected even if I do a recompute?
So today the values are:
[actual_rain0_total_mm] 27.4
[month1_rain0_total_mm] 27.60
[year1_rain0_total_mm] 27.60
The VP2 console reports 27.4
And last entry in raw file is: 20120117085148 rain0 0 0 274
So 27.4 is the correct value. Not 27.6
I'm assuming that:
[year1_rain0_total_mm] comes form hist-year1,
[month1_rain0_total_mm] comes from hist-month1
Both these have the wrong value of 27.60 for rain0
So my question is; that if I stop logging and amend these values that restart logging, will this correct the difference in the values?
Will that stay corrected even if I do a recompute?
Re: [actual_rain0_total_mm] does not match other tags
you can adjust it by setting an offset via calibration on sensor pages. But .2 mm is nothing, so I can hardly see that you have any true evidence to do that 
