Category:Log Files: Difference between revisions

m
Correction - made clearer that references to "Cumulus" apply to original version 1
m (Correction - made clearer that references to "Cumulus" apply to original version 1)
BelowThis issub-category aprovides listlinks to pages that give explanations for all of the Log files within Cumulus.
 
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 software.
== CAUTIONS ==
 
Remember, if you edit any of these log files to obey cautions in the individual articles, here are some examples:
* stop cumulus before editing any file that Cumulus might be updating,
* 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 ==
===Moving Files from MX to Cumulus 1===
 
When Steve Loft designed his original Cumulus (1), he had no expectationexperience thatto onedraw dayupon as to the best way to treat items like dates. When he woulddesigned createCumulus MX, sohe was able to learn from his experiences with both Cumulus 1 and Cumulus 2, and he decided to use dates to an ISO specification (ISO 8601 Data elements and interchange formats – Information interchange – Representation of dates and times), and therefore log files are not [https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=15167 backwards compatible].
 
That said, there are some features in Cumulus 1 that are [[Moving_from_Cumulus_1_to_MX#Cumulus_1_features_not_ever_going_to_be_included_in_MX|missing in MX]], and there are Cumulus users who have migrated back either on a temporary basis (to use a missing feature before they return to MX) or in a very few cases decided to stay with Cumulus 1 (because they prefer it).
5,838

edits