BIOME_BGC

Runs BIOME-BGC 4.2 simulations of daily carbon, nitrogen, and water fluxes for natural ecosystems.

155|6|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/lzwei196/KISS-Knowledge-Infrastructure-for-Scientific-Simulation --skill biome-bgc-lzwei196
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BIOME_BGC
Source: https://github.com/lzwei196/KISS-Knowledge-Infrastructure-for-Scientific-Simulation/tree/main/models/BIOME_BGC
Command: npx skills add https://github.com/lzwei196/KISS-Knowledge-Infrastructure-for-Scientific-Simulation --skill biome-bgc-lzwei196

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Running the BIOME-BGC terrestrial biogeochemistry model correctly requires deep operational knowledge: strict unit conventions (precipitation in cm not mm, VPD in Pa not kPa), a fragile keyword-section .ini format, and mandatory multi-century spinup before carbon fluxes are meaningful. This Skill packages that expertise so an AI agent can prepare inputs, execute spinup and normal runs, parse outputs, and recover from the model's known silent failure modes. ## Core Features & Use Cases - End-to-end pipeline tools: Six Python tools generate site .ini files, map AVHRR land cover to plant functional types and .epc files, convert VIC/CMFD forcing to BIOME-BGC meteorological format, run spinup with convergence monitoring, execute normal simulations, and parse daily/annual outputs. - Diagnostic recovery: 25+ diagnostic triplets map symptoms (e.g., GPP 10x too high, zero GPP, spinup never converging) to diagnoses and validated remedies, covering the model's most dangerous silent unit errors. - Validation and coupling guidance: Dag-based output definitions with cited validation conventions (NSE, PBIAS pass-bands), FLUXNET comparison guidance, and rules for coupling with VIC hydrology and LDNDC cropland models without double-counting ET. - Use Case: Simulate forest carbon budgets for a basin by running spinup then a transient run per grid cell, producing FLUXNET-comparable GPP, NPP, NEE, ET, LAI, and soil carbon outputs. ## Quick Start Ask the agent to run the bundled Missoula ENF example by first executing preflight_check.py, then running the spinup and normal BIOME-BGC simulations and parsing the daily output into an annual carbon summary.

Frequently Asked Questions about BIOME_BGC

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

FAQPage Schema
How do I run a BIOME-BGC simulation from VIC forcing data?

Convert VIC forcing to BIOME-BGC met format with convert_forcing_to_bgc.py, generate the .epc with select_ecophysiology.py, build spinup and normal .ini files with generate_site_ini.py, then run run_bgc_spinup.py followed by run_bgc.py and parse results with parse_bgc_output.py.

Why is BIOME-BGC spinup required before normal runs?

Spinup runs 1000-6000 model years to bring soil carbon and nitrogen pools to steady state. Without it, NEE estimates are dominated by initial-condition artifacts for centuries, making carbon flux results scientifically meaningless.

Why is my BIOME-BGC GPP about 10 times too high?

The model expects precipitation in cm/day, not mm/day. Feeding millimeter values from CMFD, MSWX, or VIC silently inflates water input and GPP roughly tenfold; divide precipitation by 10 or use convert_forcing_to_bgc.py.

Can BIOME-BGC simulate cropland or agricultural systems?

No. BIOME-BGC covers natural vegetation only (AVHRR classes 1-10: forests, grasslands, shrublands). Cropland cells should use LDNDC or DSSAT, and basin budgets aggregate both models by land cover.

Why does BIOME-BGC produce zero GPP every day?

The day length column in the met file is zero or missing. Day length in seconds must be computed astronomically from latitude and day-of-year using compute_daylength(), since forcing datasets like CMFD do not provide it.

How is BIOME-BGC output validated against observations?

Daily GPP, NEE, and ET are compared against FLUXNET eddy-covariance towers using NSE and PBIAS with cited pass-bands in validation_convention.yaml; LAI and GPP can also be compared spatially against MODIS products.