The cn_rnf variable was hardwired in namelist_cfg_template to use the JRA_RIVERS forcing.
When amending the ln_rnf_new variable in runscript*slurm to .FALSE., cn_rnf should have been automatically updating to use the runoff_1m_nomask.nc forcing, but was not.
The runscript*slurm files have been updated (for ARCHER2, but not ANEMONE), and so has the namelist_cfg_template (for v4.0.4, 4.2.1 and 4.2.2). The hardwiring has been removed and the assignment of the namelist_cfg variable from the template now follows the approach used for other variables.
The cn_rnf variable was hardwired in namelist_cfg_template to use the JRA_RIVERS forcing.
When amending the ln_rnf_new variable in runscript*slurm to .FALSE., cn_rnf should have been automatically updating to use the runoff_1m_nomask.nc forcing, but was not.
The runscript*slurm files have been updated (for ARCHER2, but not ANEMONE), and so has the namelist_cfg_template (for v4.0.4, 4.2.1 and 4.2.2). The hardwiring has been removed and the assignment of the namelist_cfg variable from the template now follows the approach used for other variables.