Migris uses the HDF data storage format (https://www.hdfgroup.org/solutions/hdf5/) for storing important results. Several releases of the hdf system have been in use over time, including the 1.8 series. Migri migrated HDF to release 1.10.6 in 2021 and has used this release until 2025.
Migri hdf files use the .h5 subfix and the last part of the filename before the subfix will typically show what type of data are stored inside the hdf container(s).
Migri files include:
- __out.mir.h5: simulation result files from one or multiple caseruns
- __stochastic.h5: results from Process Stochastic created via the Stochastic Results menu.
- __moch.h5: results from Stochastic Traps processing.
The top level inside the Migri hdf files typically contains the MigriProjects name as the uppermost “leaf”. MigriProjects/Local are often used as the next level for projects that have been saved locally from Migri, MigriX or MigriBee. There will also usually be a string named www below MigriProjects which contains a reference to the documentation of Migri hdf files (e.g. https://migris.no/hdf/).
One example of a 2D array result dataset name would be: /MigriProjects/Local/myproject/Prime/Caseruns/0/0001/Output/Grids/EasyRo/159Ma_Layer/ref0
where myproject is the name of the project (mirp) file, 0 is the bee number, 0001 is the first simulation run of the bee, EasyRo is the topic stored, 159Ma_Layer is the full Migri name of the layer with a top age at 159Ma and name Layer while ref0 refers to a time of 0 Ma (present day).
Migri uses a nomenclature where each bee refers to a separate process simulated. Each bee will store caseruns starting with 0001 and continuing with 0002, 0003 etc. for each new simulation run. Interactive processes created with the GUI produce deterministic simulation runs which are given the number bee=0 while stochastic (MonteCarlo) simulations launched from the gui via the MigriBee process are given names like 1,2,3,4 etc. Each MigriBee will run in parallel and produce its own hdf file where the bee number is included in the filename. Thus myproject__0__out.mir.h5 would be produced by bee number 0 for the myproject.mirp filename.
For additional information about the Migri datafiles and organization of data take a look at the Migris support portal at https://migris.zendesk.com/hc/ or contact sylta@migris.no via email.
Comments