Alltime.ini: Difference between revisions

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).

Edit the original file using an editor that treats all fields as text [either any text editor, or a spreadsheet program that can be instructed ''not'' to recognise special field (like date) types]. All values have to be specified in the correct section, see [[#Post_Build_924_(version_1.8.9)]] above and follow the format of the property lines in the example below. Note that figures are held internally in Cumulus in binary, and converted to Base 10 numbers for the value shown. Since fractional binary values cannot be converted exactly to base 10 decimals, real numbers appear to be given to a strange decimal resolution with multiple decimal places. Also 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).