Today.ini: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
688 bytes added ,  23:24, 15 March 2017
m
→‎Introduction: Added clarifications
m (→‎Example today.ini file: Add note re MX)
m (→‎Introduction: Added clarifications)
Line 2: Line 2:
The files '''today.ini''' and '''yesterday.ini''' are used by Cumulus to store the Highs and Lows (and their timestamps) for key parameters as reached on each of the two days.  These files are normally located in the Data sub-folder of the path where your Cumulus.exe is installed. See [[FAQ#I_can.E2.80.99t_find_my_data_files.21| FAQ on location of data log files]] for where else to look.  
The files '''today.ini''' and '''yesterday.ini''' are used by Cumulus to store the Highs and Lows (and their timestamps) for key parameters as reached on each of the two days.  These files are normally located in the Data sub-folder of the path where your Cumulus.exe is installed. See [[FAQ#I_can.E2.80.99t_find_my_data_files.21| FAQ on location of data log files]] for where else to look.  


The highs and lows are held in memory while Cumulus is running.  At the end of a day [either midnight, or 9am (or 10am) depending on your configuration and season], the final values and timestamps written to today.ini file are rolled-over to become values and timestamps in yesterday.ini; and a new today.ini is created.  From the examples below you can see that the two files have a few differences in content, so rolling-over does involve a little editing work.  
The highs and lows, as held in memory while Cumulus is running, are constantly re-written to ''today.ini''.  At the end of a day [either midnight, or 9am (or 10am) depending on your configuration and season], the final values and timestamps written to today.ini file are rolled-over.  Many are written as a new line appended onto [[dayfile.txt]] and most become values and timestamps in yesterday.ini; then a new today.ini is created.  The three files have a few differences in content, so rolling-over does involve a little editing work. When Cumulus is left running, a daily backup of all the files is created as part of this rollover.


If you restart Cumulus during the day it will read both these files at startup, so it can resume tracking extremes of the key parameters starting from latest stored values in today.ini. Equally, if you close Cumulus during the day it will write the final values for highs and lows and their timestamps to today.ini as part of the close down process.
If you restart Cumulus during the day it will read the ''today.ini'' file at startup, so it can resume tracking extremes of the key parameters starting from latest stored values in today.ini. Note that, if your weather station type supports it, Cumulus will update ''today.ini'' with revised highs and lows as it processes the station's memory; and if necessary it will do a roll-over as it processes the readings for the relevant time (this roll-over process takes a bit longer to create the daily backup than that when Cumulus is left running). As explained on support forum, there can be problems if Cumulus is started/stopped just before or just after (i.e. close to) its roll-over time.  Equally, if you close Cumulus during the day it will have written the final values for highs and lows and their timestamps to today.ini as part of the close down process.


== Dealing with rogue values ==
== Dealing with rogue values ==
5,838

edits

Navigation menu