gcubed.experiments
Public setup and runtime infrastructure for G-Cubed experiments.
One chartpack output declaration normalised for generation.
One ordered design output and its explicit layer membership.
One variable and its ordered, arbitrary metadata dimensions.
User-editable switches for one ordinary baseline invocation.
User-editable switches shared by ordinary and local experiment runs.
One named, dimension-neutral ordered member selection.
One selector with its model-resolved members in declaration order.
Exact variables plus metadata required by downstream artefact builders.
A validated setup-only document with normalised typed declarations.
Return the first chartpack for callers written before plural support.
Raised when a setup configuration violates its public contract.
A loaded setup document and paths implied by the retained model layout.
Purpose of a setup document, independent of its entry-point filename.
One generated optimisation-target CSV declaration.
An immutable sequence of model variables in source-catalogue order.
Raised when a variable declaration cannot be resolved unambiguously.
Legacy run-adapter discriminator, no longer part of setup YAML.
Normalize a dataframe or SymData-like object into a stable catalogue.
Dataframes may describe arbitrary dimensions with a mapping-valued
dimensions column, a SYM-style sets value such as
"sectors=a01,regions=USA", or explicitly named dimension_columns.
A SymData-like object is any object exposing such a dataframe through its
variable_summary attribute.
Return model and declared derived metadata suitable for chart setup.
Return derivations needed to resolve target and chart declarations.
Generate only declared layers, targets, designs, and chartpacks.
Preflight and atomically replace the complete declared setup write set.
Generate the first declared chartpack for compatibility callers.
Load setup YAML and return a copy of its canonical setup-only mapping.
Load one strict setup-only version-1 document from path.
Resolve ordered selector records, including member-group references.
Resolve setup paths from an explicit YAML document or Python entry point.
A Python source path selects a sibling setup document with the conventional
setup.yaml name. The Python filename itself is deliberately unrestricted
so historical entry-point names continue to work. Every other source path is
treated as the explicitly selected setup document.
Resolve one exact or selector-based variable declaration.
Matching variables always retain catalogue order. When
require_explicit_varying_dimensions is true, every dimension that
varies after filtering must appear in the ordered selectors so a later
chart splitter has an unambiguous grouping priority.
Resolve a declaration to exact names in stable catalogue order.
Solve or load a model, produce baseline projections, and report them.
Run one standard experiment with an optional local closure validator.
Run a standard baseline or experiment selected by its setup kind.