159 | | ==== [domain_root] ==== |
| 159 | ==== [domain_root] - [domain_XXX] ==== |
| 160 | |
| 161 | This section contains settings for each model domain for the PALM run. The section for the root domain domain must be named [domain_root]. In case of non-nested runs, this is the default model domain. In case of a nested run, the sections for the non-root domains must be named [domain_N01], [domain_N02], etc. as it is done in the PALM parameter file. |
| 162 | |
| 163 | ||='''Variable''' =||='''Data type''' =||='''Description''' =|| |
| 164 | || {{{pixel_size}}} || float ||Grid spacing in x and y / pixel size (m) || |
| 165 | || {{{origin_x}}} || float ||x-origin of the model domain (m) with respect to the input data UTM coordinates || |
| 166 | || {{{origin_y}}} || float ||y-origin of the model domain (m) with respect to the input data UTM coordinates || |
| 167 | || {{{nx}}} || float ||Number of grid points in x-direction (equals the {{{nx}}} setting in the PALM parameter file || |
| 168 | || {{{ny}}} || float ||Number of grid points in y-direction (equals the {{{ny}}} setting in the PALM parameter file || |
| 169 | || {{{buildings_3d}}} || logical ||Use 3D buildings via the {{{buildings_3d}}} array to buildings instead of {{{buildings_2d}}}. This parameter must be true if bridges are present in the simulation domain. Note that the processing of 3D buildings by palm_csd is slower than 2D buildings || |
| 170 | || {{{dz}}} || float ||Vertical grid spacing in PALM (m). This parameter is needed when {{{buildings_3d}, {{{street_trees}}}, {{{canopy_patches}}}, {{{interpolate_terrain}}}, or {{{use_palm_z_axis}}} is used || |
| 171 | || {{{allow_high_vegetation}}} || logical ||If set to {{{True}}}, it is allowed to have high vegetation classes according in the {{{vegetation_type}}} distribution. Note that this can involve very large roughness lengths > 0.5 m. If the vertical grid spacings is close or smaller than this threshold the PALM run will crash and/or does not provide meaningful results. It is generally recommended to set this parameter to {{{False}}} whenever the grid spacing in small enough to resolve canopy patches be 2 or more vertical grid levels. If set to {{{False}}} pixels where a high vegetation type was prescribed will be converted into a 3D leaf area density canopy using the canopy generator || |
| 172 | || {{{generate_vegetation_patches}}} || logical ||If set to {{{True}}} the embedded canopy generator will convert all surface pixels that contain high vegetation into a 3D leaf area density distribution. This applies to pixels where {{{vegetation_type}}} is set to a high vegetation type, or where the vegetation height field suggests high vegetation. Note that only pixels with heights {{{> 2*dz}}} are converted, while all other pixels will be parameterized via the {{{vegetation_type}}} field || |
| 173 | || {{{use_palm_z_axis}}} || logical ||If set to True, the static driver will raster the input data on the z-grid of PALM for output. Note that PALM will convert continuous static driver data itself on its grid and apply additional filtering procedures. It is thus recommended to set this parameter to {{{False}}} unless {{{interpolate_terrain = True}}} in nested set-ups.|| |
| 174 | || {{{interpolate_terrain}}} || logical ||If set to True, the terrain height is interpolated and blended over between parent and child domains in order to avoid severe steps in terrain height due to different grid spacings between parent and child || |
| 175 | || {{{domain_parent}}} || string ||Name of the parent domain of the current domain. If the current domain is the root domain, leave this parameter empty. || |
| 176 | || {{{vegetation_on_roofs}}} || logical ||If set to True, allow green roofs || |
| 177 | || {{{street_trees}}} || logical ||If set to true, information on individual street trees will be used to generate a 3D leaf area density and basal area density distribution for each tree. In contrast to vegetation patches, where a closed canopy is assumed and information is only distributed vertically for each pixel, street trees have a 3D shape that is mapped on the simulation domain || |
| 178 | |
| 179 | Example: |
| 180 | {{{ |