Monthlyalltime.ini: Difference between revisions

636 bytes removed ,  07:26, 29 January 2021
m
→‎Correcting/Editing the file within Cumulus: Removing text that was written when only Cumulus 1 existed
m (→‎Correcting/Editing the file within Cumulus: Removing text that was written when only Cumulus 1 existed)
Line 42: Line 42:


== Correcting/Editing the file within Cumulus ==
== 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 screenBy 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 [[Standard_log_files|Standard 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.
 
Please read [[Correcting Extremes]] page for full information.
 
   
=== Editing monthlyalltime.ini outside Cumulus ===  
=== Editing monthlyalltime.ini outside Cumulus ===  
It is unlikely that you need to do this, given the functionality of the in-built editor for both Cumulus 1 and recent builds of MX.  If you cannot find the file see FAQ [[FAQ#I_can.E2.80.99t_find_my_data_files.21]].
 
It is unlikely that you need to do this, given the functionality of the in-built editor for both Cumulus 1 and recent builds of MX.  If you cannot find the file (in your Windows installation) 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.  
'''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).
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).
5,838

edits