5,838
edits
Dayfile.txt: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
→Manipulation outside Cumulus: Expansion of 'NULL' section
m (→Using the daily summary log on your web-site: added x-ref) |
(→Manipulation outside Cumulus: Expansion of 'NULL' section) |
||
|
* Most value fields are in ''real number format x.y'' using your system decimal notation, a few (e.g. bearings, solar, humidity) are ''integers'' (see [[#List_of_fields_in_the_file]]). Whilst an integer can be used for a real number field, decimals are not allowed in an integer field.
* If you insert a ''lowest or highest value'' into a day, where there was none before, insert a ''timestamp'' too, as a dayfile.txt row is only accepted by the Cumulus editor if a value and any related timestamp are either both present or both absent. (Use a timestamp of your rollovertime 00:00, 09:00 or 10:00 if you have not looked up the precise time).
* Nulls ',,' are not allowed in the line (except during editing after all available valid parameters inserted, they may be added at end of lines inserted by 'Create Missing' (or your external editing software) as all lines end up with same number of fields), so if you do not know the value for a particular field within the line, then type in a zero for integer values and an extreme with opposite value (e.g. -999.9 for a signed decimal maximum, and 9999.9 for a decimal minimum) for decimal format (replace the full stops with your decimal separator).
**Beware - if you do insert zero or an obviously wrong extreme value, Cumulus will display those in any editing screen where you wish to update the all-time, monthly-all-time, this month, or this year, extremes. This can make editing by picking values in logs harder.
**Cumulus itself will use zero for any parameters (e.g. solar) not provided by your station, and will repeat the last valid value if the station fails to send a value it should provide.
**Some third-party scripts read the file to calculate averages or other statistics, and their authors suggest you remove rogue values (creating the ',,' that Cumulus objects to). My suggestion is use the 'External Program' facility to create a copy of ''dayfile.txt'' and make any such changes only on that copy. Alternatively, do as I do, upload the file into a database, with validation code checking for the -999.9 etc, and store the '''NULL''' value if that validation finds such an obviously invalid figure.
* Make sure that any editing does not create any ''blank lines'' in the file.
* All rows must ''start with date'' and include some of the parameters listed ''in correct sequence''.
| |||
