[7421] | 1 | ================================ |
---|
| 2 | = HOW TO COMPILE |
---|
| 3 | ================================ |
---|
[6956] | 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. |
---|
[6955] | 9 | |
---|
[6956] | 10 | DOMAINcfg compiled will create "make_domain_cfg.exe" executable script (the main routine of this tool is make_domain_cfg.f90) |
---|
[7108] | 11 | |
---|
[7421] | 12 | ================================ |
---|
| 13 | = HOW TO RUN |
---|
| 14 | ================================ |
---|
| 15 | just run : |
---|
| 16 | ::::::::::::::::::::::::::::::::::::::::::::::::: |
---|
[7828] | 17 | mpirun -np 1 ./make_domain_cfg.exe |
---|
[7421] | 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 |
---|
[9079] | 25 | IMPORTANT : keep the namelist_ref committed inchanged. !!! |
---|
[7421] | 26 | |
---|
[11628] | 27 | NEW OPTION: |
---|
| 28 | * ln_e3_dep |
---|
[7421] | 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 | |
---|
[11628] | 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 | |
---|
[7421] | 48 | 2) copy in DOMAINcfg directory same input files (of related configuration) required in v3.6_stable. |
---|
| 49 | |
---|
| 50 | DOMAINcfg package is EXACTLY what does exist in NEMO version 3.6 to define a model domain (both domain related namelist and initialization). |
---|
| 51 | DOMAINcfg tool creates a netcdf file "domain_cfg.nc" containing all the ocean domain informations required to define an ocean configuration, |
---|
| 52 | these files are : |
---|
| 53 | |
---|
| 54 | domain size |
---|
| 55 | domain characteristics (periodic) |
---|
| 56 | horizontal mesh |
---|
| 57 | Coriolis parameter |
---|
| 58 | depth and vertical scale factors |
---|
| 59 | |
---|
[6984] | 60 | FOR EXAMPLE |
---|
| 61 | - for AMM12 : |
---|
| 62 | coordinates.nc |
---|
| 63 | bathy_meter.nc |
---|
| 64 | bathy_level.nc |
---|
| 65 | amm12_rivers.nc |
---|
| 66 | coordinates.bdy.nc |
---|
| 67 | amm12_restart_oce.nc |
---|
| 68 | directories: bdydta/ |
---|
| 69 | fluxes/ |
---|
| 70 | - for ORCA2 : |
---|
| 71 | coordinates.nc |
---|
| 72 | bathy_meter.nc |
---|
| 73 | bathy_level.nc |
---|
| 74 | domain_def.xml |
---|
| 75 | field_def.xml |
---|
| 76 | iodef.xml |
---|