viva-tellurium
Process-bigraph wrapper for Tellurium /
libroadrunner, exposing any SBML or Antimony
kinetic model as a process-bigraph Process so it can be composed with
other simulators in a bigraph document.
View Interactive Demo Report — Lotka-Volterra predator-prey, Elowitz-Leibler repressilator, and Gillespie stochastic dimerization with Plotly time series, phase portraits, reaction-rate charts, and bigraph architecture diagrams.
Installation
uv venv .venv && source .venv/bin/activate
uv pip install -e .
Quick Start
from process_bigraph import Composite, allocate_core, gather_emitter_results
from process_bigraph.emitter import RAMEmitter
from viva_tellurium import TelluriumProcess, make_tellurium_document
ANTIMONY = """
model decay
S1 = 10; S2 = 0
S1 -> S2; k*S1; k = 0.3
end
"""
core = allocate_core()
core.register_link('TelluriumProcess', TelluriumProcess)
core.register_link('ram-emitter', RAMEmitter)
doc = make_tellurium_document(model=ANTIMONY, interval=1.0)
sim = Composite({'state': doc}, core=core)
sim.run(10.0)
print(gather_emitter_results(sim)[('emitter',)][-1]['species'])
API
TelluriumProcess (Process)
Time-driven bridge wrapping a RoadRunner instance. Lazy init; each update()
advances by interval.
| Port | Dir | Schema |
|---|---|---|
species |
input | maybe[map[float]] |
species |
output | overwrite[map[float]] |
rates |
output | overwrite[map[float]] |
parameters |
output | overwrite[map[float]] |
time |
output | overwrite[float] |
Config (all optional, one of model/model_file required):
model, model_format ('antimony'/'sbml'), model_file, integrator
('cvode'/'gillespie'), absolute_tolerance, relative_tolerance,
seed, species_overrides, parameter_overrides, reset_on_init.
TelluriumStep (Step)
One-shot trajectory Step. Extra config: start_time, end_time, n_points.
Outputs: time_series (list), species_trajectories (map[list]).
make_tellurium_document(...)
Ready-to-run composite document wiring a TelluriumProcess to a stores dict
and a RAM emitter.
Demo & Tests
python demo/demo_report.py # regenerates demo/report.html, opens in Safari
pytest tests/ # 17 offline tests
Metadata
Release files for viva-tellurium 0.1.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 | |
|---|---|---|---|
| viva_tellurium-0.1.0.tar.gz | 13.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| viva_tellurium-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.5 kB
Release files / viva_tellurium-0.1.0.tar.gz
| Download URL | viva_tellurium-0.1.0.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
457e0a284633c762ae44f2e5c95230aa8a174f55979c7b645cda6adb876ad072
|
|
BLAKE2b-256 checksum How to use checksums |
b43ac5e833c661486d6b6fa277170b579bb6ad4da25303b196fe6413fc3dac5a
|
| 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 30, 2026.
Transparency logRelease files / viva_tellurium-0.1.0-py3-none-any.whl
| Download URL | viva_tellurium-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
056a7404a7bbc22993bd0ec664f59ba5f06e0afbda162f86825e1ec3eb194558
|
|
BLAKE2b-256 checksum How to use checksums |
583403ca494f10d5459957898716a681c90fc9ca7c9f60e85da3943835cc98da
|
| 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 30, 2026.
Transparency log