A configuration is defined to be “all of the switches and options a user selects when setting up a simulation” and is required for any run of the JULES model ("switches and options" includes driving and ancillary data, i.e. a configuration is intended to be the minimum set of switches, files and other information that would allow someone to uniquely replicate another's model run). For further information, see Configuration management in JULES by Anna Harper JULES_configurations_v2.2_Nov2016-AH2_TM.docx.
Most users start off using one or other of the following configurations:
Recommended for all JULES users. These are routinely maintained and updated as part of each JULES release. These configurations are guaranteed to produce output that is bit-comparable between JULES versions (if the driving and ancillary data are also the same).
|Available via JULES support|
|NOT supported via JULES support.||NOT supported officially, although advice may be requested informally via the JULES community mailing list|
|There are also some example configurations intended for test runs (e.g. Loobos and others mentioned here).||NOT supported for science: these are just meant to get the user up and running with JULES|