Known and New Migri Issues


This page contains a brief, updated, listing of important new issues found in Migri after the date of the most current release and aims to help Migri users who have concerns about problems they may experience. The reported issues will be fixed in later releases.


Description Status Version reported
Simulate next step does not work for single timestep models (must use Simulate to 0Ma instead) Fixed in 1.9.6 1.9.0
Crash when pasting new rows into an observation table and afterwards saving the table Fixed in 1.9.4 1.9.0
Crash when loading models with a large number of input grids (e.g. geometries with many layers). Fixed in 1.9.4 1.9.2
Unable to load fault csv files when building geometry Fixed in 1.9.2 1.9.0
Monitor stochastic may report incorrect statistics when running a large number of simulations per bee. Fixed in 1.9.2 1.9.0
Migri is not able to perform ranking analysis on Maturity simulations Fixed in 1.8.6 1.8.4
Log files (.mirl) can become very large when running more than 25 stochastic simulations on each MigriBee. Fixed in 1.8.2 1.8.0
TrapViewer may show incorrect leakage volumes when using many sublayers in the shallow section. Fixed in 1.8.2 1.7.0
File tree does not always update to show current file details when working on shared (e.g. samba) drives

Fixed in 1.8.0

(added reload tree button)

Lithology selection and legend does not always work correctly when using alternative lithology schemes

Fixed in 1.7.2

Incorrect conversion from metric to oil field untis for trapped gas volumes in Trap Viewer.

Fixed in 1.7.2

Incorrect values are sometimes entered when selecting items from the menus in Output Table Editor Fixed in 1.7.0 1.6.8
"Open last project" option sometimes opens the wrong project when running more than one Migri instance Fixed in 1.7.0 1.6.8
Temperature gradient at 0Ma sometimes gets overwritten when using “ModifyProject”. Fixed in 1.6.8 1.6.6
Bug when computing irregular mesh connections in special settings. Fixed in 1.6.8 1.6.6
Histories are sometimes incorrectly indexed when number of timesteps varies Fixed in 1.6.6 1.6.4
Layer boundaries in Geohistory plots are sometimes drawn incorrectly Fixed in 1.6.6 1.6.4
Fault geometry building may fail when using fault polygons from .csv files. Fixed in 1.6.4 1.6.2
Project.area does not always update when using File/Modify Project. Fixed in 1.6.2 1.6.0
TheMigrisk license feature is checked out even when the Use Migrisk license option is not activated Fixed in 1.6.2 1.6.0
MigriBee processes are started twice when launching local simulations on Windows. Fixed in 1.5.6 1.5.4
Progress bar sometimes disappear during simulations Fixed in 1.5.4 1.5.2
Migri sometimes crash when copying table data into Table editor Fixed in 1.5.4 1.5.2
Geometries are being generated twice after modifying the Geological Events table. Fixed in 1.5.2 1.5.0
Layer scale slider does not update when loading a view configuration Fixed in 1.5.0 1.4.0
Crash in Logviewer when removing data series Fixed in 1.5.0 1.4.2
Too few decimals in Riskchart cost function Fixed in 1.5.0 1.4.2
Unable to create new Monte Carlo iterations if the Load risks option in Riskchart setup is used. Fixed in 1.4.2 1.4.0
Expulsion is still shown (but not used as input to migration) for source rocks that have been disabled by setting = 0. Fixed in 1.4.2 1.4.0
The status text in the lower right corner is not correctly updated after using the Load caserun option in Caserun Selection. Fixed in 1.4.2 1.4.0
The old HC.Flowrates legend is displayed when viewing this property in the Profile view. Fixed in 1.4.2 1.4.0
Crash may sometimes occur when exporting polygon area outlines as polygons. Fixed in 1.4.0 1.3.10
Saving parameter list from the Shortlist window causes Migri to crash. Fixed in 1.4.0 1.3.10
Strata file with ';' separator crashed Migri Fixed in 1.4.0 1.3.10
Small traps that are picked in the 3d view are shown as empty in TrapViewer. Fixed in 1.4.0 1.3.10
The numbers of sublayers are not always shown in the Geological events editor. Fixed in 1.4.0 1.3.10
Free capacity volumes are reported as negative values in the trap table. Fixed in 1.4.0 1.3.10
Risk chart sometimes opens in a very small window. Fixed in 1.4.0 1.3.10
Relative paths are not set correctly in the History Editor after using the "Load histories from file" button. Fixed in 1.3.10 1.3.8
Wrong filenames are sometimes reported as missing when using Create Histories Fixed in 1.3.10 1.3.6
Exported Zycor ZMap files sometimes contain blank lines within the data section Fixed in 1.3.10 1.3.6
Some exported overlays in PetroMod 2015 are not recognized by Migri Fixed in 1.3.8 1.3.6
Vshale in lowermost sublayer occasionally wrong when no strata file is used Fixed in 1.3.8 1.3.6
Cannot add a layer that is older than the current basement layer using drag and drop method. Fixed in 1.3.4 1.3.2
Fixed an issue causing very shallow traps to sometimes not build columns and spill properly at some timesteps. Fixed in 1.3.4 1.3.2
Simulate background stochastic does not work with project filenames containing spaces Fixed in 1.3.4 1.3.2
Pore pressures are not plotted in Trap Viewer. Fixed in 1.3.4 1.3.2
The lowermost sublayer of the lowermost layer is not plotted in logviewer Fixed in 1.3.2 1.3.0
Migri crashes during Riskchart setup if some the required columns in the HC observations file are missing. Fixed in 1.3.2 1.3.0
Status dialog does not show after Create Geometry operation has completed successfully Fixed in 1.2.6 1.2.4
Expulsion histories may be loaded incorrectly if input maps contains illegal (e.g. extremely high)   values at some timesteps. Fixed in 1.2.6 1.2.4
Tablines mathematical operation does not work correctly Fixed in 1.2.6 1.2.4
Trap phases are now plotted in flowrate and trap plots when uppermost carrier is not at top of layer. Fixed in 1.2.4 1.2.2
MigriBee simulations occasionally stop due to memory allocation issues Fixed in 1.2.4 1.2.2
Animations of Migri maturities/transformations/generation sometimes do not show same values as simulation result plots. Fixed in 1.2.4 1.2.2
Horizon lines may cross in Profiles when layers are dipping steeply. Open 1.2.2
Elements below fault planes are not plotted in Profiles. Open 1.2.2
Linux: Plotting Expulsion results repeatedly may crash Migri.  Fixed in 1.2.4 1.2.2
Mismatch in Permeability/Entry pressure for layer with 1 sublayer Fixed in 1.2.2 1.2.0
Quickplot may crash on open/save session in Linux Fixed in 1.2.2 1.2.0
Project.T.adjust is missing from the riskchart/distribution table Fixed in 1.2.2 1.2.0
Riskchart does not handle more than 150-200 observations Fixed in 1.2.2 1.2.0
Export to ZMap does not handle filenames > 80 chars Fixed in 1.2.2 1.2.0
When loading Petromod v12 histories, any spaces in the prefix and subfix fields in the histories editor need to be replaced by a "^" for Migri to be able to load the files. Fixed in 1.2.0 1.1.0
When saving, the time-step editor will occasionally be corrupted. Fixed in 1.2.0 1.1.0
Some models may crash when first selecting TWT or Age as timestep and afterwards selecting 0Ma. Fixed in 1.2.0 1.1.0
Unable to load xyz files into Selection Info panel when all layers are hidden. Fixed in 1.2.0 1.1.0
MigriBee does not accept longer paths than 200 characters.

Fixed in 1.2.0

Note: The max filepath length on Windows is 256 characters, while Linux has no limit.

Clip planes and planes are clipped to camera. Fixed in 1.2.0 1.1.0
When closing Migri by clicking the "x" button in the upper, the process is not shut down properly. Fixed in 1.2.0 1.1.0
Gridmaps are not loaded when root node is toggled. Fixed in 1.2.0 1.1.0
History grids (Eroded, Sedimentsurface, Temperature.surface, etc) need to use the same AOI (area of interest) as the geometry used in the modelling.  Workaround: use the Migri Explorer to resample these grids and use the resampled grids as input. 1.0.8
Not everything is stored when exporting to VTFx, e.g. wells and streams. Open. Only patience helps here, but do tell us what your highest priorities are. 1.0.8
Maturity plots, including may be corrupted if you navigate back and forward between timesteps.  Workaround: when using these properties always move forward in time. 1.0.8
The accuracy of the depth geometry model created by Migri and the accuracy of the burial history has been an issue for some users. Burial history accuracy is, in our experience, in the +-5m range for paleodepths and ca 10 cm for the present day depths.  Fix: The 1.1.0 release may in many cases improve the accuracy  if you recreate the history and geometry files. 1.0.8
Have more questions? Submit a request