Migrating from Cumulus 1 to MX: Difference between revisions

m
→‎Moving files from Cumulus 1 to MX: Another styling improvement
m (→‎Moving files from Cumulus 1 to MX: Another styling improvement)
Line 84: Line 84:
*Steve Loft designed MX so that in general it was able to read [[Moving_from_Cumulus_1_to_MX#Log_files|log files]] created by the original Cumulus.  
*Steve Loft designed MX so that in general it was able to read [[Moving_from_Cumulus_1_to_MX#Log_files|log files]] created by the original Cumulus.  
*See individual articles for more details on such differences.  
*See individual articles for more details on such differences.  
*'''Please note, the information for MX is taken from notes by Steve Loft, and applies to MX 3.0.0. Although, some updates have been made in line with release announcements by Mark, it is likely Mark has made other changes that affect the various log files that are not detailed in the release announcements, possibly making some content obsolete.'''
*'''Please note, the information for MX is taken from notes by Steve Loft, and applies to MX 3.0.0. Although, some updates have been made in line with release announcements by Mark, it is likely Mark has made other changes that affect the various log files that are not detailed in the release announcements, possibly making some content obsolete.'''  
 
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.
* If you move from Cumulus 1 to a version of MX  up to 3.5.y, the transfer is likely to be significantly easier. This is because Steve Loft was keen to keep forward compatibility in his beta MX, and it took a while for Mark Crossley to revise the part of the MX code that reads log files.
* If you move from Cumulus 1 to a version of MX  up to 3.5.y, the transfer is likely to be significantly easier. This is because Steve Loft was keen to keep forward compatibility in his beta MX, and it took a while for Mark Crossley to revise the part of the MX code that reads log files.
** Cumulus 1 is tolerant of various separators for dates and times.  
** 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.  
**Cumulus MX 3.0.0 insists all times use a colon separator (says Steve Loft), and all dates are in ISO format.  
===UPDATE===
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.
*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.
*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 log 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.  
5,838

edits