What is fmu-pem?
Petro-elastic model (PEM) for use in e.g. fmu-sim2seis based on the rock-physics-open library.
How to use fmu-pem?
Installation
To install fmu-pem, first activate a virtual environment, then type:
pip install fmu-pem
The PEM is controlled by parameter settings in a yaml-file, given as part of the command line arguments, or by the workflow parameter if it is run as an ERT forward model.
Calibration of rock physics models
Calibration of the rock physics models is normally carried out in RokDoc prior to running the PEM. Fluid and mineral properties can be found in the RokDoc project, or from LFP logs, if they are available.
How to develop fmu-pem?
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-pem 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 | Provenance | Actions |
|---|---|---|---|---|
| fmu_pem-2.0.0.tar.gz | 33.4 MB | With provenance | Details for fmu_pem-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fmu_pem-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for fmu_pem-2.0.0-py3-none-any.whl |
Total release size: 33.5 MB
Release files / fmu_pem-2.0.0.tar.gz
| Download URL | fmu_pem-2.0.0.tar.gz |
|---|---|
| Size | 33.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d15cad25f7aa8455a2eeb28f44443420d8c18de45b79e147396a2c01266cfa5
|
|
BLAKE2b-256 checksum How to use checksums |
65aa150025bd036e086327c315765453a45b02703131107ce7103b1c4a8b6592
|
| 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 Oct 13, 2026.
Transparency logRelease files / fmu_pem-2.0.0-py3-none-any.whl
| Download URL | fmu_pem-2.0.0-py3-none-any.whl |
|---|---|
| Size | 112.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef98ffd77114592064ab1d8357033c6a89ea94ebf2678a158f83a5e55b1f5361
|
|
BLAKE2b-256 checksum How to use checksums |
f45b203e5ce8275805b98f58409e07b31c627170ff3294f3d5efee58b9b5b197
|
| 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 Oct 13, 2026.
Transparency logSecurity for fmu-pem 2.0.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for fmu_pem-2.0.0.tar.gz
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 Oct 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.