# Configuration fields Configuration fields determine how Providentia behaves during a run using a configuration file. Below is a full list of all available parameters organised by mode. These fields can also be set via command line arguments, for more details, see the [Command line configuration page](Command-line-configuration). ## Common parameters Some of these fields are required depending on the mode. If a parameter required by a given mode is missing, Providentia will fail. | Parameter | Required in | Description | | ------ | ------ | ------ | | network | Dashboard, Report, Interpolation | Network you want to load observations from. Can be multiple (e.g. `CAPMoN, EBAS`). Adding a wild card (\*) is going to expand to certain variables (vconcaerobin* → vconcaerobin1, vconcaerobin2, etc.). | | species | All modes | Species to load. Can be multiple (e.g. `sconco3, sconcno2`). Dictated by GHOST. See the [Available Species](Available-species) page for options. | | resolution | All modes | Temporal resolution of the observations you want to load (e.g. `3hourly`). | | start_date | All modes | Comparison start date in YYYYMMDD format (e.g. `20170101`). | | end_date | All modes | Comparison end date in YYYYMMDD format (e.g. `20180601`). | | model | Dashboard, Report, Interpolation | ID of model. The model IDs can be mapped to different names by adding a list of alternative names after the model IDs (e.g. `mod1, mod2 (altmod1, altmod2)`). After interpolation model IDs will consist of 3 separate strings [ID-domain-ensemble]. The domain and ensemble | | model_resolution | Optional | Model resolution if different from observations | | domain | Optional | Domain of the model. Can be multiple. | | ensemble | Optional | Ensemble member number or ensemble statistic of the model. defaults to all members available. Can be multiple. | | forecast | Optional | Controls how forecast data is handled. Can be multiple (e.g. `day`, `daily`, `combined`). If wanting to limit to specific forecast days, then add the forecast day to the option, (e.g. `day1`, `daily2`, `combined3`). Different options cannot be mixed however (i.e. `day` options cannot be set with `daily` or `combined` options). This variable must be set to a valid value when performing interpolation for forecast data to be interpolated.| | filter_species | Optional | Filter read species by other species data within a data range. The first value set is the lower bound to filter by, and the second value the upper bound. Place a sign before each bound value to inform if the filter should be inclusive or exclusive of the bound, e.g. `<` or `<=`. If not wishing to set either the lower or upper bounds, a `:` can be used. Optionally, a fill value can also be given as a third value to impose what the filtered data is set to, by default this is `NaN`. Multiple filters can be set together separated by a comma (e.g. `network1:species1 (>lowerlim, <=upperlim, fillvalue), network2:species2 (:,