Monthlyalltime.ini: Difference between revisions
m (→Editing monthlyalltime.ini outside Cumulus: removed text moving elsewher) |
|||
| Line 20: | Line 20: | ||
Stop Cumulus first. 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]. Do not add nor remove parameters, simply amend the values and timestamps. 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). | Stop Cumulus first. 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]. Do not add nor remove parameters, simply amend the values and timestamps. 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). | ||
Revision as of 13:43, 18 March 2020
What is monthlyalltime.ini file?
The file monthlyalltime.ini was introduced in version 1.9.3 to support the Monthly Records feature that was added. For more information on this file see in the Cumulus help file, in the section “Data log file format”.
Put simply, it is just like the alltime.ini log file but each section in that is repeated 12 times in "monthlyalltime.ini" file as it contains the extremes recorded in all January periods, all February periods etc. The new feature in Cumulus allows you to compare the current month with the same month in earlier years and pick out which year had highest and lowest. The alltime.ini log file was heavily influenced by the seasonality of our weather, you might expect highest temperatures to be seen in a summer and lowest in a winter. The monthlyaltime.ini log file takes away that seasonality by limiting comparisons to a month by month basis.
Initialisation
If you update Cumulus from an earlier version than version 1.9.3, or swap from Cumulus version 1.9.2 to Cumulus MX, then you need to initialise log file by reading prior data from the monthly and daily log files. Follow the instructions for correcting the file. Once the file has been initialised, Cumulus will maintain it from then onwards, comparing the highs and lows for the current reading against those stored for that month in this file. For further information see the support forum, that contains the announcement when version 1.9.3 was released, and a few discussions concerning experience with the feature.
Viewing the monthly highs and lows
Select Highs and Lows - Monthly from View menu.
Correcting/Editing the file within Cumulus
Expanding the information in the FAQ: FAQ#How_do_I_correct_my_all-time_.28or_monthly.29_records.3F, you can update the values stored in monthlyalltime.ini by choosing all time monthly records from the Edit menu in Cumulus. This is a text editor, and works best when at full screen. By clicking the appropriate buttons, you can get Cumulus to display the extremes found by looking through all the data available in dayfile.txt for the selected month in all years, and all the data available in Monthly log files for that month in all years. Click the Help button on that screen for detailed instructions on how to copy figures across from log to log or to directly edit them on screen.
Editing monthlyalltime.ini outside Cumulus
It is unlikely that you need to do this, given the functionality of the in-built editor. Cumulus MX however, does not yet have an editor, so you have no choice but to edit the file manually. If you cannot find the file see FAQ FAQ#I_can.E2.80.99t_find_my_data_files.21.
Tips -- take a copy of the original log file before you work on it outside Cumulus.
Stop Cumulus first. 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]. Do not add nor remove parameters, simply amend the values and timestamps. 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).
