Generate model-specific run configuration files for one or more PEcAn runs
Source:R/runModule.run.write.configs.R
runModule.run.write.configs.RdThis function serves as the orchestration layer between PEcAn workflows and
the config-writing machinery. It generates appropriate input designs
(ensemble and/or SA) if not provided. For MultiSettings, it generates designs once
from the first site then shares across all sites for consistent sampling. Finally,
it delegates to run.write.configs for actual config generation.
The input design determines how parameter samples and input files (met, soil,
etc.) are coordinated across runs. Ensemble designs typically use random or
quasi-random sampling, while SA designs hold non-parameter inputs constant
(OAT methodology).
Arguments
- settings
a PEcAn Settings or MultiSettings object
- overwrite
logical: Replace config files if they already exist?
- input_design
Optional. Input design data.frame linking parameter draws and sampled inputs across runs. Include a `param` column whose values select rows from `trait.samples`/`ensemble.samples`, plus optional columns named for `settings$run$inputs` tags (e.g. `met`, `soil`) with indices into each input's `path` list. Can be:
A single data.frame (interpreted as ensemble design)
NULL to auto-generate designs based on settings
Usually generated by `generate_joint_ensemble_design()` for ensemble runs or `generate_OAT_SA_design()` for sensitivity analysis.