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: |
---|
28 | * ln_e3_dep |
---|
29 | till nemo_v3.6_stable e3 were done like an analytical derivative of depth function |
---|
30 | now e3=dk[depth] in discret sens |
---|
31 | |
---|
32 | If you want to create same e3[tuvw] like 3.6 you've to use "ln_e3_dep=.false." |
---|
33 | |
---|
34 | ln_e3_dep = .true. ! =T : e3=dk[depth] in discret sens. |
---|
35 | ! ! ===>>> will become the only possibility in v4.0 |
---|
36 | ! ! =F : e3 analytical derivative of depth function |
---|
37 | ! ! only there for backward compatibility test with v3.6 |
---|
38 | ! |
---|
39 | |
---|
40 | * ln_domclo |
---|
41 | The definition of closed sea are now integrated into ./make_domain_cfg.exe. The need on an external python script and hard coded indices has been removed. |
---|
42 | ln_domclo=T will generate the masks needed to mask or correct |
---|
43 | the fwf unbalance over closed sea. If non defined closed sea are detected, a mask containing this will also be generated. |
---|
44 | The detection of the lake is done using a lat/lon seed and a flood filling algorithm (the default namelist should work for any resolution). |
---|
45 | The definition of the target area is done by defining a lat/lon position center, then all wet points at a defined distance of it will be selected. |
---|
46 | Options are available to select only coastal points if needed. |
---|
47 | For each lake, name, lon_src, lat_src, lon_trg, lat_trg, river mouth area, correction scheme, radius trg, id trg need to be defined. |
---|
48 | * lon/lat_src/trg are the seed location of the closed sea (src) and its river outflow (trg). |
---|
49 | * river mouth area is to defined is you spread the closed sea emp correction locally (circle with raduis 'radius trg' in m) |
---|
50 | or along the coast point into a circle with raduis 'radius trg' (in m) |
---|
51 | or globally (open sea mask) |
---|
52 | * correction scheme defined how you want to spread the closed sea correction |
---|
53 | * glo : as emp globally |
---|
54 | * rnf : as a runoff for the net precip and on emp for net evaporation case locally or along the coast |
---|
55 | * emp : as emp locally or along the coast |
---|
56 | * id trg is a integer used to defined group of closed sea and their river outflow (for example all the great lake and the St Laurent outflow). |
---|
57 | |
---|
58 | 2) copy in DOMAINcfg directory same input files (of related configuration) required in v3.6_stable. |
---|
59 | |
---|
60 | DOMAINcfg package is EXACTLY what does exist in NEMO version 3.6 to define a model domain (both domain related namelist and initialization). |
---|
61 | DOMAINcfg tool creates a netcdf file "domain_cfg.nc" containing all the ocean domain informations required to define an ocean configuration, |
---|
62 | these files are : |
---|
63 | |
---|
64 | domain size |
---|
65 | domain characteristics (periodic) |
---|
66 | horizontal mesh |
---|
67 | Coriolis parameter |
---|
68 | depth and vertical scale factors |
---|
69 | |
---|
70 | FOR EXAMPLE |
---|
71 | - for AMM12 : |
---|
72 | coordinates.nc |
---|
73 | bathy_meter.nc |
---|
74 | bathy_level.nc |
---|
75 | amm12_rivers.nc |
---|
76 | coordinates.bdy.nc |
---|
77 | amm12_restart_oce.nc |
---|
78 | directories: bdydta/ |
---|
79 | fluxes/ |
---|
80 | - for ORCA2 : |
---|
81 | coordinates.nc |
---|
82 | bathy_meter.nc |
---|
83 | bathy_level.nc |
---|
84 | domain_def.xml |
---|
85 | field_def.xml |
---|
86 | iodef.xml |
---|