|
|
| Line 3: |
Line 3: |
| Descriptions, and tips, can also be found in the Help file within the Cumulus 1 software. | | Descriptions, and tips, can also be found in the Help file within the Cumulus 1 software. |
|
| |
|
| == CAUTIONS == | | == Correcting Log files == |
|
| |
|
| Remember, if you edit any of these log files to obey cautions in the individual articles, here are some examples:
| | [[Calculate Missing Values]] and [[Correcting Extremes]] are the pages to look at. |
| * if you want to edit outside Cumulus, any of its files, take a copy, and edit that, because Cumulus needs sole write access.
| |
| * don't use a word processor (that adds lots of unwanted control characters),
| |
| * don't change the format of files for example don't change format of dates or real numbers (using a spreadsheet, like Microsoft Office Excel or Libre Office Calc, don't let dates or special numbers be recognised),
| |
| * don't add 'Byte Order Mark' (traditionally, Microsoft and Google software treat a BOM as a required magic number, and so their software may add a BOM when saving text as UTF-8. Google Docs also traditionally adds a BOM when converting a document to a plain text file for download).
| |
| * don't add blank lines to any Comma Separated Value files(the only 'blank' line in a log file is the final one, where Cumulus will later append the next item), (you can add blank lines to log files that contain "attribute=value" lines such as 'today.ini')
| |
| * don't add any header lines to any log files where Cumulus needs to read the file as well as update it (Cumulus reads all log files '''except''' Alltimelog.txt).
| |
|
| |
|
| == TYPES == | | == TYPES == |
