SETTING UP

1. Starting from an existing configuration

./makenemo -n CLASS_TEST -r ORCA2_ICE_PISCES -m gfortran_local  |& tee compile_log.txt

2. Creating a completely new configuration (before running the model)

From NEMO version 4.0 there are two ways to build configurations from scratch. The appropriate method to use depends largely on the target configuration. Method 1 is for more complex/realistic global or regional configurations and method 2 is intended for simpler, idealized configurations whose domains and characteristics can be described in simple geometries and formulae.

 

Option 1: Create and use a domain configuration file (Using DOMAINcfg tool)

 

This method is used by each of the reference configurations so that downloading their input files linked to their description can help.

 

All the domain information for your new configuration will be contained within a netcdf file called domain_cfg.nc which you will need to create and place in the ./cfgs/TEST/EXP00 sub-directory. Firstly though, ensure that your configuration is set to use such a file by checking that

ln_read_cfg = .true.

in ./cfgs/MY_NEW_CONFIG/EXP00/namelist_cfg

 

There are two options for creating a domain_cfg.nc file:

• Users can use tools of their own choice to build a domain_cfg.nc with all mandatory fields.
• Users can adapt and apply the supplied tool available in ./tools/DOMAINcfg. This tool is based on code extracted from NEMO version 3.6 and will allow similar choices for the horizontal and vertical grids that were available internally to that version. See tools for details.

#########README#######
================================
= **HOW TO COMPILE**
================================
The DOMAINcfg tool can be compiled using the maketools script in the NEMOGCM/TOOLS directory as follows:
:::::::::::::::::::::::::::::::::
./maketools -m $ARCH -n DOMAINcfg
:::::::::::::::::::::::::::::::::
where $ARCH indicates the arch file to be used from the directory NEMOGCM/ARCH. 

DOMAINcfg compiled will create "make_domain_cfg.exe" executable script (the main routine of this tool is make_domain_cfg.f90)

================================
= **HOW TO RUN**
================================
just run :
:::::::::::::::::::::::::::::::::::::::::::::::::
mpirun -np 1 ./make_domain_cfg.exe
:::::::::::::::::::::::::::::::::::::::::::::::::
NOTA: it can be run in multiproc mode, but in output there will be domain_cfg_00xx.nc files

================================
= **HOW TO USE**
================================
1) copy in DOMAINcfg  directory namelist_cfg all settings (that you had in 3.6_stable) of the configuration for which you want prepare domain_cfg.nc file
IMPORTANT : keep the namelist_ref committed inchanged. !!!

NEW OPTION ln_e3_dep in the namelist_ref:
till nemo_v3.6_stable e3 were done like an analytical derivative of depth function
now  e3=dk[depth] in discret sens

If you want to create same e3[tuvw] like 3.6 you've to use "ln_e3_dep=.false."

 ln_e3_dep   = .true.    ! =T : e3=dk[depth] in discret sens.
   !                       !      ===>>> will become the only possibility in v4.0
   !                       ! =F : e3 analytical derivative of depth function
   !                       !      only there for backward compatibility test with v3.6
   !

2) copy in DOMAINcfg directory same input files (of related configuration) required in v3.6_stable.

DOMAINcfg package is EXACTLY what does exist in NEMO version 3.6 to define a model domain (both domain related namelist and initialization).
DOMAINcfg tool creates a netcdf file "domain_cfg.nc" containing all the ocean domain informations required to define an ocean configuration,
these files are :
          
    domain size
    domain characteristics (periodic)
    horizontal mesh
    Coriolis parameter
    depth and vertical scale factors

FOR EXAMPLE 
- for ORCA2 : 
            coordinates.nc
            bathy_meter.nc
            bathy_level.nc
            domain_def.xml
            field_def.xml
            iodef.xml

 

Option 2: Adapt the usr_def configuration module of NEMO for your own purposes

 

*  Tips
If you have a problem with “EMPave_old.dat”

0  0.0000000000000000E+00  0.0000000000000000E+00

3. NEMO Reference configuration inputs

Input archives for running the configurations included in NEMO 4.0.1 |

• AGRIF_DEMO: AGRIF_DEMO_v4.0.tar and ORCA2_ICE_v4.0.tar
• AMM12: AMM12_v4.0.tar
• C1D_PAPA: INPUTS_C1D_PAPA_v4.0.tar
• ORCA2_ICE_PISCES: ORCA2_ICE_v4.0.tar and INPUTS_PISCES_v4.0.tar
• ORCA2_OFF_PISCES: ORCA2_OFF_v4.0.tar and INPUTS_PISCES_v4.0.tar
• ORCA2_OFF_TRC: ORCA2_OFF_v4.0.tar
• ORCA2_SAS_ICE: ORCA2_ICE_v4.0.tar and INPUTS_SAS_v4.0.tar
• SPITZ12: SPITZ12_v4.0.tar 

 

Link for downloading initial data for NEMO

https://zenodo.org/records/3386310#.YeYndnUza-Y

NEMO Reference configurations inputs

* Tips
Information of namelists
namelist_*_cfg : configured namelist
namelist_*_ref : origin namelist

🌊 How to run

cd **TEST**/EXP00
mpirun -np 32 ./nemo

⇒ Going into ocean.output and searching for E R R O R