Skip to main content

access-experiment-generator

CI CD Coverage Status License Code style: black

About

The ACCESS Experiment Generator is a tool for creating ensembles of model experiments from a single control configuration. Instead of manually editing multiple files, you describe changes in one YAML plan, and the generator:

  • Clones the configuration repository from GitHub.
  • Creates a control branch (with optional edits).
  • Creates one new branch per perturbation experiment.
  • Applies the parameter changes and commits them.

Each generated branch is immediately Payu-ready — you can step into the branch directory and launch runs on Gadi, NCI using Payu.

Documentation

The ACCESS experient generator documentation can be found at: https://access-experiment-generator.hive-docs.org.au/

Key features

  • YAML-driven configuration: define edits once, apply them across many experiments.
  • Git-branch workflow: each variant is a branch, making experiments traceable.
  • Reproducibility: given the same repo + YAML, identical branches are regenerated.
  • Payu integration: generated branches are ready to run on Payu.

Documentation

Full documentation is available at https://access-experiment-generator.access-hive.org.au/

Installation

User setup

The experiment-generator is installed in the payu-dev conda environment:

module use /g/data/vk83/prerelease/modules && module load payu/dev

Alternatively, create a Python virtual environment and install via pip:

python3 -m venv <path/to/venv> --system-site-packages
source <path/to/venv>/bin/activate

pip install experiment-generator

Development setup

For contributors and developers, setup a development environment,

git clone https://github.com/ACCESS-NRI/access-experiment-generator.git
cd access-experiment-generator

# under a virtual environment
pip install -e .

Usage

$ experiment-generator --help

usage: experiment-generator [-h] [-i INPUT_YAML_FILE]

Manage ACCESS experiments using configurable YAML input.
If no YAML file is specified, the tool will look for 'Experiment_generator.yaml' in the current directory.
If that file is missing, you must specify one with -i / --input-yaml-file.

options:
  -h, --help            show this help message and exit
  -i INPUT_YAML_FILE, --input-yaml-file INPUT_YAML_FILE
                        Path to the YAML file specifying parameter values for experiment runs.
                        Defaults to 'Experiment_generator.yaml' if present in the current directory.

Example YAML

An exmaple plan (examples/Experiment_generator_example.yaml)

model_type: access-om2 # Specify the model ("access-om2", "access-om3", "access-esm1.5", or "access-esm1.6")
repository_url: git@github.com:ACCESS-NRI/access-om2-configs.git
start_point: "fce24e3" # Control commit hash for new branches
test_path: prototype-0.1.0 # All control and perturbation experiment repositories will be created here; can be relative, absolute or ~ (user-defined)
repository_directory: 1deg_jra55_ryf # Local directory name for the central repository (user-defined)

control_branch_name: ctrl
keep_uuid: false # Keep a pre-existing UUID. If true, this overrides new_uuid.
new_uuid: false # Generate a fresh UUID for an existing branch. Equivalent to Payu's --new-uuid.

Control_Experiment:
  accessom2.nml:
    date_manager_nml:
      restart_period: "0,0,86400"

  config.yaml:
    queue: express
    walltime: 5:00:00

  ice/cice_in.nml:
    shortwave_nml:
      albicei: 0.05
      albicev: 0.08
    thermo_nml:
      chio: 0.001

Perturbation_Experiment:
  Parameter_block1:
    branches:
      - perturb_1
      - perturb_2

    ice/cice_in.nml:
      shortwave_nml:
        albicei:
          - 0.06
          - 0.07
        albicev:
          - 0.78
          - 0.81
      thermo_nml:
        chio:
          - 0.007
          - 0.008

    ocean/input.nml:
      ocean_nphysics_util_nml:
        agm_closure_length:
          - 25000.0
          - 75000.0

Workflow example

  1. Run the generator
experiment-generator -i examples/Experiment_generator_example.yaml
  1. Inspect branches
cd my-experiment/1deg_jra55_ryf
git branch
# ctrl
# main
# perturb_1
# perturb_2
  1. Check changes
git checkout perturb_1
git diff ctrl -- ice/cice_in.nml

Metadata

Release files for experiment-generator 0.10.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 experiment-generator 0.10.0
File Size Uploaded
experiment_generator-0.10.0.tar.gz 161.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for experiment-generator 0.10.0
File Interpreter ABI Platform
experiment_generator-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 199.6 kB

Release files / experiment_generator-0.10.0.tar.gz

Download URL experiment_generator-0.10.0.tar.gz
Size 161.2 kB
Tags Source
SHA-256 checksum
How to use checksums
4b0ad1d2311ad8c9bc7cec66e798049b655886f136c2a78ec80225f1b97f60e6
BLAKE2b-256 checksum
How to use checksums
55714901884580b167744b7119dfc26639b3e99959a38f54e34c2843f67fdbb3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

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

Transparency log

Release files / experiment_generator-0.10.0-py3-none-any.whl

Download URL experiment_generator-0.10.0-py3-none-any.whl
Size 38.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0217e9aaf16de118148b12c7aa528bf556d70f97deb1f16feb481afa23f8bf1d
BLAKE2b-256 checksum
How to use checksums
75c13d099ed5f2028571488ab792cb378a5ddb07f2e633bc9d5b186870f46d69
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

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

Transparency log

Release history Release notifications | RSS feed

1.0.0

2 release files

0.10.2

2 release files

This release

0.10.0 This release

2 release files

0.9.0

2 release files

0.8.3

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

0.0.2

2 release files

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