Skip to main content

Rundra

Rundra is a portable experiment-execution framework for reproducible scientific computing. It provides stable run and task identities, explicit stochastic seeds, structured JSON output, immutable staged inputs, scheduler integration, and result retrieval through one command-line interface.

Installation

Rundra requires Python 3.12. Install the command as an isolated user tool:

uv tool install rundra
rundr --version
rundr help

Install the optional MCP interface with:

uv tool install 'rundra[mcp]'
rundr-mcp --help

Basic workflow

An experiment combines an executable command, a YAML configuration, explicit resources, and one or more integer seeds:

rundr validate experiment.yaml --json
rundr plan experiment.yaml --seeds 0:3 --json
rundr submit experiment.yaml --seeds 0:3
rundr wait --last --progress
rundr fetch --last

rundr run performs submission, waiting, and retrieval synchronously. Remote targets can combine SSH transport, a Slurm or OpenPBS scheduler, rsync or shared staging, and an Apptainer container runtime. Site connection, account, queue, workspace, and authentication policy remain explicit operator configuration.

If an asynchronous submission is interrupted, rundr resume RUN_ID recovers its durable scheduler outcome without creating a duplicate Run. rundr list returns compact paginated summaries, while rundr tasks RUN_ID pages through Task details. Automatic fetch can avoid redundant bulk transfer when client and target paths are safely visible through the same filesystem.

Automation

All important lifecycle commands support structured JSON. The optional MCP server exposes the same operation layer over stdio or authenticated Streamable HTTP, including submission recovery and paginated discovery. Network transport requires an environment-sourced bearer token and an explicit host policy; TLS should terminate at an operator-managed reverse proxy.

Rundra does not store SSH keys, passwords, registry credentials, or scheduler credentials. Run only experiment definitions and source trees that you trust, because their declared commands execute with the configured user's privileges.

The source repository contains development documentation, examples, schemas, and the complete test suite.

Metadata

Release files for rundra 0.1.3

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

Source distribution (sdist)

Source distribution for rundra 0.1.3
File Size Uploaded
rundra-0.1.3.tar.gz 207.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rundra 0.1.3
File Interpreter ABI Platform
rundra-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 450.7 kB

Release files / rundra-0.1.3.tar.gz

Download URL rundra-0.1.3.tar.gz
Size 207.2 kB
Tags Source
SHA-256 checksum
How to use checksums
7c763aee812b306809d3a77fe5d938e4895069ebb018fa7f8b6c43c1eb4d31ed
BLAKE2b-256 checksum
How to use checksums
0c1c534c82ec9245174410e11f7578bf5690c0c0883598a1131d1bfb599f085e
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 Aug 20, 2026.

Transparency log

Release files / rundra-0.1.3-py3-none-any.whl

Download URL rundra-0.1.3-py3-none-any.whl
Size 243.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
00be2343204883adc9722ac8ad71ad222634c960c40564ef353a62da8703f8ec
BLAKE2b-256 checksum
How to use checksums
06e005ec7245e04ff2cb9aa7c782ad7d8ecad57cae56eb5bb52aea67405dc551
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 Aug 20, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

This release

0.1.3 This release

2 release files

0.1.1

2 release files

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