DayCent

Runs the DayCent DDcentEVI rev491 binary to simulate soil carbon, plant production, and trace-gas fluxes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Running the DayCent ecosystem model correctly requires deep operational knowledge: fixed-format Century-100 input files, cm/day weather units, a three-stage equilibrium-to-treatment spin-up protocol, and binary output extraction. This Skill packages that expertise so an AI agent can execute real DayCent simulations, validate inputs, and recover from known failure modes without fabricating results. ## Core Features & Use Cases - End-to-end simulation pipeline: Converts CMFD/MSWX/NASA-POWER/FLUXNET forcing into DayCent .wth weather files, builds 13-layer soils.in profiles from HWSD + ROSETTA, runs the equilibrium → base history → treatment chain, and parses .lis/summary.out outputs into tidy CSVs. - Diagnostic recovery: 27 symptom-diagnosis-remedy triplets in diagnostics/triplets.yaml cover known failures such as mm-vs-cm precipitation errors, Kelvin temperatures, and missing site files. - Validation against observations: Maps DayCent outputs (cprodc, NEE, somsc, N2O) to FLUXNET variables with correct sign conventions and cited performance bands. - Use Case: Validate DayCent daily GPP against a FLUXNET2015 tower by converting the site's FULLSET_DD.csv to a .wth file, adapting the Wooster template, running the three-stage protocol, and comparing cprodc against GPP_NT_VUT_REF. ## Quick Start Run python preflight_check.py in this directory, then ask the agent to execute the Wooster quick-start example with run_daycent.py and extract daily cprodc from summary.out.

Frequently Asked Questions about DayCent

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

FAQPage Schema
How do I run a DayCent simulation from scratch?

DayCent runs follow a three-stage protocol: an ACEQ equilibrium spin-up, a base history extending it with -e eq, and a treatment run extending with -e base. The run_daycent.py wrapper chains these stages, and DDlist100_rev491 extracts variables from the resulting .bin archives.

How do I convert FLUXNET data to a DayCent weather file?

Use convert_forcing_to_daycent.py with --source fluxnet and --fluxnet-csv pointing to the site's FULLSET_DD.csv. It reads TA_F, P_F, and SW_IN_F, fills calendar gaps, and writes a .wth file with precipitation in cm/day as DayCent requires.

Why is my DayCent soil moisture saturated every day?

This almost always means precipitation is in mm/day instead of the cm/day DayCent expects, silently making the site ten times too wet. Re-run the forcing converter and verify column 7 of the .wth file is in cm/day.

Can DayCent simulate forest flux tower sites?

Not with the public distribution alone: the bundled WoosterExampleLinux ships a zero-byte tree.100, so the TREE submodel is non-functional. You must obtain a populated tree.100 from CSU NREL or use a grassland parameterization as a flagged surrogate.

How do I compare DayCent output with FLUXNET GPP and NEE?

Use cprodc from summary.out as the daily GPP proxy and the NEE column for net ecosystem exchange. Note DayCent's NEE sign convention is positive for uptake, opposite to FLUXNET, so flip the sign before computing metrics.