PyAntiGen 1.0.15__tar.gz → 2.0.1__tar.gz

{pyantigen-1.0.15 → pyantigen-2.0.1}/.github/workflows/publish.yml

@@ -3,21 +3,27 @@ name: Publish to PyPI
 on:
   push:
     tags:
-      - "v*"          # triggers on any tag like v0.1.0, v1.2.3
+      - "v*"          # triggers on any tag like v2.0.0
 
 jobs:
+  test:
+    uses: ./.github/workflows/tests.yml
+
   build-and-publish:
+    needs: test                # a failing test or build blocks the upload
     runs-on: ubuntu-latest
-    environment: pypi          # matches the environment name from Step 1
+    environment: pypi          # the environment configured for PyPI trusted publishing
     permissions:
       id-token: write          # required for trusted publishing
 
     steps:
       - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0       # setuptools-scm reads the version from the tag
 
       - uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.12"
 
       - name: Install build
         run: pip install build

pyantigen-2.0.1/.github/workflows/tests.yml

@@ -0,0 +1,46 @@
+name: Tests
+
+on:
+  push:
+    branches: [main, v2]
+  pull_request:
+  workflow_call:            # lets publish.yml gate a release on these tests
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0          # setuptools-scm needs the tags
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: pip install -e ".[test]"
+
+      - name: Test
+        run: python -m pytest tests -q
+
+  package:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build and check the distributions
+        run: |
+          pip install build twine
+          python -m build
+          twine check dist/*

{pyantigen-1.0.15 → pyantigen-2.0.1}/.gitignore

@@ -25,4 +25,4 @@ venv/
 ENV/
 
 # Written at build time by setuptools-scm (see [tool.setuptools_scm])
-framework/_version.py
+pyantigen/_version.py

{pyantigen-1.0.15 → pyantigen-2.0.1}/MANIFEST.in

@@ -4,5 +4,4 @@
 include README.md
 prune tests
 prune .git
-recursive-exclude __pycache__ *
-recursive-exclude *.pyc *
+global-exclude __pycache__ *.py[cod]

{pyantigen-1.0.15/PyAntiGen.egg-info → pyantigen-2.0.1}/PKG-INFO

@@ -1,16 +1,20 @@
 Metadata-Version: 2.4
 Name: PyAntiGen
-Version: 1.0.15
-Summary: Short one-line description of what PyAntiGen does
-Author: Open Source Contributor
-Author-email: Don <you@example.com>
-License: MIT
-Project-URL: Homepage, https://github.com/you/PyAntiGen
-Keywords: alzheimer,immunology,simulation
+Version: 2.0.1
+Summary: Declarative generation, simulation and identifiability analysis of compartmental Antimony/SBML models
+Author-email: Don Elbert <elbert5770@gmail.com>
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/elbert5770/PyAntiGen
+Project-URL: Repository, https://github.com/elbert5770/PyAntiGen
+Project-URL: Issues, https://github.com/elbert5770/PyAntiGen/issues
+Keywords: systems biology,antimony,SBML,tellurium,pharmacokinetics,alzheimer,simulation
 Classifier: Programming Language :: Python :: 3
-Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
 Classifier: Operating System :: OS Independent
-Requires-Python: >=3.9
+Classifier: Intended Audience :: Science/Research
+Classifier: Topic :: Scientific/Engineering :: Bio-Informatics
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: tellurium
@@ -21,13 +25,21 @@ Requires-Dist: numdifftools
 Requires-Dist: openpyxl
 Requires-Dist: matplotlib
 Requires-Dist: pypesto
-Dynamic: author
+Requires-Dist: SALib
+Provides-Extra: test
+Requires-Dist: pytest; extra == "test"
 Dynamic: license-file
 
 # 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.
 
+> **PyAntiGen 2 is a breaking release.** The package is now `pyantigen`
+> (was `framework`): model generation is `pyantigen.generate`, and the Engine
+> is `pyantigen.engine`, imported from the installed package instead of being
+> copied into every project. See [Migrating from 1.x](#migrating-from-1x) and
+> `docs/V2_DESIGN.md`.
+
 ## Features
 
 - **Object-Oriented Modules:** Encapsulate tissues, flows, synthesis, and excretion into reusable Python classes.
@@ -36,22 +48,91 @@ PyAntiGen is a declarative, object-oriented framework for generating compartment
 - **Isotope Tracking:** Natively supports tracking labeled isotopes and generating corresponding parallel reactions.
 
 ## Installation
-You can install PyAntiGen into your Python environment with:
+
+PyAntiGen needs **Python 3.11 or newer**. Install it into a virtual environment
+that belongs to your project, not into your system Python: the dependencies
+(Tellurium/RoadRunner, SciPy, pyPESTO, ...) are large and version-sensitive,
+and every result records the PyAntiGen version that produced it.
+
+### Recommended: a project-local environment with uv
+
+[uv](https://docs.astral.sh/uv/) creates environments in well under a second and
+installs from a shared download cache, so each additional environment costs
+little disk space beyond the first. From your project folder:
+
 ```bash
+uv venv --python 3.12 .venv
+uv pip install --python .venv/bin/python pyantigen        # Windows: .venv\Scripts\python
+```
+
+Activate it (`source .venv/bin/activate`, or `.venv\Scripts\activate` on
+Windows), or call `.venv/bin/python` directly. For a reproducible environment,
+pin exact versions in a `requirements.txt` and install with
+`uv pip install -r requirements.txt`.
+
+### Standard library `venv` + pip
+
+```bash
+python -m venv .venv
+.venv/bin/python -m pip install pyantigen                  # Windows: .venv\Scripts\python
+```
+
+A fully populated environment is roughly 0.9 GB with plain pip, so keep one per
+project repository (and add `.venv/` to `.gitignore`) rather than one per model.
+
+### conda / mamba
+
+```bash
+conda create -n pyantigen python=3.12
+conda activate pyantigen
 pip install pyantigen
 ```
 
-You can also install PyAntiGen globally into your preferred Python environment by cloning this repository and running pip:
+### Check the installation
+
+```bash
+python -c "import pyantigen, pyantigen.engine; print(pyantigen.__version__)"
+```
+
+If a project's `AntiGen_paths.py` raises "PyAntiGen 2 ... is not installed",
+the wrong environment is active: activate the one you installed into.
+
+### Developing PyAntiGen itself
+
+Clone this repository and install it editable, with the test dependencies, into
+its own environment:
 
 ```bash
 git clone https://github.com/elbert5770/PyAntiGen.git
 cd PyAntiGen
-pip install -e .
+uv venv --python 3.12 .venv
+uv pip install --python .venv/bin/python -e ".[test]"
+.venv/bin/python -m pytest tests
 ```
 
+An editable install means edits take effect immediately, in every project that
+uses that environment. There is still only one copy of the Engine.
+
+### Migrating from 1.x
+
+1.x copied an `Engine/` folder into every project, so projects drifted apart.
+In 2.x the Engine is `pyantigen.engine` and projects hold none. To move a
+project:
+
+* `from framework.<module> import ...` becomes `from pyantigen.generate.<module> import ...`.
+* `from Engine.<module> import ...` becomes `from pyantigen.engine.<module> import ...`;
+  delete the project's `Engine/` folder.
+* Pass `MODEL_NAME` and `REPO_ROOT` in the settings given to `setup_simulation` /
+  `setup_optimization_from_groups` (see `Projects/Example/Model_run.py`).
+* Replace `AntiGen_paths.py` with the 2.x version from `pyantigen-create`; it
+  also refuses to run if the Engine is missing or a local `Engine/` reappears.
+* Regenerated Antimony may differ textually (for example constant compartment
+  volumes are written `compartment X := V_X`); compare simulated time courses,
+  not file contents.
+
 ## 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. 
+Because PyAntiGen is an installed package, you don't need a copy of its code 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:
 
@@ -65,14 +146,14 @@ MyNewModel/
 ├── .agents/
 │   └── skills/          (agent skills, e.g. module generation, ODE conversion)
 ├── Projects/
-│   ├── Example/         (full example: generate, run + Modules/, Engine/)
+│   ├── Example/         (full example: generate, run + Modules/)
 │   │   ├── Model_generate.py
 │   │   ├── Model_run.py
-│   │   └── Modules/     (Data, AntimonyGen, Plots, Simulate, Optimize, Experiment, Events)
+│   │   └── Modules/     (Data, Events, Experiment, Loss_config, Optimizer_settings, Plots, ...)
 │   └── MyNewModel/      (same structure, Modules/ pre-populated from Example)
 │       ├── Model_generate.py
 │       ├── Model_run.py
-│       └── Modules/     (Data, AntimonyGen, Plots, Simulate, Optimize, Experiment, Events)
+│       └── Modules/     (Data, Events, Experiment, Loss_config, Optimizer_settings, Plots, ...)
 ├── antimony_modules/
 │   └── __init__.py      (plus Basic/ for the example)
 ├── data/                (Example experiment CSVs copied for the example)
@@ -125,5 +206,5 @@ Your own model lives under `Projects/MyNewModel/`. Modify the code for your mode
 
 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.
 
-1. **Select the correct interpreter**: `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS) → **Python: Select Interpreter** → choose the environment where you ran `pip install -e .` (e.g. your conda or venv).
+1. **Select the correct interpreter**: `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS) → **Python: Select Interpreter** → choose the environment you installed PyAntiGen into (e.g. your project's `.venv` or conda environment).
 2. **Run from project root**: Open the *project* folder (e.g. `MyNewModel`) as the workspace. Use **Run and Debug** (or Play on `Projects/Example/Model_run.py`); the project root is resolved from the script location so `antimony_models/Example/`, `generated/Example/`, and `results/Example/` resolve correctly.

pyantigen-1.0.15/README.md → pyantigen-2.0.1/PyAntiGen.egg-info/PKG-INFO

@@ -1,7 +1,45 @@
+Metadata-Version: 2.4
+Name: PyAntiGen
+Version: 2.0.1
+Summary: Declarative generation, simulation and identifiability analysis of compartmental Antimony/SBML models
+Author-email: Don Elbert <elbert5770@gmail.com>
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/elbert5770/PyAntiGen
+Project-URL: Repository, https://github.com/elbert5770/PyAntiGen
+Project-URL: Issues, https://github.com/elbert5770/PyAntiGen/issues
+Keywords: systems biology,antimony,SBML,tellurium,pharmacokinetics,alzheimer,simulation
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Classifier: Intended Audience :: Science/Research
+Classifier: Topic :: Scientific/Engineering :: Bio-Informatics
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: tellurium
+Requires-Dist: scipy
+Requires-Dist: numpy
+Requires-Dist: pandas
+Requires-Dist: numdifftools
+Requires-Dist: openpyxl
+Requires-Dist: matplotlib
+Requires-Dist: pypesto
+Requires-Dist: SALib
+Provides-Extra: test
+Requires-Dist: pytest; extra == "test"
+Dynamic: license-file
+
 # 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.
 
+> **PyAntiGen 2 is a breaking release.** The package is now `pyantigen`
+> (was `framework`): model generation is `pyantigen.generate`, and the Engine
+> is `pyantigen.engine`, imported from the installed package instead of being
+> copied into every project. See [Migrating from 1.x](#migrating-from-1x) and
+> `docs/V2_DESIGN.md`.
+
 ## Features
 
 - **Object-Oriented Modules:** Encapsulate tissues, flows, synthesis, and excretion into reusable Python classes.
@@ -10,22 +48,91 @@ PyAntiGen is a declarative, object-oriented framework for generating compartment
 - **Isotope Tracking:** Natively supports tracking labeled isotopes and generating corresponding parallel reactions.
 
 ## Installation
-You can install PyAntiGen into your Python environment with:
+
+PyAntiGen needs **Python 3.11 or newer**. Install it into a virtual environment
+that belongs to your project, not into your system Python: the dependencies
+(Tellurium/RoadRunner, SciPy, pyPESTO, ...) are large and version-sensitive,
+and every result records the PyAntiGen version that produced it.
+
+### Recommended: a project-local environment with uv
+
+[uv](https://docs.astral.sh/uv/) creates environments in well under a second and
+installs from a shared download cache, so each additional environment costs
+little disk space beyond the first. From your project folder:
+
+```bash
+uv venv --python 3.12 .venv
+uv pip install --python .venv/bin/python pyantigen        # Windows: .venv\Scripts\python
+```
+
+Activate it (`source .venv/bin/activate`, or `.venv\Scripts\activate` on
+Windows), or call `.venv/bin/python` directly. For a reproducible environment,
+pin exact versions in a `requirements.txt` and install with
+`uv pip install -r requirements.txt`.
+
+### Standard library `venv` + pip
+
+```bash
+python -m venv .venv
+.venv/bin/python -m pip install pyantigen                  # Windows: .venv\Scripts\python
+```
+
+A fully populated environment is roughly 0.9 GB with plain pip, so keep one per
+project repository (and add `.venv/` to `.gitignore`) rather than one per model.
+
+### conda / mamba
+
 ```bash
+conda create -n pyantigen python=3.12
+conda activate pyantigen
 pip install pyantigen
 ```
 
-You can also install PyAntiGen globally into your preferred Python environment by cloning this repository and running pip:
+### Check the installation
+
+```bash
+python -c "import pyantigen, pyantigen.engine; print(pyantigen.__version__)"
+```
+
+If a project's `AntiGen_paths.py` raises "PyAntiGen 2 ... is not installed",
+the wrong environment is active: activate the one you installed into.
+
+### Developing PyAntiGen itself
+
+Clone this repository and install it editable, with the test dependencies, into
+its own environment:
 
 ```bash
 git clone https://github.com/elbert5770/PyAntiGen.git
 cd PyAntiGen
-pip install -e .
+uv venv --python 3.12 .venv
+uv pip install --python .venv/bin/python -e ".[test]"
+.venv/bin/python -m pytest tests
 ```
 
+An editable install means edits take effect immediately, in every project that
+uses that environment. There is still only one copy of the Engine.
+
+### Migrating from 1.x
+
+1.x copied an `Engine/` folder into every project, so projects drifted apart.
+In 2.x the Engine is `pyantigen.engine` and projects hold none. To move a
+project:
+
+* `from framework.<module> import ...` becomes `from pyantigen.generate.<module> import ...`.
+* `from Engine.<module> import ...` becomes `from pyantigen.engine.<module> import ...`;
+  delete the project's `Engine/` folder.
+* Pass `MODEL_NAME` and `REPO_ROOT` in the settings given to `setup_simulation` /
+  `setup_optimization_from_groups` (see `Projects/Example/Model_run.py`).
+* Replace `AntiGen_paths.py` with the 2.x version from `pyantigen-create`; it
+  also refuses to run if the Engine is missing or a local `Engine/` reappears.
+* Regenerated Antimony may differ textually (for example constant compartment
+  volumes are written `compartment X := V_X`); compare simulated time courses,
+  not file contents.
+
 ## 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. 
+Because PyAntiGen is an installed package, you don't need a copy of its code 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:
 
@@ -39,14 +146,14 @@ MyNewModel/
 ├── .agents/
 │   └── skills/          (agent skills, e.g. module generation, ODE conversion)
 ├── Projects/
-│   ├── Example/         (full example: generate, run + Modules/, Engine/)
+│   ├── Example/         (full example: generate, run + Modules/)
 │   │   ├── Model_generate.py
 │   │   ├── Model_run.py
-│   │   └── Modules/     (Data, AntimonyGen, Plots, Simulate, Optimize, Experiment, Events)
+│   │   └── Modules/     (Data, Events, Experiment, Loss_config, Optimizer_settings, Plots, ...)
 │   └── MyNewModel/      (same structure, Modules/ pre-populated from Example)
 │       ├── Model_generate.py
 │       ├── Model_run.py
-│       └── Modules/     (Data, AntimonyGen, Plots, Simulate, Optimize, Experiment, Events)
+│       └── Modules/     (Data, Events, Experiment, Loss_config, Optimizer_settings, Plots, ...)
 ├── antimony_modules/
 │   └── __init__.py      (plus Basic/ for the example)
 ├── data/                (Example experiment CSVs copied for the example)
@@ -99,5 +206,5 @@ Your own model lives under `Projects/MyNewModel/`. Modify the code for your mode
 
 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.
 
-1. **Select the correct interpreter**: `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS) → **Python: Select Interpreter** → choose the environment where you ran `pip install -e .` (e.g. your conda or venv).
+1. **Select the correct interpreter**: `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS) → **Python: Select Interpreter** → choose the environment you installed PyAntiGen into (e.g. your project's `.venv` or conda environment).
 2. **Run from project root**: Open the *project* folder (e.g. `MyNewModel`) as the workspace. Use **Run and Debug** (or Play on `Projects/Example/Model_run.py`); the project root is resolved from the script location so `antimony_models/Example/`, `generated/Example/`, and `results/Example/` resolve correctly.

pyantigen-2.0.1/PyAntiGen.egg-info/SOURCES.txt

@@ -0,0 +1,98 @@
+.gitignore
+LICENSE
+MANIFEST.in
+README.md
+pyproject.toml
+.github/workflows/publish.yml
+.github/workflows/tests.yml
+.vscode/launch.json
+PyAntiGen.egg-info/PKG-INFO
+PyAntiGen.egg-info/SOURCES.txt
+PyAntiGen.egg-info/dependency_links.txt
+PyAntiGen.egg-info/entry_points.txt
+PyAntiGen.egg-info/requires.txt
+PyAntiGen.egg-info/scm_file_list.json
+PyAntiGen.egg-info/scm_version.json
+PyAntiGen.egg-info/top_level.txt
+docs/PROTOCOL_LAYER.md
+docs/V2_DESIGN.md
+pyantigen/.gitignore
+pyantigen/__init__.py
+pyantigen/_version.py
+pyantigen/cli.py
+pyantigen/.agents/skills/module_generation/SKILL.md
+pyantigen/.agents/skills/ode_conversion_antimony/SKILL.md
+pyantigen/.agents/skills/ode_extraction_pipeline/SKILL.md
+pyantigen/engine/Anchor_cache.py
+pyantigen/engine/Deadline.py
+pyantigen/engine/Differential_evolution.py
+pyantigen/engine/Evaluator.py
+pyantigen/engine/Event_times.py
+pyantigen/engine/Fast_profile.py
+pyantigen/engine/Fit_cache.py
+pyantigen/engine/Identifiability.py
+pyantigen/engine/Model_optimize.py
+pyantigen/engine/Model_simulate.py
+pyantigen/engine/Nelder_mead.py
+pyantigen/engine/Noise_floor.py
+pyantigen/engine/Optimize.py
+pyantigen/engine/Petab_export.py
+pyantigen/engine/Preequil_cache.py
+pyantigen/engine/Profile_checkpoint.py
+pyantigen/engine/README.md
+pyantigen/engine/Results.py
+pyantigen/engine/Sensitivity_analysis.py
+pyantigen/engine/Simulate.py
+pyantigen/engine/__init__.py
+pyantigen/generate/AntimonyGen.py
+pyantigen/generate/RxnDict_to_antimony.py
+pyantigen/generate/TelluriumGen.py
+pyantigen/generate/__init__.py
+pyantigen/generate/antimony_utils.py
+pyantigen/generate/data_interpolation.py
+pyantigen/generate/isotopomer_tools.py
+pyantigen/generate/model_generation.py
+pyantigen/generate/models.py
+pyantigen/generate/module_base.py
+pyantigen/generate/pyantigen.py
+pyantigen/generate/rate_laws.py
+pyantigen/generate/reaction_creation.py
+pyantigen/study/__init__.py
+pyantigen/study/assay.py
+pyantigen/study/describe.py
+pyantigen/study/design.py
+pyantigen/study/lower_v1.py
+pyantigen/study/optimization.py
+pyantigen/study/params.py
+pyantigen/study/quantity.py
+pyantigen/study/reagent.py
+pyantigen/study/refs.py
+pyantigen/study/remarks.py
+pyantigen/study/serialize.py
+pyantigen/study/validate.py
+pyantigen/template/Example/AntiGen_paths.py
+pyantigen/template/Example/Flipflop_reference.py
+pyantigen/template/Example/Model_generate.py
+pyantigen/template/Example/Model_run.py
+pyantigen/template/Example/Modules/Data.py
+pyantigen/template/Example/Modules/Events.py
+pyantigen/template/Example/Modules/Experiment.py
+pyantigen/template/Example/Modules/Loss_config.py
+pyantigen/template/Example/Modules/Observed_species.py
+pyantigen/template/Example/Modules/Optimizer_settings.py
+pyantigen/template/Example/Modules/Plots.py
+pyantigen/template/Example/Modules/Solver_settings.py
+pyantigen/template/Example/Modules/Update_opt_parameters.py
+pyantigen/template/Example/Modules/Update_parameters.py
+pyantigen/template/Example/optimizations/Example1_ADneg.json
+pyantigen/template/Example/optimizations/Example1_ADpos.json
+pyantigen/template/Example/optimizations/Example3_joint.json
+pyantigen/template/Example/optimizations/Example4_flipflop.json
+pyantigen/template/Example/optimizations/example.py
+pyantigen/template/Example/studies/example.json
+pyantigen/template/Example/studies/example.py
+pyantigen/template/Example/studies/flipflop.json
+pyantigen/template/data/ADneg.csv
+pyantigen/template/data/ADpos.csv
+pyantigen/template/data/Flipflop.csv
+pyantigen/template/data/make_flipflop_data.py

pyantigen-2.0.1/PyAntiGen.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+pyantigen-create = pyantigen.cli:create_project

{pyantigen-1.0.15 → pyantigen-2.0.1}/PyAntiGen.egg-info/requires.txt

@@ -6,3 +6,7 @@ numdifftools
 openpyxl
 matplotlib
 pypesto
+SALib
+
+[test]
+pytest