Page 1 of 1
Records
Posted: Sun 05 Feb 2023 12:55 pm
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
Re: Records
Posted: Sun 05 Feb 2023 1:30 pm
by freddie
Use the records editors. They are accessed from the "edit" menu on the MX interface.
Re: Records
Posted: Sun 05 Feb 2023 3:38 pm
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
Re: Records
Posted: Sun 05 Feb 2023 3:58 pm
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.
Re: Records
Posted: Sun 05 Feb 2023 5:01 pm
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.
Re: Records
Posted: Sun 05 Feb 2023 5:28 pm
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
Re: Records
Posted: Sun 05 Feb 2023 5:35 pm
by freddie
Just taking the High temp record - you appear to have a large value in your Feb 2017 logfile too.
Re: Records
Posted: Sun 05 Feb 2023 8:06 pm
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.
Re: Records
Posted: Mon 06 Feb 2023 7:16 am
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.
Re: Records
Posted: Mon 06 Feb 2023 12:41 pm
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