Skip to main content

taskmaestro-resinsight

taskmaestro tasks and example workflows for ResInsight.

Installation

pip install taskmaestro-resinsight

rips must match the ResInsight build it talks to. To use the API from a local ResInsight checkout instead of the released one on PyPI:

pip install -e /path/to/resinsight/GrpcInterface/Python

Development setup

git clone https://github.com/OPM/taskmaestro-resinsight ~/src/taskmaestro-resinsight
cd ~/src/taskmaestro-resinsight

# install this repo and its test/lint tools (including Ruff 0.16+)
pip install -e ".[dev]"

Discovering tasks and workflows

Installing the package registers its tasks and completions workflow through the taskmaestro.tasks and taskmaestro.workflows entry-point groups. No source-tree scan, PYTHONPATH change, or workflow-directory symlink is needed:

from taskmaestro import (
    get_registered_workflow,
    registered_task_names,
    registered_workflow_names,
)

print(
    sorted(name for name in registered_task_names() if name.startswith("resinsight."))
)
# ['resinsight.add_perforation', 'resinsight.connect', ...]

print(registered_workflow_names())
# {'resinsight.completions'}

workflow = get_registered_workflow("resinsight.completions")
print(workflow.to_mermaid())

The example in workflows/resinsight_completions/workflow.yaml also uses entry-point identifiers such as resinsight.connect in its task: and depends_on: fields. It can be loaded normally after installation:

from taskmaestro import load_workflow_from_yaml

loaded = load_workflow_from_yaml(
    "workflows/resinsight_completions/workflow.yaml",
    "workflows/resinsight_completions/input.yaml",
)

Applications can use registered_workflows() as their workflow catalogue and avoid the old convention of scanning ~/.taskmaestro/workflows.

Included operations

The package includes tasks for launching, connecting to, and exiting ResInsight; opening, saving, and closing projects; loading cases, properties, surfaces, and well paths; creating and configuring grid views; and creating or exporting well completions.

Running tests

RESINSIGHT_EXECUTABLE=/path/to/ResInsight pytest tests/ -v

Metadata

Release files for taskmaestro-resinsight 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for taskmaestro-resinsight 0.4.0
File Size Uploaded Provenance
taskmaestro_resinsight-0.4.0.tar.gz 30.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for taskmaestro-resinsight 0.4.0
File Interpreter ABI Platform
taskmaestro_resinsight-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 60.4 kB

Release files / taskmaestro_resinsight-0.4.0.tar.gz

Download URL taskmaestro_resinsight-0.4.0.tar.gz
Size 30.9 kB
Tags Source
SHA-256 checksum
How to use checksums
ac4dac8f6a46cbea3fe4b96a0e3ac9eb84123f2fc2bf2c4122b1d4478e2a9723
BLAKE2b-256 checksum
How to use checksums
c03eda1ae1a52f36b841c930e1d13b18e31719a89e27c106b8155231ba530662
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 23, 2026.

Transparency log

Release files / taskmaestro_resinsight-0.4.0-py3-none-any.whl

Download URL taskmaestro_resinsight-0.4.0-py3-none-any.whl
Size 29.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5dbecf8c5150803f26685290d0ad2a4134966a04d2f290014911649e6d17242b
BLAKE2b-256 checksum
How to use checksums
214b2a89e305bb4bc46a511c920e195c9b53512b4964962fa05eb1743cf842ce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 23, 2026.

Transparency log

Security for taskmaestro-resinsight 0.4.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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for taskmaestro_resinsight-0.4.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 23, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page