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 | === Closed seas (closea module) === |
---|
22 | |
---|
23 | If you want to define closed seas in the bathymetry either to suppress them at runtime or |
---|
24 | redistribute freshwater fluxes, then you need to run make_closea_masks.py after you have |
---|
25 | created the basic domain_cfg file. This utility will add "closea_mask*" fields to the |
---|
26 | domain_cfg file to define the closed seas in the configuration. (If you have closed seas |
---|
27 | but don't want to treat them in a special way then you can ignore this step). |
---|
28 | |
---|
29 | ================================ |
---|
30 | = HOW TO USE |
---|
31 | ================================ |
---|
32 | 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 |
---|
33 | IMPORTANT : keep the namelist_ref committed inchanged. !!! |
---|
34 | |
---|
35 | NEW OPTION ln_e3_dep in the namelist_ref: |
---|
36 | till nemo_v3.6_stable e3 were done like an analytical derivative of depth function |
---|
37 | now e3=dk[depth] in discret sens |
---|
38 | |
---|
39 | If you want to create same e3[tuvw] like 3.6 you've to use "ln_e3_dep=.false." |
---|
40 | |
---|
41 | ln_e3_dep = .true. ! =T : e3=dk[depth] in discret sens. |
---|
42 | ! ! ===>>> will become the only possibility in v4.0 |
---|
43 | ! ! =F : e3 analytical derivative of depth function |
---|
44 | ! ! only there for backward compatibility test with v3.6 |
---|
45 | ! |
---|
46 | |
---|
47 | 2) copy in DOMAINcfg directory same input files (of related configuration) required in v3.6_stable. |
---|
48 | |
---|
49 | DOMAINcfg package is EXACTLY what does exist in NEMO version 3.6 to define a model domain (both domain related namelist and initialization). |
---|
50 | DOMAINcfg tool creates a netcdf file "domain_cfg.nc" containing all the ocean domain informations required to define an ocean configuration, |
---|
51 | these files are : |
---|
52 | |
---|
53 | domain size |
---|
54 | domain characteristics (periodic) |
---|
55 | horizontal mesh |
---|
56 | Coriolis parameter |
---|
57 | depth and vertical scale factors |
---|
58 | |
---|
59 | FOR EXAMPLE |
---|
60 | - for AMM12 : |
---|
61 | coordinates.nc |
---|
62 | bathy_meter.nc |
---|
63 | bathy_level.nc |
---|
64 | amm12_rivers.nc |
---|
65 | coordinates.bdy.nc |
---|
66 | amm12_restart_oce.nc |
---|
67 | directories: bdydta/ |
---|
68 | fluxes/ |
---|
69 | - for ORCA2 : |
---|
70 | coordinates.nc |
---|
71 | bathy_meter.nc |
---|
72 | bathy_level.nc |
---|
73 | domain_def.xml |
---|
74 | field_def.xml |
---|
75 | iodef.xml |
---|