5,838
edits
Alltime.ini: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Editing alltime.ini within Cumulus
m (Update for post build 924) |
|||
| Line 14: | Line 14: | ||
If you restart Cumulus 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 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. | If you restart Cumulus 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 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. | ||
=== Editing alltime.ini within Cumulus === | === Editing alltime.ini within Cumulus === | ||
Expanding what it says in FAQ: [[FAQ#How_do_I_correct_my_all-time_.28or_monthly.29_records.3F]], the stored values can be corrected using the ''All time records'' screen on the '''Edit''' menu and this Cumulus editor allows you to read from the [[dayfile.txt|daily log]] or the [[Monthly_log_files]]. Therefore, normally any rogue values are corrected in these source files, and resulting lows and highs copied across to the all time log using the in-built editor. However, you can also just edit any low, high or timestamp manually looking at [[Alltimelog.txt]] for current and previous values. Note that the timestamp includes a calendar date, so for a 9 or 10am rollover, if you need to manually look for highs and lows for times between midnight and rollover, these would be derived from the daily log (dayfile.txt) row for the meteorological date (the date before the calendar date for those early hours). | |||
=== Editing alltime.ini outside Cumulus === | === Editing alltime.ini outside Cumulus === | ||
