Coupling Branches

This page provides the FCM links to the branches used in all, or at least most, of the coupling

• vn8.6_jobidTo2Chars: makes the job id two characters rather than one. It means that if I use the same run id for both the senior and junior UM, the run ids can be distinguished by adding a `1' and a `2' to the job id. For example, `./coupleJobs.scr cakdb cakdb nudge' will have senior run id `cakdb1' and junior run id `cakdb2'. There are some lines in src/control/stash/expt_enc.F90 that say the RUN_ID mustn't exceed 5 chars - but doesn't really explain why (I'll probably find out why later).
• vn8.6_take_version2: reads the 2nd version of environment variables (these should be included in Coupling Environment Variables). Mostly editing the arguments in subroutine FORT_GET_ENV and replacing subroutine GET_FILE with GET_FILE_V2, which reads environment variables UNIT<unit number>_2 rather than UNIT<unit number>.
• vn8.6_2UMs: Adding logicals L_OCEAN, L_SENIOR and L_JUNIOR and macros OCEAN, SENIOR and JUNIOR.

Richard's branches

Also of interest is Richard's branches

• vn8.6_UKCA_toychem_interface: his toy chemistry branch