offline-testing-workflow

Designs, launches, and analyzes FATES parameter-sweep experiments on HPC Morris base cases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running ad-hoc parameter-sweep experiments on top of an A2MC Morris calibration ensemble often leads to duplicated plans, contaminated ensemble outputs, unverified parameter files, and uninterpretable results. This Skill codifies a reproducible 12-step pipeline so each hypothesis test is falsifiable, isolated, and feeds verified findings back into the knowledge base. ## Core Features & Use Cases - Prior-plan and literature grounding: Searches dev_logs/ana_logs for existing experiment plans and runs a focused literature plus satellite-data review before designing variants. - Falsifiable variant design: Builds variant matrices with a control (V0), a falsifiability variant, and pre-committed quantitative thresholds, then generates and verifies per-variant FATES parameter files. - Isolated HPC submission and analysis: Uses dedicated output directories, case-suffix naming, pre-flight validation, a V0 reproducibility gate, and a decision tree that injects confirmed results into the knowledge base. - Use Case: A user suspects the clumping_index parameter drives a GPP bias in an ELM-FATES Arctic site; the Skill designs an 8-variant sweep on Morris base case 1304, submits it on HPC, verifies V0 reproduces the baseline NRMSE, and writes a results ana_log with a KB-injection decision. ## Quick Start Ask the agent to design and launch an offline parameter-sweep experiment testing a specific FATES parameter hypothesis on a named Morris base case.

Frequently Asked Questions about offline-testing-workflow

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

FAQPage Schema
How do I run a FATES parameter sweep experiment on HPC?▼

Define a variant matrix of parameter overrides, generate one modified NC parameter file per variant with tools/modify_fates_parameters.py, then submit each variant via create_case.sh with --case-suffix on a Morris base case. Verify the files before submitting and gate analysis on a V0 control reproducibility check.

How do I test a hypothesis about a FATES parameter like clumping_index?▼

Search dev_logs for prior plans, run a literature and satellite-data review to bracket plausible values, then design variants including a control, a falsifiability variant, and pre-committed quantitative thresholds. Analyze results against those thresholds and inject confirmed findings into the knowledge base.

When should I not use the offline testing workflow?▼

Do not use it for full Morris ensemble runs, single-case re-runs, or AI-orchestrated Phase 4/5/6 experiments inside a calibration cycle, since the orchestrator already handles those. It is scoped to small experiments of roughly 10 or fewer variants.

Why must experiment cases use --case-suffix instead of new case numbers?▼

Case numbers above the Morris range share the Morris case-name pattern, contaminating the auto-monitor and Morris screening tools. The case-suffix keeps the variant name between PrescP and _TRANS_, so Morris analysis naturally excludes experiment cases.

What happens if the V0 control does not reproduce the baseline?▼

Stop and investigate before trusting any variant results. A V0 mismatch indicates build, environment, or seed drift between the Morris run and the experiment, so variant signals cannot be distinguished from infrastructure drift until it is resolved.

Why does parameter file verification matter before HPC submission?▼

Generator bugs such as 0-based versus 1-based PFT index confusion silently modify the wrong PFT. A 30-second programmatic and ncdump check catches this before submission, avoiding wasted compute across dozens of jobs.