5,838
edits
m (→(Invented rain) Error in all-time extremes or month-by-month all time extremes: added list of extremes) |
m (→How do I correct my all-time (or monthly all-time) records?: Slight re-sequencing of existing material to emphaise edit logs before ini files.) |
||
Line 794: | Line 794: | ||
== How do I correct my all-time (or monthly all-time) records? == | == How do I correct my all-time (or monthly all-time) records? == | ||
Cumulus works by whenever the reading it is currently processing exceeds a particular record, that record is updated. In essence, Cumulus end-of-day works by reading what is in the detailed [[Monthly_log_files]] to find the highs and lows during the day just ended, these then update the [[dayfile.txt|daily summary log]]. Cumulus can also read what is in the daily summary log to update the all-time extremes held in [[alltime.ini]] and month-by-month all-time extremes held in [[monthlyalltime.ini]]. Look up those cross-references to help you understand the various items, and how they can be updated. | |||
Either 1) Consequently, you can manually copy the sequence remembering it requires several steps: | |||
# Correct the rogue values or values in the detailed [[Monthly_log_files]] ''with Cumulus stopped''. Neither Cumulus 1 nor Cumulus MX provides an editor to do this, and you need to guess new values for readings as there is no other file provided by Cumulus to offer any suggestions, often people interpolate between earlier and later readings. | |||
# Correct the [[dayfile.txt|daily summary log]] ''(don't do this near the rollover time)'', the editor in Cumulus 1 requires you to manually change the numbers, unless you delete the whole day (or it was previously missing) and you ask Cumulus to '''Insert missing''' i.e. populate a single line (day) from the detailed log, ignoring any extremes at times between logged readings. | |||
# Correct the all-time extremes held in [[alltime.ini]] and monthly all-time extremes held in [[monthlyalltime.ini]]. For both these files if you are using ''Cumulus MX'' you will need to use an external text file editor (don't use a word processor). Using the Cumulus 1 [[Cumulus_Screenshots#File.2FEdit.2FHelp_Menu|built-in appropriate editor]] from the first couple of commands in the Edit menu allows you to see, and copy across, suggested extremes based on contents of the detailed [[Monthly_log_files]] or contents of the [[dayfile.txt|daily summary log]]. | |||
If you know the correct figures, you can enter them manually. | or 2) If you know the correct figures, you can alternatively enter them manually directly into the .ini files and not bother to update the detailed log or the daily summary log. (It is pointless to edit the .ini files directly and then afterwards edit the log files): | ||
*You can look at the [[Alltimelog.txt]] file to find the previous values for the [[ | *You can look at the [[Alltimelog.txt]] file to find the previous values for the [[alltime.ini|all-time records]]. | ||
*Similar entries are logged to the [[diags]] files for the monthly highs and lows in [[ | *Similar entries are logged to the [[diags]] files for any updates to the monthly highs and lows in [[monthlyalltime.ini|month-by-month records]]. | ||
Cumulus takes a backup of | |||
or 3) Cumulus takes a backup of most of the active data files when it starts up, and also at the start of the meteorological day (just after midnight for a lot of users). The backups are kept in folders within the backup sub-folder in the Cumulus installation. So yet another alternative method would be to find the latest backup from before the error occurred, and copy the ''alltime.txt'' and/or ''monthlyalltime.txt'' file from the backup to the Cumulus data folder. Do this with Cumulus stopped. There is more information in [[:Category:Log_Files]], for all of the types of file. | |||
== It's January 1st and my 'rain since midnight' and/or 'last 24 hours rain' and/or Evapotranspiration are wrong/negative == | == It's January 1st and my 'rain since midnight' and/or 'last 24 hours rain' and/or Evapotranspiration are wrong/negative == |
edits