| 1 | ================================ |
|---|
| 2 | = HOW TO COMPILE |
|---|
| 3 | ================================ |
|---|
| 4 | The DOMAINcfg tool can be compiled using the maketools script in the NEMOGCM/TOOLS directory as follows: |
|---|
| 5 | ::::::::::::::::::::::::::::::::: |
|---|
| 6 | ./maketools -m $ARCH -n DOMAINcfg |
|---|
| 7 | ::::::::::::::::::::::::::::::::: |
|---|
| 8 | where $ARCH indicates the arch file to be used from the directory NEMOGCM/ARCH. |
|---|
| 9 | |
|---|
| 10 | DOMAINcfg compiled will create "make_domain_cfg.exe" executable script (the main routine of this tool is make_domain_cfg.f90) |
|---|
| 11 | |
|---|
| 12 | ================================ |
|---|
| 13 | = HOW TO RUN |
|---|
| 14 | ================================ |
|---|
| 15 | just run : |
|---|
| 16 | ::::::::::::::::::::::::::::::::::::::::::::::::: |
|---|
| 17 | mpirun -np 1 ./make_domain_cfg.exe |
|---|
| 18 | ::::::::::::::::::::::::::::::::::::::::::::::::: |
|---|
| 19 | NOTA: it can be run in multiproc mode, but in output there will be domain_cfg_00xx.nc files |
|---|
| 20 | |
|---|
| 21 | ================================ |
|---|
| 22 | = HOW TO USE |
|---|
| 23 | ================================ |
|---|
| 24 | 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 |
|---|
| 25 | IMPORTANT : keep the namelist_ref committed inchanged. !!! |
|---|
| 26 | |
|---|
| 27 | NEW OPTION ln_e3_dep in the namelist_ref: |
|---|
| 28 | till nemo_v3.6_stable e3 were done like an analytical derivative of depth function |
|---|
| 29 | now e3=dk[depth] in discret sens |
|---|
| 30 | |
|---|
| 31 | If you want to create same e3[tuvw] like 3.6 you've to use "ln_e3_dep=.false." |
|---|
| 32 | |
|---|
| 33 | ln_e3_dep = .true. ! =T : e3=dk[depth] in discret sens. |
|---|
| 34 | ! ! ===>>> will become the only possibility in v4.0 |
|---|
| 35 | ! ! =F : e3 analytical derivative of depth function |
|---|
| 36 | ! ! only there for backward compatibility test with v3.6 |
|---|
| 37 | ! |
|---|
| 38 | |
|---|
| 39 | 2) copy in DOMAINcfg directory same input files (of related configuration) required in v3.6_stable. |
|---|
| 40 | |
|---|
| 41 | DOMAINcfg package is EXACTLY what does exist in NEMO version 3.6 to define a model domain (both domain related namelist and initialization). |
|---|
| 42 | DOMAINcfg tool creates a netcdf file "domain_cfg.nc" containing all the ocean domain informations required to define an ocean configuration, |
|---|
| 43 | these files are : |
|---|
| 44 | |
|---|
| 45 | domain size |
|---|
| 46 | domain characteristics (periodic) |
|---|
| 47 | horizontal mesh |
|---|
| 48 | Coriolis parameter |
|---|
| 49 | depth and vertical scale factors |
|---|
| 50 | |
|---|
| 51 | FOR EXAMPLE |
|---|
| 52 | - for AMM12 : |
|---|
| 53 | coordinates.nc |
|---|
| 54 | bathy_meter.nc |
|---|
| 55 | bathy_level.nc |
|---|
| 56 | amm12_rivers.nc |
|---|
| 57 | coordinates.bdy.nc |
|---|
| 58 | amm12_restart_oce.nc |
|---|
| 59 | directories: bdydta/ |
|---|
| 60 | fluxes/ |
|---|
| 61 | - for ORCA2 : |
|---|
| 62 | coordinates.nc |
|---|
| 63 | bathy_meter.nc |
|---|
| 64 | bathy_level.nc |
|---|
| 65 | domain_def.xml |
|---|
| 66 | field_def.xml |
|---|
| 67 | iodef.xml |
|---|
