| 59 | | |
| 60 | | Input:: List of all namelist parameters \\\\ |
| 61 | | Preparatory steps:: Description how to prepare the config file for a nested setup \\\\ |
| 62 | | Example setup:: Files to carry out example runs \\\\ |
| 63 | | |
| 64 | | |
| 65 | | |
| 66 | | |
| 67 | | == Job preparation == |
| 68 | | The following example provide a step-by-step tutorial on how to set up a nesting system with one parent (root) domain and two child domains. |
| 69 | | |
| 70 | | 1. Prepare parameter files for all domains, e.g. topography files or static drivers and separate each file for each domain: |
| 71 | | {{{ |
| 72 | | testrun_p3d (root/parent domain) |
| 73 | | testrun_p3d_N02 (child domain 1) |
| 74 | | testrun_p3d_N03 (child domain 2) |
| 75 | | testrun_topo |
| 76 | | testrun_topo_N02 |
| 77 | | testrun_topo_N03 |
| 78 | | testrun_static |
| 79 | | testrun_static_N02 |
| 80 | | testrun_static_N03 |
| 81 | | }}} |
| 82 | | Note that numbering of the child domains must start with "02" as "01" is internally reserved for the root domain. |
| 83 | | |
| 84 | | 2. The nesting system is activated by specifying a {{{&nesting_parameters}}} NAMELIST in the _p3d file of the '''root domain''', e.g.: |
| 85 | | {{{ |
| 86 | | &nesting_parameters domain_layouts = 'root domain', 1, -1, 24, 0.0, 0.0, |
| 87 | | 'child domain 1', 2, 1, 24, 100.0, 100.0, |
| 88 | | 'child domain 2', 3, 2, 24, 200.0, 200.0, |
| 89 | | nesting_datatransfer_mode = 'mixed', |
| 90 | | nesting_mode = 'two-way', |
| 91 | | / |
| 92 | | }}} |
| 93 | | For details on the parameters, see [wiki:doc/app/nestpar#nestpar &nesting_parameters]. |
| 94 | | |
| 95 | | 3. No additional file connection statements for the child domains are required as long as the suffix * is set: |
| 96 | | {{{ |
| 97 | | #---------------------------------------------------------------------------- |
| 98 | | # List of input-files for nested model runs |
| 99 | | #---------------------------------------------------------------------------- |
| 100 | | PARIN in:tr d3# $base_data/$run_identifier/INPUT _p3d* |
| 101 | | #---------------------------------------------------------------------------- |
| 102 | | }}} |
| 103 | | 4. Execute {{{palmrun}}} and specify the nesting input files, i.e., |
| 104 | | {{{ |
| 105 | | palmrun -r testrun -a "d3#" -X 72 ... |
| 106 | | }}} |
| 107 | | Make sure that the total number of PEs (here 72) the sum of the PEs allocated for the individual domains (3 x 24). |
