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

Records

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
Cambium
Posts: 274
Joined: Wed 03 Aug 2011 11:19 pm
Weather Station: ProWeatherTP3000
Operating System: Windows10
Location: Coastal CT, USA
Contact:

Records

Post by Cambium »

Hi Guys. Hope you all been well.

What is the best way to change an error in the "Records".

I went back into the log file and corrected it but curious how do I get the new record to read.

For example: Record Max high showed 136.5° Feb, 20 2019. I Fixed it in the Feb 2019 log but how do I get the program toautomatically detect the new record max?

Thank You
freddie
Posts: 2870
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 24.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: Records

Post by freddie »

Use the records editors. They are accessed from the "edit" menu on the MX interface.
Freddie
Image
Cambium
Posts: 274
Joined: Wed 03 Aug 2011 11:19 pm
Weather Station: ProWeatherTP3000
Operating System: Windows10
Location: Coastal CT, USA
Contact:

Re: Records

Post by Cambium »

freddie wrote: Sun 05 Feb 2023 1:30 pm Use the records editors. They are accessed from the "edit" menu on the MX interface.
Thats only good if you know the new record. How do you go about retrieving it automatically? I tried the Fetch Monthly Log but didnt work
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: Records

Post by mcrossley »

Cambium wrote: Sun 05 Feb 2023 3:38 pm [I tried the Fetch Monthly Log but didn't work
That probably means you have a problem with the format in the log file. Please look in your latest MXdiags file, it should tell you the line number in the file to look at.
Cambium
Posts: 274
Joined: Wed 03 Aug 2011 11:19 pm
Weather Station: ProWeatherTP3000
Operating System: Windows10
Location: Coastal CT, USA
Contact:

Re: Records

Post by Cambium »

mcrossley wrote: Sun 05 Feb 2023 3:58 pm
Cambium wrote: Sun 05 Feb 2023 3:38 pm [I tried the Fetch Monthly Log but didn't work
That probably means you have a problem with the format in the log file. Please look in your latest MXdiags file, it should tell you the line number in the file to look at.
Yup, you're right, I see errors posted. Thanks! Let me try to tackle this, there's more than 1.
Cambium
Posts: 274
Joined: Wed 03 Aug 2011 11:19 pm
Weather Station: ProWeatherTP3000
Operating System: Windows10
Location: Coastal CT, USA
Contact:

Re: Records

Post by Cambium »

mcrossley wrote: Sun 05 Feb 2023 3:58 pm That probably means you have a problem with the format in the log file. Please look in your latest MXdiags file, it should tell you the line number in the file to look at.

I deleted the lines that were showing up as errors but the records are still not updating. I attached the DIAGS file and the Log files for which the errors were being mentioned

20230205-104549.txt
Oct14log.txt
Feb22log.txt
Dec12log.txt
Feb19log.txt

Here's a look at the records, Feb 2019 seems like when things started going haywire. But an example is I fixed the Feb 20, 2019 max temp file in the log and its still not picking up the next record max anywhere.
SS1.jpg
You do not have the required permissions to view the files attached to this post.
freddie
Posts: 2870
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 24.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: Records

Post by freddie »

Just taking the High temp record - you appear to have a large value in your Feb 2017 logfile too.
Freddie
Image
Cambium
Posts: 274
Joined: Wed 03 Aug 2011 11:19 pm
Weather Station: ProWeatherTP3000
Operating System: Windows10
Location: Coastal CT, USA
Contact:

Re: Records

Post by Cambium »

freddie wrote: Sun 05 Feb 2023 5:35 pm Just taking the High temp record - you appear to have a large value in your Feb 2017 logfile too.
Is it worth it for me to just copy and past all the log files and just sort by each column to see what the record is and just manually edit it?
Would take time just to copy and paste.
flort
Posts: 248
Joined: Thu 17 Dec 2020 9:06 am
Weather Station: Davis Vantage Vue
Operating System: Raspbian GNU/Linux 10 (buster)
Location: Tin Can Bay, Queensland, Australia

Re: Records

Post by flort »

I think your best course of action is to correct your log files where anomalies exist and that should be fairly easy to do. For example, the Records Editor currently shows you have an incorrect entry at 08:16 on 13/02/2017. If you remove this from the Feb17log and then Fetch Monthly Log Data again it will show the new highest value (which will probably be 136.2 @ 16:42 on 20/02/2019). Correct this and fetch data again then continue this cycle until you believe you have an accurate high temp. This process should be much quicker then copying and pasting all of your log files.

Regards,
Trevor

EDIT: On second thoughts, I just looked closely at your Feb19log and the values are all over the place. Your data is at 5 minute intervals and the temperature goes from 34.5 to 103.3 to 92.1 to -10.8 to 25.5 all in the space of 20 minutes. You would have serious cleanup work to do. Your original thought of dumping all the data so you can sort it might be the best option.
Cambium
Posts: 274
Joined: Wed 03 Aug 2011 11:19 pm
Weather Station: ProWeatherTP3000
Operating System: Windows10
Location: Coastal CT, USA
Contact:

Re: Records

Post by Cambium »

flort wrote: Mon 06 Feb 2023 7:16 am I think your best course of action is to correct your log files where anomalies exist and that should be fairly easy to do. For example, the Records Editor currently shows you have an incorrect entry at 08:16 on 13/02/2017. If you remove this from the Feb17log and then Fetch Monthly Log Data again it will show the new highest value (which will probably be 136.2 @ 16:42 on 20/02/2019). Correct this and fetch data again then continue this cycle until you believe you have an accurate high temp. This process should be much quicker then copying and pasting all of your log files.

Regards,
Trevor

EDIT: On second thoughts, I just looked closely at your Feb19log and the values are all over the place. Your data is at 5 minute intervals and the temperature goes from 34.5 to 103.3 to 92.1 to -10.8 to 25.5 all in the space of 20 minutes. You would have serious cleanup work to do. Your original thought of dumping all the data so you can sort it might be the best option.
Thanks! Yeah, I never maintained it when it was going haywire.. Thanks for looking at it guys!

Looks like I got some work to do. I just realized also the Day file needs fixing too. 100°F+ days. Haha


SS2.jpg
You do not have the required permissions to view the files attached to this post.
Post Reply