Just installed 961 and noticed some wrong values in my all time records.
After "OK"ing the all time records editor I got the error in the subject and cumulus closed down - it was because there was an all time record that was blank (not one of the ones I had corrected).
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
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
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
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
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
'' is not a valid floating point value (build 961)
-
steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: '' is not a valid floating point value (build 961)
Did the message not tell you about the cumulus.elf file? There should be one in your Cumulus folder. Which was the blank all-time record? Is it still blank?
Steve
-
Greebo
- Posts: 40
- Joined: Sat 14 Feb 2009 7:03 am
- Weather Station: La Crosse WS-2355
- Operating System: Windows 7
- Location: NSW, Australia
Re: '' is not a valid floating point value (build 961)
yes it did... but I didn't pay that much attention the first time... my bad!File attached....
High Hourly Rain and Low Wind Chill are both blank.
I set them to zero and it saves ok but they remain blank when I go back into the editor again.
You do not have the required permissions to view the files attached to this post.
-
Greebo
- Posts: 40
- Joined: Sat 14 Feb 2009 7:03 am
- Weather Station: La Crosse WS-2355
- Operating System: Windows 7
- Location: NSW, Australia
Re: '' is not a valid floating point value (build 961)
I just put values in those fields and they've stuck (I've only just added the rain guage so the rain figures should all be zero at the moment).
If any of the values are set to zero, the dialog closes ok but when it opens, the zero values appear as blanks and wont allow the editor to close without crashing.
If any of the values are set to zero, the dialog closes ok but when it opens, the zero values appear as blanks and wont allow the editor to close without crashing.
-
steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: '' is not a valid floating point value (build 961)
I don't really understand how this has happened; it's not even as if those two are new items added recently, they've been in the all-time records for a long time. All I can suggest is that you stop Cumulus and edit alltime.ini to do the corrections, and then see if it's OK after that. If you attach your alltime.ini and alltimelog.txt files here before you do the edit, I'll see if I can work out what went wrong.
Steve
-
Greebo
- Posts: 40
- Joined: Sat 14 Feb 2009 7:03 am
- Weather Station: La Crosse WS-2355
- Operating System: Windows 7
- Location: NSW, Australia
Re: '' is not a valid floating point value (build 961)
High hourly rain is sorted now but I still have a problem with wind chill - see the other thread I posted in this morning.
I've just done some more experimenting... I think it might be that if ANY value in the alltime records editor is 0.0, reopening the editor will leave those values as blank. As unlikely as it might sound, I think if I had a minimum temp of exactly 0 degrees I would have the issue in the all time record editor for minimum temperature.
I tried by setting my all time minimum temp to 0 or 0.0 and both caused the editor to show "" when I reopened it.
Oddly enough, the 0 minimum temp didn't make it into my alltime.ini file and when I restarted Cumulus it was back to 3.9 again.
I've just done some more experimenting... I think it might be that if ANY value in the alltime records editor is 0.0, reopening the editor will leave those values as blank. As unlikely as it might sound, I think if I had a minimum temp of exactly 0 degrees I would have the issue in the all time record editor for minimum temperature.
I tried by setting my all time minimum temp to 0 or 0.0 and both caused the editor to show "" when I reopened it.
Oddly enough, the 0 minimum temp didn't make it into my alltime.ini file and when I restarted Cumulus it was back to 3.9 again.
-
steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: '' is not a valid floating point value (build 961)
Ah, that's a possibility. That may be an aspect of this new editor that I was unaware of - I'll investigate.Greebo wrote:I've just done some more experimenting... I think it might be that if ANY value in the alltime records editor is 0.0, reopening the editor will leave those values as blank.
Steve