What is fmu-sim2seis?
Calculates synthetic seismic from reservoir simulation model, together with a petro-elastic model.
fmu-sim2seis can be run either from command line, or from ERT, the latter being the
preferred option.
Installation
To install fmu-sim2seis, run
pip install fmu-sim2seis
ERT jobs
fmu-sim2seis is divided into a series of separate jobs:
- sim2seis_seismic_forward
- sim2seis_relative_ai
- sim2seis_observed_data
- sim2seis_map_attributes
- sim2seis_cleanup
There exists also a forward model for running petro-elastic modelling, defined in fmu-pem.
In the ERT-file for running fmu-sim2seis, necessary arguments are shown in this example ERT setup.
Beware of hardcoded directory names - they should be replaced by your project path/name.
cd ./ERT
ert gui run_sim2seis.ert
fmu-sim2seis (and fmu-pem) are controlled by a series of .yaml-files which you find in examples of here.
The files modelled_data_intervals and observed_data_intervals.yml are used to define zones/intervals
for estimating seismic attributes. sim2seis_config contains all configuration parameters for all parts
of fmu-sim2seis workflow, except for observed seismic data, which has its own configuration file -
obs_data_config.yml.
Tests
fmu-sim2seis has tests that use the tests/data structure, which contains the necessary input data
files.
pytest tests
User interface
Users can visit https://equinor.github.io/fmu-sim2seis/ in order to get help configuring the fmu-sim2seis input data.
Developing the user interface can be done by:
cd ./documentation
npm ci # Install dependencies
npm run create-json-schema # Extract JSON schema from Python code
npm run docs:dev # Start local development server
The JSON schema itself (type, title, description etc.) comes from the corresponding Pydantic models in the Python code.
Metadata
Release files for fmu-sim2seis 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fmu_sim2seis-2.0.0.tar.gz | 18.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fmu_sim2seis-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.1 MB
Release files / fmu_sim2seis-2.0.0.tar.gz
| Download URL | fmu_sim2seis-2.0.0.tar.gz |
|---|---|
| Size | 18.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80ef5974933576fed6d44fe3695371a1f2520fa3130068f5de878e9cf1086623
|
|
BLAKE2b-256 checksum How to use checksums |
e00bca0cdf691572d133b4c89b3b1c3ac513f66270aeb09841eec5d996225014
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / fmu_sim2seis-2.0.0-py3-none-any.whl
| Download URL | fmu_sim2seis-2.0.0-py3-none-any.whl |
|---|---|
| Size | 75.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72db08de789b14ca8872e56a5361fd3a9a6ad3d365bbf01898501b3cf8cf231d
|
|
BLAKE2b-256 checksum How to use checksums |
7a2c11ffc262dbf841be375b1fea41c31a857b857da5a7e30814728a4bd216c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log