Cumulus Support

This may be a known thing as I haven't looked for a while as things going so well. I've just noticed that with an applied correction multiplier in calibration for rainfall, the daily rainfall bar graph isn't allowing for this and plots the original value. I am running what is now a fairly old version of Cumulus so has this been picked up before?
Dave

The daily rain graph is plotted from the rain total values in dayfile.txt, so if the graph doesn't reflect the multiplier that you've been using, then the values in dayfile.txt won't have it either. I don't know if/when it changed, but looking at the current code it looks like it correctly writes the calibrated value to dayfile.txt.

I don't remember having changed it, and I can't work out what the code would have looked like before to have managed to write the uncalibrated value. Also, the value displayed in 'today' on the Cumulus main screen is the same as the value that's written to dayfile.txt at the end of the day, so presumably that's also displaying the uncalibrated value?

Hi Steve - dayfile.txt for 12th has rainfall total as 9.0. Trend graph shows 9.0. factor is 1.3x atm and has been for sometime. In "Yesterday" page yesterday's rain is showing as 11.7mm which is = to 9.0x1.3. You can see this (before midnight) by using link to my website. Interesting.

Thanks - so it looks like there was indeed a bug where it wrote the uncalibrated value to the dayfile, which I have (hopefully) fixed at some point.

I guess it's about time I did an update. You know what they say - if it ain't broke don't fix it!
Cheers, Dave

I note the same problem as Dave. My rainfall using a calibration of 1.11 (don't ask) was 5.2 mm yesterday but shows up as 4.7mm on the rainfall histogram. I have Cumulus version 1.8.6 build 804 which otherwise works superbly.

Cheers,
Chris

dionaea wrote:I have Cumulus version 1.8.6 build 804

All I can suggest is that you update to the latest version - preferably the 1.8.8 beta. The current code for calibrated rainfall looks OK to me. And if it isn't, then any fix would be to 1.8.8 anyway.

FYI upgrade to 1.8.8 has indeed fixed it.
Cheers, Dave

dc1500 wrote:FYI upgrade to 1.8.8 has indeed fixed it.

Ah, good; it seems I did fix it at some point but forgot to note it in the change log.