compare-calibration-rounds

Compare A2MC calibration rounds via cross-round parameter, mechanism, and model-evolution ledgers.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jingtao-lbl/A2MC --skill compare-calibration-rounds-jingtao-lbl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compare-calibration-rounds
Source: https://github.com/jingtao-lbl/A2MC/tree/main/.claude/skills/compare-calibration-rounds
Command: npx skills add https://github.com/jingtao-lbl/A2MC --skill compare-calibration-rounds-jingtao-lbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Calibration campaigns run many rounds, and without a cross-round record a later round can re-propose parameters that earlier rounds already tested and refuted, or compare rounds that ran on different model binaries. This Skill builds the cross-round parameter ledger, mechanism ledger, and model-evolution comparability verdict that every round report requires, including the first round. ## Core Features & Use Cases - Cross-Round Parameter Ledger: One row per parameter ever in play, one column per round, with statuses like calibrated, refuted with mechanism, baked into base, or bounds provisional, sourced from parameter lists, round configs, state files, and investigation reports. - Mechanism and Model-Evolution Ledgers: Records what the campaign has learned about the system (one row per established mechanism with evidence) and verifies which model binary each round ran via git ancestry checks before claiming comparability. - Performance and Sensitivity Figures: Regenerates multiround top-50 biomass overlays and Morris mu* sensitivity comparisons per model backend, with documented footguns such as screening contamination, stale indices files, and partial-ensemble caveats. - Use Case: After round R3 of an EcoSIM calibration completes, run this Skill to produce the R1-R3 parameter ledger, confirm R3's binary ancestry, and refresh the multiround comparison figures before writing the round report. ## Quick Start Ask the agent to compare all completed calibration rounds for the current case and regenerate the cross-round parameter ledger and multiround figures before the round report.

Frequently Asked Questions about compare-calibration-rounds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare calibration rounds in A2MC?▼

Run the compare-calibration-rounds workflow, which builds a cross-round parameter ledger from each round's parameter lists, configs, state files, and investigation reports, then regenerates the multiround performance and sensitivity figures. It is required before every round report, including the first.

Why is cross-round comparison required for the first calibration round?▼

The first round has no prior rounds for figures, but the parameter, mechanism, and model-evolution ledgers still have content and form the baseline later rounds are checked against. Skipping it forces later rounds to reconstruct round one's history from logs.

Does this comparison work for models other than FATES?▼

Yes, the parameter ledger is model-agnostic and works for any onboarded model such as EcoSIM, PFLOTRAN, or ATS. Only the figure-producing backend differs per model, resolved via tools/describe_mode.py or the A2MC_MODEL setting.

Why does the screening step include unexpected experiment cases?▼

screen_ensemble.py matches any case number, so out-of-range experiment cases in a shared extract directory get swept in and can rank as best. Pass --max-case-num with the ensemble maximum for cross-round comparisons and verify the set count in the results file.

Can Morris sensitivity be compared for a partially complete ensemble?▼

No, Morris mu* is unreliable until the ensemble is reasonably complete. Include partial rounds in the biomass top-N figure with a label, but exclude them from the sensitivity overlay until a full Y-matrix rebuild and Morris re-run.

How is model comparability across rounds verified?▼

The skill reads the model_change_ledger in config/calibration_rounds.yaml and verifies ancestry with git merge-base --is-ancestor against the commit each round's binary actually ran. If the ledger is absent, the report must state the comparison is unverified on the model axis.