C-STAR Forge
A utility for generating new regional oceanographic modeling domains and creating reproducible C-Star workflows through blueprint descriptors.
:alt: C-STAR Forge Logo
:class: csforge-logo
:align: center
This project is still in an early phase of development.
You are welcome to try out using the package, but be aware that development is ongoing and we cannot yet guarantee backwards compatibility.
How it works
C-STAR Forge takes you from "I want a regional ROMS-MARBL domain here" to a running simulation in three steps:
-
Build a forge blueprint — an interactive wizard (in Jupyter, or as a standalone Voilà web app) helps you assemble a
ForgeBlueprintfrom catalog specs (model, domain, forcing, output). The blueprint is a single YAML file that fully describes what to generate. -
Process the blueprint — the forge application consumes the forge blueprint and produces everything needed to run: grids, initial conditions, surface/boundary forcing, rivers, tides, rendered model settings, and a ROMS-MARBL blueprint describing the resulting setup:
python -m cstar_forge.run path/to/forge_blueprint.yaml
-
Run the simulation — C-Star consumes the ROMS-MARBL blueprint to build and execute the actual ROMS-MARBL simulation.
To learn more, check out the documentation.
Installation
Until packaged releases are available, install from source with the setup script
(creates the cstar-forge-v0 conda environment, installs the package in editable
mode, and registers a Jupyter kernel):
git clone https://github.com/CWorthy-ocean/cstar-forge.git
cd cstar-forge
./dev-setup.sh
conda activate cstar-forge-v0 # or: micromamba activate cstar-forge-v0
See docs/installation.md for details, options, and verification steps.
Building a ForgeBlueprint
Two interactive front-ends assemble a ForgeBlueprint (the authoritative input to
processing). Both are thin shells over
cstar_forge.forge_blueprint_resolve.build_forge_blueprint; all resolution/validation
lives in the resolver.
In a Jupyter notebook
cstar_forge/forge-blueprint-wizard.ipynb— run the wizard inline, then inspectwiz.config. Good for exploring / scripting.
from cstar_forge.forge_blueprint_wizard import ForgeBlueprintWizardApp
app = ForgeBlueprintWizardApp()
app.display()
# ... build & review ... then: cfg = app.inner.config
ForgeBlueprintWizardApp adds a catalog-location bar above the wizard: it auto-loads
the bundled in-repo catalog (catalog/) by default, or you can enter a different
local path, "local", a GitHub URL, or an http URL and click Reload catalog to
rebuild the wizard against it.
As a standalone web app (Voilà)
cstar_forge/forge-blueprint-wizard-app.ipynb— a code-free "form" view, served by Voilà (pure Python,pip install voila, no admin).
./run-wizard-app.sh # opens http://localhost:8866
On an HPC login node (no browser there), bind locally and SSH-forward from your laptop:
# on the login node:
./run-wizard-app.sh --no-browser
# on your laptop:
ssh -N -L 8866:localhost:8866 <user>@<login-node>
# then open http://localhost:8866 locally
Use the Download link to save forge_blueprint.yaml to your machine (works in the
browser without server file access), or Save to disk to write it on the host
running Voilà. Take the file to the machine of your choice to run the processing
step.
Portability note: the builder needs only
pydantic+pyyaml(andipywidgets/voilafor the UI) — no ROMS / C-Star / roms_tools. The one exception is the optional Compute dt (CFL) button, which builds a grid viaroms_tools; leave it and enterdtdirectly to stay fully lightweight.
Processing a ForgeBlueprint
On the machine where the input files should be generated (laptop or HPC):
python -m cstar_forge.run path/to/forge_blueprint.yaml
Run python -m cstar_forge.run --help for options (partial runs, host inspection,
verbosity, dask controls). Outputs — input NetCDF files, rendered model settings, and
the ROMS-MARBL blueprint — are written under the blueprint's working directory, and
the emitted ROMS-MARBL blueprint is then handed to C-Star to run the simulation.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file cstar_forge-0.3.0.tar.gz.
File metadata
- Download URL: cstar_forge-0.3.0.tar.gz
- Upload date:
- Size: 4.7 MB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
b24a3c0d324b61e7e4def3b0ff7c48ca9412fbfb6e8ab63f156c962d59d4b740
|
|
| MD5 |
b7bc78b303fce790dab1e7a5f34addfd
|
|
| BLAKE2b-256 |
3ca1d0cc8ea8ab339d925f334a9220f8b59b96f9a38a8a98f82feb42f3e0370c
|
Provenance
The following attestation bundles were made for cstar_forge-0.3.0.tar.gz:
Publisher:
pypipublish.yaml on CWorthy-ocean/cstar-forge
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
cstar_forge-0.3.0.tar.gz -
Subject digest:
b24a3c0d324b61e7e4def3b0ff7c48ca9412fbfb6e8ab63f156c962d59d4b740 - Sigstore transparency entry: 2373817025
- Sigstore integration time:
-
Permalink:
CWorthy-ocean/cstar-forge@dc76055ae0721a060220e87f45996a9e15f0b499 -
Branch / Tag:
refs/tags/0.3.0 - Owner: https://github.com/CWorthy-ocean
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
pypipublish.yaml@dc76055ae0721a060220e87f45996a9e15f0b499 -
Trigger Event:
release
-
Statement type:
File details
Details for the file cstar_forge-0.3.0-py3-none-any.whl.
File metadata
- Download URL: cstar_forge-0.3.0-py3-none-any.whl
- Upload date:
- Size: 215.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
251482b42f4767a55560397d7540f17ac44ba0cd084205c77d30f9131440daa0
|
|
| MD5 |
fdf2f3f123c6c4d84a658d11c7780e76
|
|
| BLAKE2b-256 |
88aa3aadf744c30ebd06eb5618dfba917f3a911dae4e0ced49db9d3351c240c4
|
Provenance
The following attestation bundles were made for cstar_forge-0.3.0-py3-none-any.whl:
Publisher:
pypipublish.yaml on CWorthy-ocean/cstar-forge
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
cstar_forge-0.3.0-py3-none-any.whl -
Subject digest:
251482b42f4767a55560397d7540f17ac44ba0cd084205c77d30f9131440daa0 - Sigstore transparency entry: 2373817133
- Sigstore integration time:
-
Permalink:
CWorthy-ocean/cstar-forge@dc76055ae0721a060220e87f45996a9e15f0b499 -
Branch / Tag:
refs/tags/0.3.0 - Owner: https://github.com/CWorthy-ocean
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
pypipublish.yaml@dc76055ae0721a060220e87f45996a9e15f0b499 -
Trigger Event:
release
-
Statement type: