PyAntiGen
PyAntiGen is a declarative, object-oriented framework for generating compartmental biological models in Antimony format. It is designed to abstract away the repetitive boilerplate of defining reactions and compartments manually, allowing researchers to build complex, scalable models using clean Python syntax.
Features
- Object-Oriented Modules: Encapsulate tissues, flows, synthesis, and excretion into reusable Python classes.
- Dynamic Registration: Automatically binds reactions, compartments, and species to the global model state when a module is instantiated.
- Project Scaffolding: Includes a CLI command to instantly spin up new modeling projects with all necessary directories.
- Isotope Tracking: Natively supports tracking labeled isotopes and generating corresponding parallel reactions.
Installation
You can install PyAntiGen into your Python environment with:
pip install pyantigen
You can also install PyAntiGen globally into your preferred Python environment by cloning this repository and running pip:
git clone https://github.com/elbert5770/PyAntiGen.git
cd PyAntiGen
pip install -e .
Quick Start: Creating a New Model
Because PyAntiGen is installed as a system-level Python package, you don't need a copy of the framework files in your working directory.
To start a brand new modeling workspace, just open a terminal and navigate to a folder where you want your project to live (be careful not to build within the PyAntiGen folder itself) and run:
pyantigen-create MyNewModel
This will automatically scaffold the following project directory:
MyNewModel/
├── .agents/
│ └── skills/ (agent skills, e.g. module generation, ODE conversion)
├── Projects/
│ ├── Example/ (full example: generate, run + Modules/, Engine/)
│ │ ├── Model_generate.py
│ │ ├── Model_run.py
│ │ └── Modules/ (Data, AntimonyGen, Plots, Simulate, Optimize, Experiment, Events)
│ └── MyNewModel/ (same structure, Modules/ pre-populated from Example)
│ ├── Model_generate.py
│ ├── Model_run.py
│ └── Modules/ (Data, AntimonyGen, Plots, Simulate, Optimize, Experiment, Events)
├── antimony_modules/
│ └── __init__.py (plus Basic/ for the example)
├── data/ (Example experiment CSVs copied for the example)
├── antimony_models/
│ └── Example/ (Example_parameters.csv, Example_InitialConditions.csv, etc.)
├── generated/
│ └── Example/ (reaction dict, rules, etc. after generate)
├── results/
│ └── Example/ (plots from Model_run.py)
├── SBML_models/
└── pyantigen_settings.json (e.g. archive_with_timestamp: false)
Every project folder under Projects/ has a script called Model_generate.py that is run to generate the model. MODEL_NAME is derived automatically from the enclosing folder name (see AntiGen_paths.py), so being in the right project folder is all that's needed to generate/run the correct project. From MyNewModel/Projects/Example/ run:
python Model_generate.py
This generates the model from the specified files in 'antimony_modules' and writes outputs to antimony_models/Example/ and generated/Example/. This is entirely optional as Model_run.py also calls the constructor functions in Model_generate.py.
To run a simulation or optimization, you may edit the parameters in antimony_models/Example/Example_parameters.csv, derived parameters in antimony_models/Example/Example_manual.txt, and initial conditions in antimony_models/Example/Example_InitialConditions.csv.
Then, run Model_run.py to simulate the Example in Tellurium/RoadRunner:
python Model_run.py --simulate Example
To run optimization examples use the --optimize flag:
python Model_run.py --optimize Example1
python Model_run.py --optimize Example2
python Model_run.py --optimize Example3
Your own model lives under Projects/MyNewModel/. Modify the code for your model in Projects/MyNewModel/Modules/, Projects/MyNewModel/Model_generate.py, and Projects/MyNewModel/Model_run.py. Your problem will also require new modules in antimony_modules/ to define the model.
Running from an IDE (Cursor / VS Code)
The Play button uses whichever Python interpreter is currently selected. If your environment (conda/venv) isn’t loaded, the run may fail with import or path errors.
- Select the correct interpreter:
Ctrl+Shift+P(orCmd+Shift+Pon macOS) → Python: Select Interpreter → choose the environment where you ranpip install -e .(e.g. your conda or venv). - Run from project root: Open the project folder (e.g.
MyNewModel) as the workspace. Use Run and Debug (or Play onProjects/Example/Model_run.py); the project root is resolved from the script location soantimony_models/Example/,generated/Example/, andresults/Example/resolve correctly.
Metadata
Release files for PyAntiGen 1.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyantigen-1.0.7.tar.gz | 106.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyantigen-1.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 225.6 kB
Release files / pyantigen-1.0.7.tar.gz
| Download URL | pyantigen-1.0.7.tar.gz |
|---|---|
| Size | 106.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89e2909b85131d88d9319b42f45e77bc23195ee7545856688599131649c8872f
|
|
BLAKE2b-256 checksum How to use checksums |
3c39d0feda8bcc04f2a68f72731d2e78b2889acf9d86694e1b8b326598373505
|
| 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 18, 2026.
Transparency logRelease files / pyantigen-1.0.7-py3-none-any.whl
| Download URL | pyantigen-1.0.7-py3-none-any.whl |
|---|---|
| Size | 119.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
931dd6f2ef8024fc64495f0c76c0de4a72cb366baca4d08bacb583348a73abbb
|
|
BLAKE2b-256 checksum How to use checksums |
d956fba535f438772444d34d7d54f04483f4257f51643bdf1b38f1507c35e7a1
|
| 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 18, 2026.
Transparency log