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

Historic charts: Dew point data problems prior to v1.9.2 beta build

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
User avatar
gerardwood
Posts: 26
Joined: Tue 17 Aug 2010 7:26 am
Weather Station: Davis Vantage PRO 2
Operating System: Windows 10 Pro
Location: Musbury, nr Axminster, Devon
Contact:

Historic charts: Dew point data problems prior to v1.9.2 beta build

Post by gerardwood »

I'm having a problem with the creation of alldailytempdata.json - specifically, for max/min dew point data for dayfile.txt entries created prior to v1.9.2 beta (which is the point at which dew point data was added). For me, this changeover occurred on 2/2/2011.

I have 'fixed' my dayfile.txt to have the correct number of 'columns' (i.e. additional commas at the end of each data row), but this doesn't solve the problem.

What happens is this:
  • "maxDew" appears to have duplicated null entries for each day, but with no comma separating the two, creating invalid JSON. What is more likely to be happening is that the max and min values are both being output together:
    "maxDew":[[1280880000000,null][1280880000000,null],[1280966400000,null][1280966400000,null], ...]
  • "minDew" has no entries for corresponding each day, again creating invalid JSON:
    "minDew":[,,,,,,,,,,,,,,,,,, ...]
Removing these two rogue areas manually from alldailytempdata.json and reuploading 'solves' the problem, but I don't want to be doing this every morning!

I've attached my dayfile.txt and today's alldailytempdata.json (before the manual fix).

If there's a 'fix' I can make to my dayfile.txt (which doesn't involve inventing fake data), I'd be happy to hear about it!

Thanks,
Gerard.
You do not have the required permissions to view the files attached to this post.
User avatar
mcrossley
Posts: 14388
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: Historic charts: Dew point data problems prior to v1.9.2 beta build

Post by mcrossley »

Thanks for the report - it is a problem in Cumulus that I will fix for the next release.
Post Reply