5,838
edits
Alltime.ini: Difference between revisions
m
→How alltime.ini is used
m (→Cumulus MX) |
|||
|
== How alltime.ini is used ==
If you restart Cumulus 1 during the day it will read this file at startup, so it can resume tracking extremes of the key parameters starting from latest stored values in alltime.ini. Equally, if you close Cumulus 1 during the day it will write the final values for highs and lows and their timestamps to alltime.ini as part of the close down process. Remember, while Cumulus 1 is running, the values shown in the table will usually be up to date, but there may be some time lag as it can hold values in an internal memory.
For Cumulus MX, the developers have not documented how it works, and I have not examined the code to this detail, but I believe it reads this file at start up and updates the file when necessary as it processes the various reads from your weather station. I saw no evidence of it being featured in the close down process.
== Editing this log file ==
It is possible that rogue values read from your weather station will cause this log file to show an incorrect extreme. As mentioned earlier, there is a log of changes to the "alltime.ini" records, called [[alltimelog.txt]], so look at that to see when your rogue value was processed and what was the previous extreme that you should reset to in "alltime.ini".
| |||