Migrating from Cumulus 1 to MX: Difference between revisions

Migrating from Cumulus 1 to MX (view source)

Revision as of 09:39, 29 January 2021

287 bytes added , 09:39, 29 January 2021

m

→‎Moving files from Cumulus 1 to MX: Clarity

Sfws

5,838

edits

@@ Line 88: / Line 88: @@
 ** Cumulus 1 is tolerant of various separators for dates and times.
 **Cumulus MX 3.0.0 insists all times use a colon separator (says Steve Loft), and all dates are in ISO format.
+*This means, '''MX releases from version 3.0.0 to 3.5.4''' can read the date/time entries in the Cumulus 1 format and in the MX format.
+*When the MX software needs to update a particular entry (e.g. an extreme) in a particular file, it will subsequently save the file and change the content for the affected line to the new format.
+*Consequently, within a single file both formats will co-exist, you may see lines using Cumulus 1 format for the extremes that have existed for a while, and Cumulus MX format for any new extremes.
-===UPDATE===
+===Update as at MX release 3.7.0===
-In particular '''internal''' changes mentioned in release announcements for various 3.6.x versions, and for release 3.7.0, have made MX work significantly differently and it is now more fussy about content of log files.
+In particular '''internal''' changes mentioned in release announcements for various 3.6.x versions, and for release 3.7.0, have made MX work significantly differently and it is now more fussy about content of log files having to be in correct MX format.
-*However, '''MX releases from version 3.0.0 to 3.5.4''' will read the date/time entries in the Cumulus 1 format, and it will only change them to the new format when it needs to update a particular entry (e.g. an extreme) in that particular file.  Consequently some files will have a different formats for the extremes that have existed for a while and for any new ones, meaning both formats will co-exist in those files.
+** It is difficult to move from Cumulus 1 to a release of MX that is 3.6.z or higher, mainly because you may find that Cumulus 1's .txt, and .ini, files can no longer be read.
-** It is difficult to move from Cumulus 1 to a release of MX that is 3.6.z or higher, mainly because you may find that log files can no longer be read.
+**This is because '''for releases 3.7.0 onwards''', each log file in modern MX releases must have lines that match what is in the local settings absolutely perfectly;
-**In particular releases 3.7.0 onwards are less tolerant of log files created by the original Cumulus software; each log file in modern MX releases must have lines that match what is in the local settings absolutely perfectly; this means MX is now very fussy about the symbol that separates the 3 parts of a date, very fussy about decimal symbol, and number of fields in files.
+**this means MX is now very fussy about the symbol that separates the 3 parts of a date, very fussy about decimal symbol, and expects the number of parameters/fields in files to be consistent with release 3.7.0.
+**Thus modern releases are less tolerant of log files created by the original Cumulus software;
 ===General points===