| 14 | |
| 15 | [[Image(button_input.png,120px,link=wiki:doc/app/agtpar)]] |
| 16 | [[Image(button_ex_setup.png,120px,link=browser:palm/trunk/EXAMPLES/agents/)]] |
| 17 | [[Image(button_prepro.png,120px,link=wiki:doc/tec/mas/agent_preprocessing)]] |
| 18 | [[Image(button_a_star.png,120px,link=wiki:doc/tec/mas/agent_pathfinding)]] |
| 19 | [[Image(button_social_force.png,120px,link=wiki:doc/tec/mas/social_forces)]] |
| 20 | [[Image(button_output.png,120px,link=wiki:doc/tec/mas/output)]] |
| 21 | [[Image(button_code_structure.png,120px,link=wiki:doc/tec/mas/implementation)]] \\\\\\\\ |
| 22 | [[Image(pathfinding_berlin.gif,600)]] |
| 23 | |
| 24 | Input:: List of all namelist parameters \\\\ |
| 25 | Preparatory steps:: Description how to prepare the config file for a nested setup \\\\ |
| 26 | Example setup:: Files to carry out example runs \\\\ |
| 27 | |
| 28 | |
| 29 | |
| 30 | |
| 31 | |
| 32 | '''Offline nesting within larger-scale models''' |
| 33 | |
| 34 | Since revision -r3347 a nesting in larger-scale models is available in PALM, which is realized as a pure offline nesting. |
| 35 | Therefore, time-dependent values for the three velocity components, potential temperature and the mixing ratio are stored for the lateral and top boundaries of the PALM model domain in the dynamic input file (see [wiki:doc/app/iofiles/pids/#dynamic_input dynamic input file]). |
| 36 | The boundary data are read and mapped onto the respective boundaries during the simulation, while the boundary data is interpolated linearly in time, depending on the data availability. |
| 37 | This way, it is possible to account for changing synoptic conditions during the simulation without adding further tendency terms or to nudge the LES solution. |
| 38 | The four lateral boundaries as well as the model top boundary are thus non-cyclic boundaries (see [wiki:doc/tec/bc#noncyc non-cyclic]), where, depending on the input data, in- and outflow can occur simultaneously at one lateral boundary layer. |
| 39 | At the beginning, the model is initialized with mean profiles or heterogeneous 3D data inferred from the larger-scale model. \\\\ |
| 40 | |
| 41 | The PALM model can be nested into any larger-scale model of your choice (COSMO, WRF, etc.), subject to the condition that the data in the dynamic input file is readable, i.e. with horizontal and vertical dimensions as expected by PALM. |
| 42 | Boundary data need to be provided for each boundary grid point at the lateral ''xz, yz''-layers as well as at the top boundary. |
| 43 | To date, the pre-processing tool [wiki:doc/app/iofiles/inifor INIFOR] is available which can convert output data from the COSMO model into PALM-readable boundary data (not available for WRF so far). \\\\ |
| 44 | |
| 45 | Larger-scale model output data do not encompass any resolved-scale turbulence but turbulence is completely parametrized. |
| 46 | Hence, turbulence needs to develop first in the PALM model domain, requiring some adjustment zones near the boundaries. |
| 47 | In order reduce the adjustment zones near the boundaries, turbulence development is accelerated / triggered by using a [wiki:doc/tec/bc#synth synthetic turbulence generator], which is applied at the lateral boundaries; and imposes turbulent fluctuations onto the boundary data of the velocity components with characteristic amplitude depending on atmospheric stability inferred from the mean boundary data. \\\\ |
| 48 | |
| 49 | The offline nesting can be applied in combination with the self nesting implemented in PALM, with the root model nested offline in the larger-scale model and the child models recursively nesting within the root model. |
| 50 | This case, only the root model requires the initialization and boundary data from the larger-scale model via the [wiki:doc/app/iofiles/pids/#dynamic_input dynamic input file]. |
| 51 | |
| 52 | To apply the offline nesting, a [wiki:doc/app/iofiles/pids/#dynamic_input dynamic input file] is required, as well as the namelist [wiki:doc/app/nestofflpar#nestofflpars &nesting_offl_parameters] must be provided. |
| 53 | |
| 54 | [[Image(button_input.png,120px,link=wiki:doc/app/agtpar)]] |
| 55 | [[Image(button_ex_setup.png,120px,link=browser:palm/trunk/EXAMPLES/agents/)]] |
| 56 | [[Image(button_prepro.png,120px,link=wiki:doc/tec/mas/agent_preprocessing)]] |
| 57 | [[Image(button_a_star.png,120px,link=wiki:doc/tec/mas/agent_pathfinding)]] |
| 58 | [[Image(button_social_force.png,120px,link=wiki:doc/tec/mas/social_forces)]] |
| 59 | [[Image(button_output.png,120px,link=wiki:doc/tec/mas/output)]] |
| 60 | [[Image(button_code_structure.png,120px,link=wiki:doc/tec/mas/implementation)]] \\\\\\\\ |
| 61 | [[Image(pathfinding_berlin.gif,600)]] |
| 62 | |
| 63 | Input:: List of all namelist parameters \\\\ |
| 64 | Preparatory steps:: Description how to prepare the config file for a nested setup \\\\ |
| 65 | Example setup:: Files to carry out example runs \\\\ |
| 66 | |
| 67 | |