Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Topics about the Beta trials up to Build 3043, the last build by Cumulus's founder Steve Loft. It was by this time way out of Beta but Steve wanted to keep it that way until he made a decision on his and Cumulus's future.
I remember talking about this before, but I can't seem to find where it was?!
My High daily temp range record broke today, somewhere around 3pm. I thought CMX might have set <#newrecord> to 1 at some point, or even after the midnight rollover? I remember this working OK last year, as my station was still fairly new, the daily temp range record was broken on several occasions, and the light flashed on my webpage, but not any more. I apologise for bringing this up again.
It's in the "new record? Post here" thread ( which I found by looking through your posting history from your profile page). On a mobile device at the moment and can't link.
I'm still confused by it though. I did some digging on a weather forum that I post at, and I made a post back in December last year, about my minimum daily range record being broken, and the light flashing on my webpage. And i'm fairly positive that the light used to flash when the high range was broken too?
Just found the all time records log: 2017-08-28 00:00 16.889 "High daily temp range" 2017-04-08 00:00 16.500
Would that not constitute <#newrecord> 1 at the midnight update?
I'll have to look at the code when I get chance, to see when it resets the flag compared to when it does the high/low range determination. But given the time stamp in the log, and my previous explanation, I wouldn't expect it be showing on the 29th at all. Note also that as I said previously, the way it works currently is a hack (as there is no proper mechanism for resetting the flags).
I know there haven't been a huge number of new versions of MX in recent times, but there have been some and it's quite possible that I spotted an inconsistency and changed it. A time of 23:00 is clearly nonsense for this statistic.
