5,838
edits
Dayfileeditlog.txt: Difference between revisions
m
→Content generation: added example
(New page using cross-references to stop it needing maintenance when related pages changed.) |
m (→Content generation: added example) |
||
|
It will have one row for each date that is missing in the original ''dayfile.txt'', but present in monthly log files. A row holds the fields listed [[Dayfile.txt#List_of_fields_in_the_file|here]], including highs and lows of that (meteorological) day, calculated from looking at all the records in the [[Monthly_log_files]] for that (meteorological) day, and the added rows are in chronological order (but without rows for any date that is in 'dayfile.txt').
== Content generation ==
Cumulus 'Create missing' makes no attempt to create values for 'highest hourly rainfall' but does the best it can with everything else. Normally, what is stored in dayfile.txt is based on every reading received from the weather station, but only the logged readings are available to put as values and timestamps in dayfileeditlog.txt and Cumulus has to assume that these have captured all extremes for each daily summary row it creates. Calculated values that involve a number of original observations (e.g. temperature and wind speed are needed to calculate wind chill) may be particularly sensitive to logging interval.
= Exiting the editor =
When you press ''OK'', the records listed in ''dayfileeditlog.txt'' are inserted (from version 1.9.4) in correct chronological order position into ''dayfile.txt'' file. If you press ''Cancel'', the ''dayfileeditlog.txt'' is retained, but the ''dayfile.txt'' file is left unchanged.
| |||