EPIC

Runs the EPIC 1102 agro-ecosystem model under Wine with copy-first Fortran input builders and output parsers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Running the EPIC 1102 crop and soil model requires correctly assembling fixed-width Fortran input files, converting weather and soil data into exact units, executing a Windows binary under Wine, and parsing annual output files — a process where a single misaligned column or wrong unit silently produces invalid results. ## Core Features & Use Cases - End-to-end pipeline tools: 16 Python tools cover site setup (.SIT), soil profiles from HWSD (.SOL), operation schedules (.OPC), CMFD/NASA POWER forcing conversion (.DLY/.WP1/.WND), control files, Wine execution, and output parsing (.ACY/.ANN to CSV). - One-command quickstart: quickstart.py chains crop calendar lookup, NPKGRIDS fertilizer rates, SPAM yield targets, input building, and the Wine run from just latitude, longitude, crop, and years. - Diagnostic recovery: 32 symptom-diagnosis-remedy triplets in diagnostics/triplets.yaml plus a preflight check that verifies the binary, Wine, templates, and imports before any run. - Use Case: Simulate 20 years of rainfed maize at a Northeast China site, then score the simulated yield against GDHY gridded observations using the dag.yaml validation contract with the correct moisture-basis conversion. ## Quick Start Ask the agent to run the EPIC quickstart for your site, for example: run EPIC for corn at latitude 44.25, longitude 125.25 from 1995 to 2016 with CMFD forcing and dryland management.

Frequently Asked Questions about EPIC

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

FAQPage Schema
How do I run the EPIC crop model for a new site?▼

Use tools/quickstart.py with latitude, longitude, crop, and start/end years. It builds the .SIT, .SOL, and .OPC files, converts CMFD forcing, writes control files, runs EPIC under Wine, and parses the yield output in one command.

How do I convert CMFD weather data to EPIC input format?▼

Use tools/convert_forcing_to_epic.py, which reads the 3-hourly CMFD store and writes fixed-width .DLY, .WP1, and .WND files. It converts precipitation from kg m-2 s-1 to mm, temperature from Kelvin to degC, and radiation from W m-2 to MJ m-2 day-1.

Can EPIC 1102 run on Linux?▼

Yes, EPIC 1102 is a Windows console executable that runs on Linux through Wine. All input files must be present in the current working directory when the binary launches, and the preflight_check.py script verifies Wine and the binary before running.

Why does my EPIC run produce zero or tiny yields?▼

Common causes are wrong crop or equipment codes in the .OPC file, Kelvin temperatures passed as degC, or precipitation left in kg m-2 s-1. Check diagnostics/triplets.yaml first, which maps 32 known failure symptoms to diagnoses and remedies.

How should EPIC simulated yield be compared to gridded observations like GDHY?▼

Run tools/resolve_obs_shape.py before scoring to bind the observation to the correct obs_shape in dag.yaml. For regional aggregates the verdict metric is PBIAS only, and EPIC dry-matter yield must be converted to market moisture using the registered basis (w = 0.14 for China maize).

What are the limitations of the EPIC model setup?▼

EPIC simulates a single homogeneous field-scale hydrologic unit, not spatially distributed grids, and its .ANN runoff column excludes deep percolation and lateral flow. Fixed-management runs cannot reproduce technology trends in regional yield statistics, so detrended metrics are required.