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.