Small bug in NOAA annual report?

[chrisecurtis]

I have noticed that on my system, the NOAA annual report is recording the "min<=0" days correctly but the total at the bottom of the column only shows the total for January, not for the whole the year to date. See here: http://weather.curtisfamily.org.uk/NOAA ... hp?yr=2016

Strangely, the other things at the base of the columns (max, mins and totals) seem to be working correctly. The previous year's seems completely correct, but this was generated by previous version of cumulus.

Not serious, but I wonder if it is a bug or whether I have something set up wrongly. Everything else seems to be working fine.

Thanks

[PaulMy]

It looks correct to me. Are you referring to the word "Jan" on the summary line for Temperature?

I believe that refers to the month when the lowest temperature occurred. Yours appear to be only in the month of January and in mine I have it in Dec Jan or Feb depending on the year.

Paul

[mcrossley]

Mine is the same, it does look like it started going wrong with MX. 2014 is correct, 2015 and 2016 are both wrong.

[PaulMy]

I've redone the math, and for both of you 2015 and 2016 seems to be incorrect. Mine is correct for all years but I am still using Cumulus1 and I missed the CumulusMX topic.

Paul

[steve]

Yes, it's a bug. Fixed in next build.

[chrisecurtis]

Thank you.

[Werk_AG]

Regarding to NOAA reports:

This is from Monthly Climatological Summary with Cumulus 1:
Days of Rain: 5 (>= 0,2 mm) 2 (>= 2,0 mm) 0 (>= 20,0 mm)

and this is with Cumulus MX:
Days of Rain: 5 (>= 2,0 mm) 2 (>= 2,0 mm) 0 (>= 20,0 mm)

Something wrong with my system, or perhaps a bug?
I'm running Cumulus MX build 3038

[steve]

What have you got for "Rain comparison 1" in the NOAA settings? Did you perhaps not change the comma to a decimal point in Cumulus.ini, if you used the file from Cumulus 1 with MX? The figure "0,2" from a Cumulus 1 ini file will probably get read as "02" in MX unless the comma is changed, as MX doesn't use commas in ini files.

[mcrossley]

My 2016 report is now correct with b3038, I have manually corrected the 2015 report.