Track and report progress of a request to create and run an EcoSIM case for a site ("create an ecosim run for site US-UMB", "set up and run EcoSIM at <site>"). Records four stages — data preparation, namelist creation, model simulation, and output evaluation — in result/<SITE_ID>/progress.json and PROGRESS.md, derives step status from files and quality reports on disk, and records manual results such as the executable, test run, and evaluation verdicts. Use at the start of such a request, after each stage, and whenever the user asks where a site run stands.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
| Stage | Steps | Detected from |
|---|---|---|
| Data preparation | site_metadata, climate_forcing, atmospheric_chemistry, soil_grid, plant_management, soil_management | <SITE_ID>_ecosim_site.json (location checks, run live if not recorded), <SITE_ID>_ecosim_climate_<first>-<last>.nc and ERA5 quality report (time registration, ZNOONG, tower warnings), climate derivation report (derived chemistry), grid NetCDF and layer validation (run live if not recorded), plant and soil management NetCDF |
| Namelist creation | run_folder, namelist, chronology | result/<SITE_ID>/{input,run_dir}, namelist paths resolving from run_dir/, stop_n equal to EcoSIM get_sim_len of forc_periods |
| Model simulation | executable, smoke_test, full_run | executable file in run_dir/; *.ecosim.h0.*.nc history files in run_dir/ (reported in_progress until the run is confirmed) |
| Output evaluation | target_extraction, benchmark_comparison, evaluation_report | files in result/<SITE_ID>/evaluation/ named *targets*, *comparison*/*benchmark*, *report* |
Statuses: pending, in_progress, done, warning, failed, skipped. A stage is failed if any step failed, done/warning when every non-skipped step is done, pending when none started, else in_progress.
Run from the python-tools repository root.
At the start of the request, initialize the tracker with the request text:
python .agents/skills/ecosim-site-run-tracker/scripts/site_run_tracker.py init \
--site-id US-UMB --request "create an ecosim run for site US-UMB"
After each stage (site inputs generated, run folder created, run finished, evaluation written), rescan and relay changed statuses to the user:
python .agents/skills/ecosim-site-run-tracker/scripts/site_run_tracker.py scan --site-id US-UMB
Record what files cannot show. A manual status is kept across scans; --auto returns the step to detection.
python .agents/skills/ecosim-site-run-tracker/scripts/site_run_tracker.py set --site-id US-UMB \
--step soil_management --status skipped --note "Unmanaged forest"
python .agents/skills/ecosim-site-run-tracker/scripts/site_run_tracker.py set --site-id US-UMB \
--step executable --status done --note "build/<config>/.../ecosim.f90.x (gfortran 14)"
python .agents/skills/ecosim-site-run-tracker/scripts/site_run_tracker.py set --site-id US-UMB \
--step smoke_test --status done --note "20 days, exit 0, no NaN/Inf"
python .agents/skills/ecosim-site-run-tracker/scripts/site_run_tracker.py set --site-id US-UMB \
--step full_run --status done --note "exit 0; 113 years; h0 files to 2021"
Answer status questions from show (or show --json) after a fresh scan.
These scripts rescan the tracker when they finish (creating it if needed), so data-preparation and namelist steps stay current without an explicit scan:
Tools/create_ecosim_climate_forcing.pyTools/create_ecosim_grid_forcing.py.agents/skills/unified-ameriflux-extractor/unified_ameriflux_extractor.py.agents/skills/ameriflux-namelist-generator/scripts/create_site_run_folder.py (also after a failed assembly)They call Tools/run_progress.py, which never fails the calling script; set ECOSIM_PROGRESS_TRACKER=0 to disable. Simulation and evaluation steps still need set, because no tracked script runs EcoSIM or judges its output. Run init --request yourself so the request text is recorded.
full_run done only after confirming the model exited normally and covered the namelist period; history files alone mean the run started, not that it finished.smoke_test done only after a short run exited normally with finite output; it shows the case runs, not that it is scientifically correct.--note; do not reset them to pending to tidy the report.skipped is for steps that do not apply (e.g. soil management at an unmanaged site), not for steps not yet done.result/<SITE_ID>/evaluation/ so they are detected, e.g. ecosim-h0-target-extractor output as evaluation/<SITE_ID>_h0_targets.json.result/<SITE_ID>/
progress.json tracker state (stages, steps, status, source auto|manual, detail, note, evidence, timestamps)
PROGRESS.md rendered summary with open items
input/ site inputs (ameriflux-namelist-generator run-folder layout)
run_dir/ namelist and, after running, EcoSIM output
evaluation/ output-evaluation products
create_site_run_folder.py leaves progress.json and PROGRESS.md at the site root.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Extract EPA/NADP tDEP atmospheric deposition and NADP precipitation chemistry rasters for an AmeriFlux or EcoSIM site. Use when deriving atmospheric chemistry inputs such as NH4, NO3, SO4, Ca, or precipitation pH for EcoSIM forcing workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Extract AmeriFlux BASE-BADM/BIF crop management records into EcoSIM-editable plant-management and soil-management Excel workbooks that can be converted to EcoSIM NetCDF files. Use when asked to derive EcoSIM planting, harvest, fertilizer, or tillage management inputs from AMF *_BIF_*.xlsx or BIF CSV files, especially for crop sites where management details live in GRP_DM_* records and DM_COMMENT fields.
日本語の概要は準備中です。原文の説明を表示しています。
Sort AmeriFlux BASE-BADM BIF variables from Excel or CSV files into observation, management-event, static metadata, and plotting-ready target time-series tables. Use when Codex is asked to sort AmeriFlux BIF variables into time series; organize BADM/BIF variables by date; pivot AMF *_BIF_*.xlsx files by GROUP_ID; output total LAI, leaf mass per area, above-ground biomass, canopy height, fruit yield, or total yield time series; write MATLAB readers for BIF time-series plotting; or prepare dated AmeriFlux site observations and management records for EcoSIM workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Convert AmeriFlux ERA5 half-hourly meteorological CSV files into EcoSIM hourly climate forcing NetCDF files, compare generated forcing against overlapping measured tower meteorology when a FULLSET file is available, and report large biases or errors. Use when preparing or validating EcoSIM climate inputs for AmeriFlux sites, checking ERA5 against in situ records, diagnosing forcing discrepancies, or writing climate-quality reports. For non-AmeriFlux paper sites that need a fresh Copernicus CDS ERA5 point download by longitude/latitude, use era5-cds-point-download first.
日本語の概要は準備中です。原文の説明を表示しています。
Create EcoSIM Fortran namelist files and workable EcoSIM run folders for AmeriFlux site runs from site-specific grid, plant management, climate forcing, and greenhouse-gas inputs. Use when preparing or updating an EcoSIM `.namelist`, run folder, runfolder, run directory, or executable-ready site case for AmeriFlux or FLUXNET sites, especially after generating `*_ecosim_grid.nc`, `*_ecosim_climate_<first>-<last>.nc`, and `*_pft_mgmt.nc` inputs.
日本語の概要は準備中です。原文の説明を表示しています。
Extract AmeriFlux site metadata and map it to EcoSIM JSON variables. Use when a task needs site latitude, longitude, elevation, mean annual temperature, Koppen climate code, or vegetation type for an AmeriFlux site ID or flux-site name.
日本語の概要は準備中です。原文の説明を表示しています。