JULES v4.2 details
JULES version 4.2 is the first release where all development has taken place in the Met Office collaboration repository. On the whole, this has been a success, with module leaders beginning to use the Trac system to track and approve developments in their areas.
The JULES vn4.2 release consists of 35 tickets from 13 authors across 39 commits.
- TRIP and RFM river routing (see jules_rivers.nml)
- Incorporation of widely used fire risk indices (see fire.nml)
- New soil thermal conductivity model that is more appropriate for organic soils (see
- Addition of “bedrock” column beneath the soil column, in which only thermal diffusion occurs (see
- New canopy radiation scheme in which the nitrogen follows an exponential decay (see
- Updates to trait PFTs (see
l_trait_phys) to ensure that the dynamic and equilibrium solutions for vegetation fraction are equivalent
- Crop model now conserves carbon
- Added flag to force the model grid to be 1D (see
- Several new diagnostics added (see JULES Output variables)
- New rose-stem regression tests added
- All rose-stem tests migrated to use NetCDF and
- Retirement of several include files
- Removal of logging namelist - output location should now be controlled using pipes (i.e.
1>/my/file 2>&1) or features of your
- Additional consolidation of shared (i.e. standalone and UM) control and initialisation routines
- Optimisation of
leaf_limits, resulting in ~20% speedup for
- Bug in calculation of
- Memory overwriting bug in TRIFFID
- Differing error message lengths in UM
hconsnow passed to the snow scheme instead of
- Several bug fixes for IMOGEN
- Patch to enable collective access for parallel NetCDF in NetCDF 4.2 onwards
ksz(npnts,nshyd)) - this only affects runs where the soil properties vary for each layer
- Correction to the accumulation of
g_leaf_phenin-between calls to TRIFFID
Full details of the tickets committed for JULES vn4.2 can be found on the collaboration repository Trac system.
Building and running JULES v4.2 is described in the JULES User Guide.
Developers should use the collaboration repository - contact Matt Pryor for access (firstname.lastname@example.org).