We try to make sure that Migri is backward compatible in the sense that new releases of Migri can load all old projects. Many new projects can, however, be loaded by old releases of Migri, but Migri is not always forward compatible. When new projects make use of features that were not present in older versions of Migri, the forward compatibility will off course be broken, and Migri may present the user with a message similar to:
The version you are using is too old for this project. See Troubleshooting at Help/OnlineSupport for more info (Project requires YYMMDD)
The Project will then not be loaded into Migri because of the issue referred to by YYMMDD:
170914: New default lithology parameter values not supported by pre 1.5.6 releases
190410: ENI lithologies not supported by pre 1.8.0 releases
190810: Modified ENI lithologies not supported by pre 1.8.2 releases
210311: Baur 4 component kinetics added to the Migri 2.0.0 release. Migri 1 series can not model with multicomponent kinetics, but you can change from Baur to Pepper kinetics in order to simulate the model.
211122: The Migri CO2 module requires a Migri 2.1.0 release to work properly.
220408: LateralBarriers functionality requires version 2.2.0 or newer.
221130: The use of Regular (R!), Triangular (T!) and Lognormal (L!) distributions requires 2.3.0 or newer.
231212: Project.downwards=2 will boost the downwards migration calculation along carrier pinchouts.
240202: Vertical LeakageZones was introduced as a new feature in Migri 2.4.0
250101: Using 2 source rocks units for each layer not supported by pre 2.5.0 releases.
250501: Project.strata.method=1 improves permeability function, but is not supported by pre 2.5.0 releases.
Sometimes you may still need to load the project into the older version of Migri. This can be done by repeatedly trying to load the project - a minimum of e.g 3 times - until it loads into Migri. After doing this, we recommend that you check what the issue may be. This you may do by writing in the command window:
im Project.info Project.requires
one of more numbers in the form of YYMMDD, e.g. 210311 may be listed, each representing a date where a new feature that is required by the project was added. At the present time, the list above contains the new features dates that older releases cannot load.
Comments