Dayfile.txt: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
→‎Editing in Cumulus: introduced word 'obsolete', added 2nd para about errors
m (→‎Dealing with rogue measurements: removal of reference to average wind speed always being midnight to midnight)
m (→‎Editing in Cumulus: introduced word 'obsolete', added 2nd para about errors)
The last command in '''Edit''' menu is ''dayfile.txt''. This is a text editor, and works best when at full screen.
Click the ''Help'' button for detailed instructions. Cumulus Help is comprehensive.
 
If there is an error in ''dayfile.txt'', then it is most likely to be found when you are viewing its data on one of the screens for editing the monthly, annual or all-time extremes. Cumulus will illuminate its ''Error'' light if it finds an error in such cases and tell you the line/row number of the first found error, together with some details of the error it found. For example, if a row is blank, a row is duplicated, a field is corrupted, a field does not have an acceptable value, or a field is missing so subsequent fields are to the left of where they should be.
 
You can use this editor to:
*correct individual values by overtyping,
*use '''insert''' key to add one or more missing rows (complete days) manually,
*use '''Create missing''' button to insert missing rows (complete days) by reading from [[Monthly_log_files]] and automatically calculating the best approximations for each field for those missing days.
 
If you do have a 'duplicate' error, you need to decide which row to ''delete'', and whether to copy any values from that row into the row you are keeping to ensure the correct extremes are retained.
 
As an alternative to manual line ''insert'', you may wish to use a procedure for importing, and processing, pre-Cumulus observations into [[Monthly_log_files]]. Once there is data for required days in monthly logs, ''Create missing'' can insert the new rows for those days previously missing in dayfile.txt.
For ''Create missing'' a list of inserted records is produced in [[dayfileeditlog.txt]]. If just some fields are wrong in a particular row (meteorological day) on day file, then there is a [[Monthly_log_files#Using_Monthly_logs_to_deal_with_shorter_.28or_incomplete.29_dayfile.txt_records_for_particular_dates | workaround]] as at all current versions (up to 1.9.4) you can only use 'Create missing' to read from the [[Monthly_log_files]] if the whole day (a row starting with a date) is missing in ''dayfile.txt''.
 
For ''Create missing'' a list of inserted records is produced in [[dayfileeditlog.txt]]. If just some fields are wrong in a particular row (meteorological day) on day file, then there is a [[Monthly_log_files#Using_Monthly_logs_to_deal_with_shorter_.28or_incomplete.29_dayfile.txt_records_for_particular_dates | workaround]] as at all current versions (up to 1.9.4) you can only use 'Create missing' to read from the [[Monthly_log_files]] if the whole day (a row starting with a date) is missing in ''dayfile.txt''.
The procedure for importing, and processing, pre-Cumulus observations is explained in [[Monthly_log_files |this Wiki topic]].
 
'''Note for obsolete version 1.9.2 and 1.9.3 only:''' CreateThere missing might in some cases be affected byis a bug in 1.9.3these thatversions canin causethat incorrect'Create datemissing' orderinserts for records (dayfile.txt uses dd/mm/yy or dd-mm-yy'heating and allcooling recordsdegree shouldday' bevalues inthe ascendingwrong chronologicalway order)round.
 
'''Note for versions 1.9.2 orobsolete version 1.9.3 only:''' ThereCreate ismissing might in some cases be affected by a bug in these1.9.3 versionsthat incan thatcause 'Createincorrect missing'date insertsorder 'heatingfor records (dayfile.txt uses dd/mm/yy or dd-mm-yy and coolingall degreerecords day'should valuesbe thein wrongascending waychronological round.order)
 
There are no known bugs in version 1.9.4 build 1086, the current release at time of writing.
 
==Manipulation outside Cumulus==
5,838

edits

Navigation menu