1. Overview of the trial CO9 AMM15 NEMO 4 run
2. Reference 3.6 Long Run AMM15
   1. Forcing Data
      1. Open Boundaries
      2. Surface Boundaries
      3. Tides
   2. Data Archive
3. Initial 402 run covering 1990-onward
4. 404 runs 2004-2014 Runs
   1. P0.0 CO9 AMM15 NEMO 404 (u-cb676) (done)
   2. With FES Tides (u-cb907)
      1. P0.1a CO9 AMM15 NEMO 404 With FES Tides (u-cb907) (done) This had issues with Love Number and Equilibrium tide
      2. P0.1b CO9 AMM15 NEMO 404 With FES Tides (u-ce198) Corrected version
   3. P0.2 CO9 AMM15 NEMO 404 Baltic SSH ON (u-cc161)
   4. P0.3 CO9 AMM15 NEMO 404 Baltic SSH OFF (u-cc447) (done)
   5. P0.4 CO9 AMM15 NEMO 404 Change EOS to 2010 (u-cc321) (short run just as sanity check)
   6. P0.5 CO9 AMM15 NEMO 404 Add Nicos Baltic Bdy
      1. P0.5.a Atlantic 3D UV zerograd,Tra FRS (u-cc606), this is unstable
      2. P0.5.b Atlantic 3D UV specified,Tra specified,LN_FULL_TRUE (u-cd097)
      3. P0.5.c Atlantic 3D UV specified,Tra FRS ,LN_FULL_TRUE (u-cd223)
   7. P0.6 CO9 AMM15 NEMO 404 update GLS options (u-cc776) (done)
   8. P0.7 CO9 AMM15 NEMO 404 ERA5 (u-cc945) (done)
      1. P0.7b CO9 AMM15 NEMO 404 ERA5 NCAR (u-cc708)
   9. P0.8 CO9 AMM15 NEMO 404 ERA5+update GLS options (u-cd400) (done)
   10. All combined
       1. Unstable P0.9a CO9 AMM15 NEMO 404 ERA5+update GLS options + Atlantic 3D UV specified,Tra specified,LN_FULL_TRUE +FES2014 (u-cd513)
       2. P0.9b CO9 AMM15 NEMO 404 ERA5+update GLS options + Atlantic 3D UV specified,Tra specified,LN_FULL_TRUE +TPXO (u-cd611)(_done)
5. NATL12 BDYS Operrestart 2016,2017
   1. NATL ATLANTIC BDY, ERA5 SBC, OLD GLS P0.0_OP_FORCE( u-cd014, done)
   2. NATL ATLANTIC BDY, ERA5 SBC, NEW GLS P0.0_OP_FORCE_GLS( u-cd101, done)
   3. NATL ATLANTIC BDY, ERAI SBC, OLD GLS P0.0_OP_FORCE_ERAI (u-cd044, done)
   4. GLOSEA TS BDY, Barotropic NATL ATLANTIC BDY, ERA5 SBC, OLD GLS P0.0_OP_FORCE_GLOSEA_TSBDY( u-cd224, done)
   5. NATL ATLANTIC BDY, ERA5 SBC, OLD GLS P0.0_OP_FORCE NCAR BLK FORMULAE ( u-cd399, done)

We start from a base of replicating the NEMO3.6 AMM15 run documented in the GMD paper:

https://doi.org/10.5194/gmd-11-681-2018

"AMM15: a new high-resolution NEMO configuration for operational simulation of the European north-west shelf Graham et al. 2018"

This long run was split into 3 sections covering 1985-1989(spin up), 1990-2003, 2004-2014 the split was representative of changing of GLOSEA runs used for the open boundaries on the Atlantic.

we re-use in our base NEMO4 runs the exact same input data as used in the NEMO 3.6 run. Specifics follow

• Atlantic: Barotropic U,V, SSH, TS Rims 15 from GLOSEA data sets SPJZA and SPJZD Note no baroclinic UV not even zerograd.
• Baltic: IOW GETM derived data covers up until 2014

• ERAI projects data contains up to 2014, but have extended to 2017.

TPXO derived data with just 11 constituents: M2, S2, N2, K2, K1, O1, P1, Q1, M4, MS4, MN4

The relevant data is under devfc suites we are interested in start in 1990:

• mi-an561_1990
  • 1989-12-30 - 2003-12-31
• mi-ao113_2004
  • 2003-12-30 - 2014-12-31

We have an initial 402 run based on the suite, this was not run on monsoon and archived to devfc:

• u-cb854 (archived under :/devfc/rosie_U-BP634_BASED_TEST_NEMO4.0.2_CO7_MATCH_SAFEBUILD_TIDE_V1_GLS_EN_BUG_FIX_HALF_MASK)
  • Started from restart of mi-an561_1990 in the 10th of January 1990 (restarts were dumped in that run on mod 10 days)
  • Has run with a rdt of 60 seconds up to 2008-04-19 at time of writing

From this 402 run we have derived 404 runs to represent our based 404 AMM15 p0 run starting from January-1st 2004.

Note the following 404 suites are all run on monsoon and are archived under: :/crum/x{suite_id}

This is as close to the reference 3.6 suite as possible at NEMO 404. It starts from the 402 run from January 1st 2004

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/b/6/7/6/trunk/app/nemo_cice/rose-app.conf

(may extend this over 2015 gap year to start of operational data in 2016)

The first run below P0.1a had some problems. The First was that the Love number was not specified in the namelist. In the older code it was hardwired as 0.7. In the new code it needs to be read in from the namelist. If it is not set it is defaulted to 0. The second problem concerns the equitide for K1. It appears that it has a negative value, which appears to degrade the phase considerably. If we revert it to the original positive value it performs much more as expected. In P0.1b the experiment is repeated with these corrections.

This suite picks up on Nico's code and has 34 tidal constituents.

: SA,SSA,MM,MF,MTM,MSF,MSQM,K1,O1,Q1,P1,S1,J1,M2,N2,S2,K2,L2,T2,R2,MU2,2N2,MKS2,LA2,EPS2,M3,M4,M6,M8,N4,S4,MN4,MS4

Note this code also allows for the specification of the boundary SSH to be used or not. The Operational suite also has this option and chooses not to apply SSH on the Baltic boundary. In this suite we only test the Addition of tides not the switching no or off of the Baltic

This run crashed with checker-board pattern in velocities during 20070301 It was restarted with reduced time step of 80 s instead of 90 s and that month remains stable. Will see how long it remains stable at this time step.

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/b/9/0/7/trunk/app/nemo_cice/rose-app.conf

This is as in P0.1a but we have update the code now are revision number 14746. This brings in the K1 equilibrium correction to the sign.

It also sets the Love number in the namelist. In particular, it is set as 0.69 as set out by Nico in his FES2014 trials.

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/e/1/9/8/trunk/app/nemo_cice/rose-app.conf

This run uses the updated Tide code and the option to switch on/off SSH BDYS But in this case the Baltic SSH bdy is still on . In effect it is only difference from P0 in testing the updated tidal code with TPXO forcing instead of FES

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/c/1/6/1/trunk/app/nemo_cice/rose-app.conf

This run is the same as p0.2 except it turns the baltic SSH OFF.

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/c/4/4/7/trunk/app/nemo_cice/rose-app.conf

This is exactly the same as P0.0 but we change the EOS used in the namelist. This did not change the initial state used form pot temp to conservative temperature nor practical salinity to absolute. Likewise it did not update the Boundary conditions

It only changes the namelist eos option to eos2010. It in effect is a functional test rather than an absolute test.

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/c/3/2/1/trunk/app/nemo_cice/rose-app.conf

Set of experiments to test Nico's Baltic boundaries, Note Atlantic boundary options are also changed hence the set.

This run is similar to P0.0 but uses Nicos Baltic boundary condition. Nico modified the bathymetry, and thus we need to generate a domain cfg file based on that bathymetry as we do not have the config file.

We then interpolated the 402 2004-01-01 restart file to this domain.

The initial month is ran with rdt=80 to make sure it stays stable for the initial interpolation.

Nico uses 3D U and V on the Baltic boundary, In fact he also uses them on the Atlantic boundary. But here we want to isolate just the effect of the Baltic, We do however use the zerograd option to reduce w velocities as in the operational run.

Nico uses specified instead of FRS on the Atlantic but here we keep it as FRS as in the operational run

This particular configuration of Atlantic boundaries was unstable as so we have a b run where we use conditions as set **in Nico's original experiment. **

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/c/6/0/6/trunk/app/nemo_cice/rose-app.conf

This run is is as in P0.5.a but the Atlantic boundaries are changed. The 3DUV boundaries are wit the specified option instead of zerograd, the tracer Atlantic boundaries are with specified instead of FRS.

This model run appears stable.

We then interpolated the 402 2004-01-01 restart file to this domain.

https://code.metoffice.gov.uk/svn/roses-u/c/d/0/9/7/trunk/app/nemo_cice/rose-app.conf

This run is is as in P0.5.b but the Atlantic boundaries are changed. The 3DUV boundaries are with the specified option, but the tracer Atlantic boundaries are with FRS instead of specified.

The specified boundaries make quite large changes. We'd liek to isolate that change alone. Also would be nice to isolate changes due to 3D UV alone.

We then interpolated the 402 2004-01-01 restart file to this domain.

https://code.metoffice.gov.uk/svn/roses-u/c/d/2/2/3/trunk/app/nemo_cice/rose-app.conf

This run is the same as P0.0 except that we use a set up updated options to GLS.

https://code.metoffice.gov.uk/svn/roses-u/c/c/7/7/6/trunk/app/nemo_cice/rose-app.conf

Change in GLS options are as below

Note there was also the option to change nn_bc_surf from 1 to 0 that is from Neumann to Dirichlet but it proves unstable at the given time step so had had to revert to Neumann.

This is the same as P0.0 but switches to using ERA5 sufrface fluxes.

Note the TYPE of core bulk forcing is also changed to ECMWF.

• ln_NCAR=.true. --> False !"NCAR" algorithm (Large and Yeager 2008)
• ln_ECMWF= .false. --> True ! "ECMWF" algorithm (IFS cycle 31)

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/c/9/4/5/trunk/app/nemo_cice/rose-app.conf

Exactly as PO7 but with NCAR BLK FORCING as has been used to date with ERAI forcing.

• ln_NCAR=.true. --> True !"NCAR" algorithm (Large and Yeager 2008)
• ln_ECMWF= .false. --> False ! "ECMWF" algorithm (IFS cycle 31)

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/d/7/0/8/trunk/app/nemo_cice/rose-app.conf

This is a combination of P0.6 and P0.7, that is to both change the GLS options and the SBC to ERA5.

It has been found in shorter runs that changing to ECMWF bulk formulae substantially changes stratification, in the opposite direction to the changes from GLS. Nico used both these changes in hiss AMM15 trial runs and it might be required to use both to have sensible stratification.

NEMO_RUN options in details under:

https://code.metoffice.gov.uk/svn/roses-u/c/d/4/0/0/trunk/app/nemo_cice/rose-app.conf

so we have a separate run with TPX but all the other changes added (run b)

This Run combines ERA5+GLS (P0.8) with New baltic bdys using specified TS, UV 3D Both Atlantic and Baltic and uses FES2014 tides this run should be analogous to all the changes brought in by NICO. It turned out to be unstable to run be is exactly the same but reverting tides to TPXO which appears more stable

https://code.metoffice.gov.uk/svn/roses-u/c/d/5/1/3/trunk/app/nemo_cice/rose-app.conf

This Run combines ERA5+GLS (P0.8) with New baltic bdys using specified TS, UV 3D Both Atlantic and Baltic and uses TPXO tides this run should be analogous to all the changes brought in by NICO except for the tides

https://code.metoffice.gov.uk/svn/roses-u/c/d/6/1/1/trunk/app/nemo_cice/rose-app.conf

Here we have a series of short runs spanning 2016,2017 (runs with purely oper forcing also cover 2018 Note the default Atlantic boundaries are from NATL12 (North Atlantic 1/12th degree) We pick up on the ERA5 data for this period as used in the op suite and a restart for JAN 02 2016.

We run with existing GLS options and those proposed by Maria. We run with ERAI forcing as in the longer runs. We also have a run using GLOSEA TS data for the boundaries. Yet to do full run with Barotropic GLOSEA data)

https://code.metoffice.gov.uk/svn/roses-u/c/d/0/1/4/trunk/app/nemo_cice/rose-app.conf Starts from operational restart 20160101 Uses same settings as in P0.0 BUT uses operational SBC and BDY forcing:

Completed (2016,2017,2018)

https://code.metoffice.gov.uk/svn/roses-u/c/d/1/0/1/trunk/app/nemo_cice/rose-app.conf Starts from operational restart 20160101 Uses same settings as in P0.0_OP_FORCE BUT uses update GLS options:

Completed (2016,2017,2018)

https://code.metoffice.gov.uk/svn/roses-u/c/d/0/4/4/trunk/app/nemo_cice/rose-app.conf Starts from operational restart 20160101 Uses same settings as in P0.0_OP_FORCE BUT uses uses ERAI SBC instead of ERA5

Completed (2016,2017) [ don't have 2018 ERAI data to hand]

https://code.metoffice.gov.uk/svn/roses-u/c/d/2/2/4/trunk/app/nemo_cice/rose-app.conf Starts from operational restart 20160101 Uses same settings as in P0.0_OP_FORCE BUT uses uses GLOSEA TS data on the open Atlantic bdy

Completed (2016,2017) [ no GLOSEA data for 2018 ]

https://code.metoffice.gov.uk/svn/roses-u/c/d/3/9/9/trunk/app/nemo_cice/rose-app.conf Starts from operational restart 20160101 Uses same settings as in P0.0 BUT uses operational SBC and BDY forcing AND uses NCAR BLK formula not ECMWF

Completed (2016,2017,2018)

Just a quick replication of Figure 6 from the original CO7 GMD paper against profiles:

• 2004-2014 JJA Outer Shelf
• 2004-2014 JJA Northern North Sea
• 2004-2014 JJA Nowegian Trench
• 2004-2014 DJF Outer Shelf
• 2004-2014 DJF Northern North Sea
• 2004-2014 DJF Nowegian Trench