Model parameters and xml parameter files
Settings in the ED2 setting file correspond to variables defined in the “ed_data” object. These variables have been lumped into a number of groupings related to their role in the model and the common block memory they are assigned to:
| Misc. Settings | <misc></misc> |
| <ed_misc></ed_misc> | |
| Plant Functional Types | <pft></pft> |
| PFT constants | <pftconst></pftconst> |
| Hydrology | <hydro></hydro> |
| Lapse Rates | <lapse></lapse> |
| Solar Radiation/Light Interception | <light></light> |
| Soils | <soil></soil> |
| Decomposition | <decomposition></decomposition> |
| Patch/Cohort Fusion/Fission | <fusefiss></fusefiss> |
| Disturbance | <disturbance></disturbance> |
| Phenology | <phenology></phenology> |
| Physiology | <physiology></physiology> |
| Additional XML files | <extern></extern> |
Configuration files are encoded in XML format using the above tags. The parser doesn't care about the order or number of tags in the config file. In fact, one must specify one <pft></pft> section per plant functional type. Currently there are a large number of defaults built into the model. The config file is read AFTER all the defaults have been set, so any values not set in the config stay at their default. Within a section, as few or as many values can be set as the user desires. An example of a config file might be:
<?xml version="1.0">
<config>
<ed_misc>
<restart_target_year>1993</restart_target_year>
</ed_misc>
<pft>
<num>5</num>
<name>SouthernPine</name>
<SLA>10</SLA>
</pft>
</config>Since XML can be easily read/written by a large number of programs/languages, the use of XML config files makes it easy to generate “batch jobs” or “ensembles” of runs where parameters can be sampled from, as is done in http://pecanproject.org https://github.com/PecanProject/pecan/tree/master/models/ed
Because they were large tables, each section has been moved to it's own page: