| 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
|---|
| 2 | <html><head> |
|---|
| 3 | <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>PALM chapter 4.2</title></head> |
|---|
| 4 | <body><h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime |
|---|
| 5 | parameters</a> and <a href="#Paketparameter">package |
|---|
| 6 | parameters</a></h3> |
|---|
| 7 | <h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3> |
|---|
| 8 | <br><br> |
|---|
| 9 | <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr> |
|---|
| 10 | <td style="vertical-align: top;"><font size="4"><b>Parameter |
|---|
| 11 | name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td> |
|---|
| 12 | <td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td> |
|---|
| 13 | <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td> |
|---|
| 14 | </tr> <tr> <td style="vertical-align: top;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br> |
|---|
| 15 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 16 | <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td> |
|---|
| 17 | <td style="vertical-align: top;">Averaging interval for |
|---|
| 18 | all output of temporally averaged data (in s).<br><br>This |
|---|
| 19 | parameter defines the time interval length for temporally averaged data |
|---|
| 20 | (vertical profiles, spectra, 2d cross-sections, 3d volume data). By |
|---|
| 21 | default, data are not subject to temporal averaging. The |
|---|
| 22 | interval |
|---|
| 23 | length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>. |
|---|
| 24 | In any case, <span style="font-weight: bold;">averaging_interval</span> |
|---|
| 25 | <= <span style="font-weight: bold;">dt_data_output_av</span> |
|---|
| 26 | must hold.<br><br>If |
|---|
| 27 | an interval is defined, then by default the average is calculated from |
|---|
| 28 | the data values of all timesteps lying within this interval. The number |
|---|
| 29 | of time levels entering into the average can be reduced with the |
|---|
| 30 | parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br><br>If |
|---|
| 31 | an averaging interval can not be completed at the end of a run, it |
|---|
| 32 | will be finished at the beginning of the next restart run. Thus for |
|---|
| 33 | restart runs, averaging intervals do not |
|---|
| 34 | necessarily begin at the beginning of the run.<br><br>Parameters |
|---|
| 35 | <a href="#averaging_interval_pr">averaging_interval_pr</a> |
|---|
| 36 | and <a href="#averaging_interval_sp">averaging_interval_sp</a> |
|---|
| 37 | can be used to define different averaging intervals for vertical |
|---|
| 38 | profile data and spectra, respectively.<br> </td> </tr> |
|---|
| 39 | <tr> <td style="vertical-align: top;"> <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p> |
|---|
| 40 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 41 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br> |
|---|
| 42 | interval</a><br> |
|---|
| 43 | </span> </td> <td style="vertical-align: top;"> |
|---|
| 44 | <p>Averaging interval for output of vertical profiles to |
|---|
| 45 | local |
|---|
| 46 | file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a> |
|---|
| 47 | </font></font>and/or <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a> |
|---|
| 48 | (in s). </p> <p>If |
|---|
| 49 | this parameter is given a non-zero value, temporally |
|---|
| 50 | averaged vertical profile data are output. By default, profile data |
|---|
| 51 | data are not subject to temporal averaging. The interval length is |
|---|
| 52 | limited by the parameter <a href="#dt_dopr">dt_dopr</a>. |
|---|
| 53 | In any case <b>averaging_interval_pr</b> <= <b>dt_dopr |
|---|
| 54 | </b>must |
|---|
| 55 | hold.</p>If an interval is defined, then by default the average |
|---|
| 56 | is calculated |
|---|
| 57 | from the data values of all timesteps lying within this interval. The |
|---|
| 58 | number of time levels entering into the average can be reduced with the |
|---|
| 59 | parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>. |
|---|
| 60 | <p>If |
|---|
| 61 | an averaging interval can not be completed at the end of a run, it will |
|---|
| 62 | be finished at the beginning of the next restart run. Thus for restart |
|---|
| 63 | runs, averaging intervals do not |
|---|
| 64 | necessarily begin at the beginning of the run.</p> </td> </tr> |
|---|
| 65 | <tr> <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br> |
|---|
| 66 | substeps</span></td> <td style="vertical-align: top;">L<br> |
|---|
| 67 | </td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td> |
|---|
| 68 | <td style="vertical-align: top;">Switch |
|---|
| 69 | to steer the call of the pressure solver.<br> <br> |
|---|
| 70 | In order to speed-up performance, the Poisson equation for perturbation |
|---|
| 71 | pressure (see <a href="#psolver">psolver</a>) can |
|---|
| 72 | be called only at the last substep of multistep Runge-Kutta |
|---|
| 73 | timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>) |
|---|
| 74 | by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span> |
|---|
| 75 | = <span style="font-style: italic;">.F.</span>. |
|---|
| 76 | In many cases, this sufficiently reduces the divergence of the velocity |
|---|
| 77 | field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this |
|---|
| 78 | case and in case |
|---|
| 79 | of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span> |
|---|
| 80 | = <span style="font-style: italic;">.T.</span> |
|---|
| 81 | should be used. <span style="font-weight: bold;"></span></td> |
|---|
| 82 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 83 | <p><a name="fcl_factor"></a><b>cfl_factor</b></p> |
|---|
| 84 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 85 | <td style="vertical-align: top;"> <p><i>0.1, |
|---|
| 86 | 0.8 or 0.9</i> <br> <i>(see right)</i></p> |
|---|
| 87 | </td> <td style="vertical-align: top;"> <p lang="en-GB">Time step limiting factor. </p> |
|---|
| 88 | <p><span lang="en-GB">In the model, the <span lang="en-GB">maximum |
|---|
| 89 | allowed </span>time step according to CFL and |
|---|
| 90 | diffusion-criterion |
|---|
| 91 | dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">= |
|---|
| 92 | dt_max * <b>cfl_factor</b> |
|---|
| 93 | in order to avoid stability problems which may arise in the vicinity of |
|---|
| 94 | the maximum allowed timestep. The condition <i>0.0</i> |
|---|
| 95 | < <b>cfl_factor</b> |
|---|
| 96 | < <i>1.0 </i>applies.<br> </span></p> |
|---|
| 97 | <p><span lang="en-GB">The default value of |
|---|
| 98 | cfl_factor depends on |
|---|
| 99 | the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br> </span></p> <p><span lang="en-GB">For the third order Runge-Kutta scheme it |
|---|
| 100 | is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br> </span></p> <p><span lang="en-GB">In case of the leapfrog scheme a quite |
|---|
| 101 | restrictive value of <span style="font-weight: bold;">cfl_factor</span> |
|---|
| 102 | = <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity |
|---|
| 103 | divergence |
|---|
| 104 | significantly effects the accuracy of the model results.</span><a href="chapter_4.1.html#scalar_advec"><span lang="en-GB"></span></a><span lang="en-GB"> Possibly larger values may |
|---|
| 105 | be used with the leapfrog scheme but these are to be determined by |
|---|
| 106 | appropriate test runs.<span style="font-family: times new roman;"><br> |
|---|
| 107 | </span></span></p> <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler |
|---|
| 108 | scheme is <span style="font-weight: bold;">cfl_factor</span> |
|---|
| 109 | = <span style="font-style: italic;">0.8</span> .</font></span></td> |
|---|
| 110 | </tr> |
|---|
| 111 | <tr> <td style="vertical-align: top;"> <p><a name="create_disturbances"></a><b>create_disturbances</b></p> |
|---|
| 112 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 113 | <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td> |
|---|
| 114 | <td style="vertical-align: top;"> <p>Switch to |
|---|
| 115 | impose random perturbations to the horizontal |
|---|
| 116 | velocity field. </p> <p>With <b>create_disturbances</b> |
|---|
| 117 | = <i>.T.,</i> random |
|---|
| 118 | perturbations can be imposed to the horizontal velocity field at |
|---|
| 119 | certain times e.g. in order to trigger off the onset of convection, |
|---|
| 120 | etc..<br> </p> <p>The temporal interval between |
|---|
| 121 | these times can be steered with <a href="#dt_disturb">dt_disturb</a>, |
|---|
| 122 | the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a> |
|---|
| 123 | and <a href="#disturbance_level_t">disturbance_level_t</a>, |
|---|
| 124 | and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>. |
|---|
| 125 | In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a> |
|---|
| 126 | and <a href="chapter_4.1.html#bc_ns">bc_ns</a>), |
|---|
| 127 | the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a> |
|---|
| 128 | and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>. |
|---|
| 129 | A perturbation is added to each grid point with its individual value |
|---|
| 130 | determined by multiplying the disturbance amplitude with a uniformly |
|---|
| 131 | distributed random number. |
|---|
| 132 | After this, the arrays of u and v are smoothed by applying a |
|---|
| 133 | Shuman-filter twice and made divergence-free by applying the pressure |
|---|
| 134 | solver.<br> </p> <p>The random number generator to |
|---|
| 135 | be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br> |
|---|
| 136 | </p> <p>As soon as the desired flow features have |
|---|
| 137 | developed |
|---|
| 138 | (e.g. convection has started), further imposing of |
|---|
| 139 | perturbations |
|---|
| 140 | is not necessary and can be omitted (this does not hold for non-cyclic |
|---|
| 141 | lateral boundaries!). This can be steered by assigning |
|---|
| 142 | an upper limit value for the perturbation energy (the perturbation |
|---|
| 143 | energy is defined by the deviation of the velocity from the mean flow) |
|---|
| 144 | using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>. |
|---|
| 145 | As soon as the perturbation energy has exceeded this energy limit, no |
|---|
| 146 | more random perturbations are assigned<br> |
|---|
| 147 | . <br> |
|---|
| 148 | Timesteps where a random perturbation has been imposed are marked in |
|---|
| 149 | the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a> |
|---|
| 150 | by the character "D" appended to the values of the maximum horizontal |
|---|
| 151 | velocities. </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p> |
|---|
| 152 | </td> <td style="vertical-align: top;">C*10 |
|---|
| 153 | <br> (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td> |
|---|
| 154 | <td style="vertical-align: top;"> <p>Type of |
|---|
| 155 | normalization applied to the x-coordinate of vertical |
|---|
| 156 | profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p> |
|---|
| 157 | <p>This parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 158 | = <span style="font-style: italic;">'profil'</span>.</p><p>If |
|---|
| 159 | vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on |
|---|
| 160 | local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>, |
|---|
| 161 | parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>) |
|---|
| 162 | the x-values of the data points can be normalized with respect to |
|---|
| 163 | certain quantities (e.g. the near-surface heat flux) in order to ensure |
|---|
| 164 | a better comparability. This type of normalization then applies to all |
|---|
| 165 | profiles of one coordinate system (panel). The normalization quantities |
|---|
| 166 | are re-calculated for each output time of each individual profile. If |
|---|
| 167 | temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>), |
|---|
| 168 | then the normalization quantities are also temporally averaged |
|---|
| 169 | accordingly. If the value of a normalization quantity becomes zero, |
|---|
| 170 | then normalization for the total respective coordinate system (panel) |
|---|
| 171 | is switched off automatically (also for the y-axis).<br> </p> |
|---|
| 172 | <p>By default, the normalization quantities are calculated as the |
|---|
| 173 | horizontal mean of the total model domain and and these values are also |
|---|
| 174 | used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>). |
|---|
| 175 | Instead of this, they can be calculated from the data of a certain |
|---|
| 176 | subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a> |
|---|
| 177 | (however, they are used again for all subdomains and even for the total |
|---|
| 178 | domain). </p> <p>The user can choose between |
|---|
| 179 | the following normalization |
|---|
| 180 | quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'wpt0'</i></td> |
|---|
| 181 | <td style="vertical-align: top;">Normalization with |
|---|
| 182 | respect |
|---|
| 183 | to the total surface sensible heat |
|---|
| 184 | flux (k=0 ).</td> </tr> <tr> <td style="vertical-align: middle;"><i>'ws2'</i></td> |
|---|
| 185 | <td style="vertical-align: top;">Normalization with |
|---|
| 186 | respect |
|---|
| 187 | to w<sub>*</sub> <sup>2</sup> |
|---|
| 188 | (square of the characteristic vertical wind speed of the CBL)</td> |
|---|
| 189 | </tr> <tr> <td style="vertical-align: top;"><i>'tsw2'</i></td> |
|---|
| 190 | <td style="vertical-align: top;">Normalization with |
|---|
| 191 | respect |
|---|
| 192 | to the square of the characteristic |
|---|
| 193 | temperature of the CBL theta<sub>*</sub> (this is defined |
|---|
| 194 | as ratio of |
|---|
| 195 | the surface heat flux and w<sub>*</sub>).</td> </tr> |
|---|
| 196 | <tr> <td style="vertical-align: middle;"><i>'ws3'</i></td> |
|---|
| 197 | <td style="vertical-align: top;">Normalization with |
|---|
| 198 | respect |
|---|
| 199 | to w<sub>*</sub> <sup>3</sup>.</td> </tr> |
|---|
| 200 | <tr> <td style="vertical-align: middle;"><i>'ws2tsw'</i></td> |
|---|
| 201 | <td style="vertical-align: top;">Normalization with |
|---|
| 202 | respect |
|---|
| 203 | to w<sub>*</sub><sup>2</sup>theta<sub>*</sub> |
|---|
| 204 | (for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td> |
|---|
| 205 | </tr> <tr> <td style="vertical-align: middle;"><i>'wstsw2'</i></td> |
|---|
| 206 | <td style="vertical-align: top;">Normalization with |
|---|
| 207 | respect |
|---|
| 208 | to w<sub>*</sub><sup>2 </sup>theta<sub>*</sub> |
|---|
| 209 | (for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td> |
|---|
| 210 | </tr> </tbody> </table> <p>For each |
|---|
| 211 | coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>) |
|---|
| 212 | an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> = |
|---|
| 213 | <span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>, |
|---|
| 214 | then the |
|---|
| 215 | x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup> |
|---|
| 216 | and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>. |
|---|
| 217 | Data |
|---|
| 218 | of the further coordinate systems (if any are to be drawn) are not |
|---|
| 219 | normalized. </p> <p>Using a normalization |
|---|
| 220 | leaves all vertical profile data on |
|---|
| 221 | local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a> |
|---|
| 222 | unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the |
|---|
| 223 | normalization is steered |
|---|
| 224 | by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a> |
|---|
| 225 | which may be changed subsequently by the user in the parameter file |
|---|
| 226 | (local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br> |
|---|
| 227 | <br> |
|---|
| 228 | The assigned normalization quantity is noted in the axes labels of the |
|---|
| 229 | respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p> |
|---|
| 230 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p> |
|---|
| 231 | </td> <td style="vertical-align: top;">C*10 |
|---|
| 232 | <br> (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td> |
|---|
| 233 | <td style="vertical-align: top;"> <p>Type of |
|---|
| 234 | normalization applied to the y-coordinate of vertical |
|---|
| 235 | profiles to be plotted with <span style="font-weight: bold;">profil</span>. </p> |
|---|
| 236 | <p>This parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 237 | = <span style="font-style: italic;">'profil'</span>.</p><p>If |
|---|
| 238 | vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on |
|---|
| 239 | local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>, |
|---|
| 240 | parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>) |
|---|
| 241 | the y-values of the data points can be normalized with respect to |
|---|
| 242 | certain quantities (at present only the normalization with respect to |
|---|
| 243 | the boundary layer height is possible) in order to ensure a better |
|---|
| 244 | comparability. </p> <p>The user can choose between the |
|---|
| 245 | following normalization |
|---|
| 246 | quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'z_i'</i></td> |
|---|
| 247 | <td style="vertical-align: top;">Normalization with |
|---|
| 248 | respect |
|---|
| 249 | to the boundary layer height |
|---|
| 250 | (determined from the height where the heat flux achieves its minimum |
|---|
| 251 | value).</td> </tr> </tbody> </table> <p>For |
|---|
| 252 | further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p> |
|---|
| 253 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_profiles"></a><b>cross_profiles</b></p> |
|---|
| 254 | </td> <td style="vertical-align: top;">C*100 |
|---|
| 255 | <br> (100)</td> <td style="vertical-align: top;">see right<br> </td> |
|---|
| 256 | <td style="vertical-align: top;"> <p>Determines |
|---|
| 257 | which vertical profiles are to be presented in |
|---|
| 258 | which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used. |
|---|
| 259 | </p> <p>This parameter only applies for |
|---|
| 260 | <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 261 | = <span style="font-style: italic;">'profil'</span>.</p><p>The |
|---|
| 262 | default assignment is: </p> <p><b>cross_profiles</b> |
|---|
| 263 | = </p> <ul> <p><span style="font-family: monospace; font-style: italic;">' |
|---|
| 264 | u v ',</span><br> <span style="font-family: monospace; font-style: italic;">' pt |
|---|
| 265 | ', </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' |
|---|
| 266 | w"pt" w*pt* w*pt*BC wpt wptBC ', </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' |
|---|
| 267 | w"u" w*u* wu w"v"w*v* wv ', </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' km |
|---|
| 268 | kh ',</span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' l ' |
|---|
| 269 | ,</span><br> |
|---|
| 270 | 14 * <span style="font-family: monospace; font-style: italic;">' |
|---|
| 271 | '</span></p> </ul> <p>If plot output of |
|---|
| 272 | vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>), |
|---|
| 273 | the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>. |
|---|
| 274 | Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>) |
|---|
| 275 | which describes the layout for a plot to be generated with the plot |
|---|
| 276 | program <span style="font-weight: bold;">profil</span>. |
|---|
| 277 | The parameter <b>cross_profiles</b> |
|---|
| 278 | determines how many coordinate systems (panels) the plot contains and |
|---|
| 279 | which profiles are supposed to be drawn into which panel. <b>cross_profiles</b> |
|---|
| 280 | expects a character string (up to 100 characters long) for each |
|---|
| 281 | coordinate system, which consists of the names of the profiles to be |
|---|
| 282 | drawn into this system (all available profiles and their respective |
|---|
| 283 | names are described at parameter <a href="#data_output_pr">data_output_pr</a>). |
|---|
| 284 | The single names have to be separated by one blank (' ') and a blank |
|---|
| 285 | must be spent also at the beginning and at the end of the |
|---|
| 286 | string. </p> <p>Example: </p> <ul> |
|---|
| 287 | <p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ', |
|---|
| 288 | ' pt '</span></p> </ul> <p>In this case the |
|---|
| 289 | plot consists of two coordinate systems |
|---|
| 290 | (panels) with the first panel containing the profiles of the horizontal |
|---|
| 291 | velocity components (<span style="font-style: italic;">'u'</span> |
|---|
| 292 | and <span style="font-style: italic;">'v'</span>) |
|---|
| 293 | of all output times (see <a href="#dt_dopr">dt_dopr</a>) |
|---|
| 294 | and the second one containing the profiles of the potential temperature |
|---|
| 295 | (<span style="font-style: italic;">'pt'</span>).<br> |
|---|
| 296 | </p> <p>Whether the coordinate systems are actually drawn, |
|---|
| 297 | depends on |
|---|
| 298 | whether data of the appropriate profiles were output during the run |
|---|
| 299 | (profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>). |
|---|
| 300 | For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned, |
|---|
| 301 | then |
|---|
| 302 | the plot only consists of one panel, since no profiles of the potential |
|---|
| 303 | temperature were output. On the other hand, if profiles were assigned |
|---|
| 304 | to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>, |
|---|
| 305 | then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>) |
|---|
| 306 | but they are not drawn in the plot. <br> </p> |
|---|
| 307 | The arrangement of the panels in the plot can be controlled |
|---|
| 308 | with the parameters <a href="#profile_columns">profile_columns</a> |
|---|
| 309 | and <a href="#profile_rows">profile_rows</a>. |
|---|
| 310 | Up to 100 panels systems are allowed in a plot (however, they may be |
|---|
| 311 | distributed on several pages).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_xtext"></a><b>cross_xtext</b></p> |
|---|
| 312 | </td> <td style="vertical-align: top;">C*40 |
|---|
| 313 | <br> (100)</td> <td style="vertical-align: top;">see right<br> </td> |
|---|
| 314 | <td style="vertical-align: top;"> <p>x-axis labels |
|---|
| 315 | of vertical profile coordinate systems to be |
|---|
| 316 | plotted with <span style="font-weight: bold;">profil</span>. |
|---|
| 317 | </p> <p>This parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 318 | = <span style="font-style: italic;">'profil'</span>.</p><p>The |
|---|
| 319 | default assignment is: </p> <p><b>cross_xtext</b> |
|---|
| 320 | = </p> <ul> <p><span style="font-style: italic;">'wind speed in |
|---|
| 321 | ms>->1', </span><br style="font-style: italic;"> <span style="font-style: italic;">'pot. temperature in |
|---|
| 322 | K', </span><br style="font-style: italic;"> |
|---|
| 323 | <span style="font-style: italic;">'heat flux in K |
|---|
| 324 | ms>->1', </span><br style="font-style: italic;"> <span style="font-style: italic;">'momentum flux in |
|---|
| 325 | m>2s>2', </span><br style="font-style: italic;"> <span style="font-style: italic;">'eddy diffusivity in |
|---|
| 326 | m>2s>->1', </span><br style="font-style: italic;"> <span style="font-style: italic;">'mixing length in m',</span> |
|---|
| 327 | <br>14 * <span style="font-style: italic;">' '</span></p> |
|---|
| 328 | </ul> <p>This parameter can be used to assign x-axis |
|---|
| 329 | labels to vertical |
|---|
| 330 | profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output |
|---|
| 331 | of vertical |
|---|
| 332 | profile data see <a href="#data_output_pr">data_output_pr</a>).<br> |
|---|
| 333 | The labels are assigned to those coordinate systems (panels) defined by |
|---|
| 334 | <a href="#cross_profiles">cross_profiles</a> |
|---|
| 335 | according to their respective order (compare the default values of <b>cross_xtext</b> |
|---|
| 336 | and <b>cross_profiles</b>). </p> <p>Umlauts |
|---|
| 337 | are possible (write “ in front of, similar to TeX), as |
|---|
| 338 | well as super- and subscripts (use ">" or "<" in front of |
|---|
| 339 | each |
|---|
| 340 | character), special characters etc. (see UNIRAS manuals) when using the |
|---|
| 341 | plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p> |
|---|
| 342 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cycle_mg"></a><b>cycle_mg</b></p> |
|---|
| 343 | </td> <td style="vertical-align: top;">C*1</td> |
|---|
| 344 | <td style="vertical-align: top;"><i>'w'</i></td> |
|---|
| 345 | <td style="vertical-align: top;"> <p>Type of cycle |
|---|
| 346 | to be used with the multi-grid method. </p> <p>This |
|---|
| 347 | parameter determines which type of cycle is applied in |
|---|
| 348 | the multi-grid method used for solving the Poisson equation for |
|---|
| 349 | perturbation pressure (see <a href="#psolver">psolver</a>). |
|---|
| 350 | It defines in which way it is switched between the fine and coarse |
|---|
| 351 | grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b> |
|---|
| 352 | may be assigned the values <i>'v'</i> or <i>'w'</i>). |
|---|
| 353 | The |
|---|
| 354 | computational cost of w-cycles is much higher than that of v-cycles, |
|---|
| 355 | however, w-cycles give a much better convergence. </p> </td> |
|---|
| 356 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 357 | <p><a name="data_output"></a><b>data_output</b></p> |
|---|
| 358 | </td> <td style="vertical-align: top;">C * 10 (100)<br> |
|---|
| 359 | </td> <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br> |
|---|
| 360 | </td> <td style="vertical-align: top;">Quantities |
|---|
| 361 | for which 2d cross section and/or 3d volume data are to be output.<br><br>PALM |
|---|
| 362 | allows the output of instantaneous data as well as of temporally |
|---|
| 363 | averaged data which is steered by the strings assigned to this |
|---|
| 364 | parameter (see below).<br><br>By default, cross section |
|---|
| 365 | data are output (depending on the selected cross sections(s), see |
|---|
| 366 | below) to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>, |
|---|
| 367 | <a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a> |
|---|
| 368 | and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>. |
|---|
| 369 | Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>. |
|---|
| 370 | If the user has switched on the output of temporally averaged data, |
|---|
| 371 | these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>, |
|---|
| 372 | <a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>, |
|---|
| 373 | <a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>, |
|---|
| 374 | and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>, |
|---|
| 375 | respectively.<br><br>The |
|---|
| 376 | filenames already suggest that all files have NetCDF format. |
|---|
| 377 | Informations about the file content (kind of quantities, array |
|---|
| 378 | dimensions and grid coordinates) are part of the self describing NetCDF |
|---|
| 379 | format and can be extracted from the NetCDF files using the command |
|---|
| 380 | "ncdump -c <filename>". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing |
|---|
| 381 | the PALM NetCDF data.<br><br>The following quantities are |
|---|
| 382 | available for output by default:<br><br><table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="width: 106px;"><span style="font-weight: bold;">quantity |
|---|
| 383 | name</span></td><td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td><td><span style="font-weight: bold;">unit</span></td><td><span style="font-weight: bold;">remarks</span></td></tr><tr><td style="width: 106px;"><span style="font-style: italic;">e</span></td><td style="width: 196px;">SGS TKE</td><td>m<sup>2</sup>/s<sup>2</sup></td><td></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td><td style="width: 196px; vertical-align: top;">liquid water path</td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">only horizontal cross section |
|---|
| 384 | is allowed, requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a> |
|---|
| 385 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td><td style="width: 196px; vertical-align: top;">perturpation |
|---|
| 386 | pressure</td><td style="vertical-align: top;">N/m<sup>2</sup>, |
|---|
| 387 | Pa</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td><td style="width: 196px; vertical-align: top;">particle/droplet |
|---|
| 388 | concentration</td><td style="vertical-align: top;">#/gridbox</td><td style="vertical-align: top;">requires that particle |
|---|
| 389 | advection is switched on by <span style="font-weight: bold;">mrun</span>-option |
|---|
| 390 | "-p particles"</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td><td style="width: 196px; vertical-align: top;">mean |
|---|
| 391 | particle/droplet radius </td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">requires that particle |
|---|
| 392 | advection is switched on by <span style="font-weight: bold;">mrun</span>-option |
|---|
| 393 | "-p particles"</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td><td style="width: 196px; vertical-align: top;">potential |
|---|
| 394 | temperature<br></td><td style="vertical-align: top;">K</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td><td style="width: 196px; vertical-align: top;">specific humidity |
|---|
| 395 | (or total water content, if cloud physics is switched on)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#moisture">moisture</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td><td style="width: 196px; vertical-align: top;">liquid water |
|---|
| 396 | content</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a> |
|---|
| 397 | = <span style="font-style: italic;">.TRUE.</span> |
|---|
| 398 | or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> |
|---|
| 399 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td><td style="width: 196px; vertical-align: top;">change in liquid |
|---|
| 400 | water content due to condensation/evaporation during last timestep</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> |
|---|
| 401 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td><td style="width: 196px; vertical-align: top;">volume of liquid |
|---|
| 402 | water</td><td style="vertical-align: top;">m<sup>3</sup>/gridbox</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> |
|---|
| 403 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td><td style="width: 196px; vertical-align: top;">weighting factor</td><td style="vertical-align: top;"></td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> |
|---|
| 404 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td><td style="width: 196px; vertical-align: top;">water vapor |
|---|
| 405 | content (specific humidity)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a> |
|---|
| 406 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td><td style="width: 196px; vertical-align: top;">concentration of |
|---|
| 407 | the scalar</td><td style="vertical-align: top;">1/m<sup>3</sup></td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#passive_scalar">passive_scalar</a> |
|---|
| 408 | = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td><td style="width: 196px; vertical-align: top;">(near surface) |
|---|
| 409 | characteristic temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">only horizontal cross section |
|---|
| 410 | is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td><td style="width: 196px; vertical-align: top;">u-component of |
|---|
| 411 | the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td><td style="width: 196px; vertical-align: top;">(near surface) |
|---|
| 412 | friction velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;">only horizontal cross section |
|---|
| 413 | is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td><td style="width: 196px; vertical-align: top;">v-component of |
|---|
| 414 | the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td><td style="width: 196px; vertical-align: top;">virtual potential |
|---|
| 415 | temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#moisture">moisture</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td><td style="width: 196px; vertical-align: top;">w-component of |
|---|
| 416 | the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr></tbody></table><br>Multiple |
|---|
| 417 | quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span> |
|---|
| 418 | = <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br><br>By |
|---|
| 419 | assigning the pure strings from the above table, 3d volume data is |
|---|
| 420 | output. Cross section data can be output by appending the string <span style="font-style: italic;">'_xy'</span>, <span style="font-style: italic;">'_xz'</span>, or <span style="font-style: italic;">'_yz'</span> to the |
|---|
| 421 | respective quantities. Time averaged output is created by |
|---|
| 422 | appending the string <span style="font-style: italic;">'_av' |
|---|
| 423 | </span>(for |
|---|
| 424 | cross section data, this string must be appended after the cross |
|---|
| 425 | section string). Cross section data can also be (additionally) averaged |
|---|
| 426 | along the direction normal to the respective section (see below). |
|---|
| 427 | Assignments of quantities can be given in arbitrary |
|---|
| 428 | order:<br><br>Example:<br><br><div style="margin-left: 40px;"><span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'pt_xz_av'</span>, <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'u_av'</span>.<br></div><br>This |
|---|
| 429 | example will create the following output: instantaneous 3d volume data |
|---|
| 430 | of u-velocity component (by default on file DATA_3D_NETCDF), temporally |
|---|
| 431 | averaged 3d volume data of u-velocity component (by default on file |
|---|
| 432 | DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of |
|---|
| 433 | w-velocity component (by default on file DATA_2D_XY_NETCDF), and |
|---|
| 434 | temporally averaged vertical cross section data of potential |
|---|
| 435 | temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br><br>The |
|---|
| 436 | user is allowed to extend the above list of quantities by defining his |
|---|
| 437 | own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br><br>The |
|---|
| 438 | time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>. |
|---|
| 439 | This is valid for all types of output quantities by default. Individual |
|---|
| 440 | time intervals for instantaneous (!) 3d and section data can |
|---|
| 441 | be |
|---|
| 442 | declared using <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="#dt_do2d_xz">dt_do2d_xz</a>, and <a href="#dt_do2d_yz">dt_do2d_yz</a>.<br><br>Also, |
|---|
| 443 | an individual time interval for output of temporally averaged data can |
|---|
| 444 | be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>. |
|---|
| 445 | This applies to both 3d volume and cross section data. The length of |
|---|
| 446 | the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br><br>The |
|---|
| 447 | parameter <a href="#skip_time_data_output">skip_time_data_output</a> |
|---|
| 448 | can be used to shift data output activities for a given time interval. |
|---|
| 449 | Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>, |
|---|
| 450 | <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><p>With |
|---|
| 451 | the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a> |
|---|
| 452 | the output can be limited in the vertical direction up to a certain |
|---|
| 453 | grid point.<br> </p> Cross sections extend through the |
|---|
| 454 | total model |
|---|
| 455 | domain. In the two horizontal directions all grid points with 0 |
|---|
| 456 | <= i |
|---|
| 457 | <= nx+1 and 0 <= j |
|---|
| 458 | <= ny+1 are output so that in case of cyclic boundary conditions |
|---|
| 459 | the |
|---|
| 460 | complete total domain is represented. The location(s) of the cross |
|---|
| 461 | sections can be defined with parameters <a href="#section_xy">section_xy</a>, |
|---|
| 462 | <a href="#section_xz">section_xz</a>, and <a href="#section_yz">section_yz</a>. Assigning <span style="font-weight: bold;">section_..</span> = <span style="font-style: italic;">-1</span> |
|---|
| 463 | causes the output data to be averaged along the direction |
|---|
| 464 | normal to the respective section.<br><br><br><span style="font-weight: bold;">Output of user defined quantities:</span><br><br>Beside |
|---|
| 465 | the standard quantities from the above list, the user can output any |
|---|
| 466 | other quantities. These have to be defined and calculated within the |
|---|
| 467 | user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>). |
|---|
| 468 | They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a> |
|---|
| 469 | for which the same rules apply as for <span style="font-weight: bold;">data_output</span>. |
|---|
| 470 | Output of the user defined quantities (time interval, averaging, |
|---|
| 471 | selection of cross sections, etc.) is controlled with the parameters |
|---|
| 472 | listed above and data are written to the same file(s) as the standard |
|---|
| 473 | quantities.<br><br><p style="font-weight: bold;">Output |
|---|
| 474 | on parallel machines:</p><p> |
|---|
| 475 | By default, with parallel runs, processors output only data |
|---|
| 476 | of their respective subdomains into seperate local files (file names |
|---|
| 477 | are |
|---|
| 478 | constructed by appending the four digit processor ID, e.g. |
|---|
| 479 | <filename>_0000, <filename>_0001, etc.). |
|---|
| 480 | After PALM has |
|---|
| 481 | finished, the contents of these individual |
|---|
| 482 | files are sampled into one final file<span style="font-weight: bold;"></span> |
|---|
| 483 | using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt> |
|---|
| 484 | (to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span> |
|---|
| 485 | configuration file).</p> <p>Alternatively, PALM is able to |
|---|
| 486 | collect all grid points of a |
|---|
| 487 | cross section on PE0 before output is done. In this case only |
|---|
| 488 | one |
|---|
| 489 | output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt> |
|---|
| 490 | does not have to be called. In case of very large numbers of horizontal |
|---|
| 491 | gridpoints, sufficient |
|---|
| 492 | memory is required on PE0. This method can be used by |
|---|
| 493 | assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> |
|---|
| 494 | = <i>.F.</i>.</p><p>3d volume data output is |
|---|
| 495 | always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span> |
|---|
| 496 | has to be called anyway after PALM has been finished.</p><p><br><span style="font-weight: bold;">Old formats:</span></p> |
|---|
| 497 | <p>Beside |
|---|
| 498 | the NetCDF format, 2d cross section data and 3d volume data |
|---|
| 499 | can |
|---|
| 500 | also be output, for historical reasons, in a different (binary) format |
|---|
| 501 | using parameter <a href="#data_output_format">data_output_format</a>.</p><p>By |
|---|
| 502 | assigning <span style="font-weight: bold;">data_output_format |
|---|
| 503 | </span>= <span style="font-style: italic;">'avs'</span>, |
|---|
| 504 | the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>. |
|---|
| 505 | Output is in FORTRAN binary format readable by |
|---|
| 506 | the plot software <span style="font-weight: bold;">AVS</span>. |
|---|
| 507 | The order of data on the file follows the order used in the assignment |
|---|
| 508 | for <b>data_output</b> (e.g. <b>data_output</b> |
|---|
| 509 | = <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,... |
|---|
| 510 | means that the file starts with the pressure data, followed by the |
|---|
| 511 | v-component of the velocity, etc.). Both instantaneous and time |
|---|
| 512 | averaged data are written on this file! Additional to this file, PALM |
|---|
| 513 | creates |
|---|
| 514 | a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>) |
|---|
| 515 | with coordinate information needed by <span style="font-weight: bold;">AVS</span>. |
|---|
| 516 | As third and |
|---|
| 517 | fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a> |
|---|
| 518 | and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>), |
|---|
| 519 | which describe the contents of the data file and/or coordinate file |
|---|
| 520 | and are used by AVS. However, AVS expects the content description in |
|---|
| 521 | one file. This needs the local file PLOT3D_FLD_COOR to be appended to |
|---|
| 522 | the file |
|---|
| 523 | PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span> |
|---|
| 524 | configuration file: “<span style="font-family: monospace;">cat |
|---|
| 525 | PLOT3D_FLD_COOR >> PLOT3D_FLD</span>”) |
|---|
| 526 | after PALM has |
|---|
| 527 | finished. To reduce the amount of data, output to this file |
|---|
| 528 | can be done |
|---|
| 529 | in |
|---|
| 530 | compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>). |
|---|
| 531 | Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in |
|---|
| 532 | <a href="chapter_4.5.5.html">chapter |
|---|
| 533 | 4.5.5</a>.</p>By assigning <span style="font-weight: bold;">data_output_format </span>= |
|---|
| 534 | <span style="font-style: italic;">'iso2d'</span>, |
|---|
| 535 | the cross section data is output to the local files <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>, <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>, and <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>. |
|---|
| 536 | Output is in FORTRAN binary format readable by |
|---|
| 537 | the plot software <span style="font-weight: bold;">iso2d</span>. |
|---|
| 538 | The order of data on the files follows the order used in the assignment |
|---|
| 539 | for <b>data_output</b> (e.g. <b>data_output</b> |
|---|
| 540 | = <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,... |
|---|
| 541 | means that the file containing the horizontal cross section data starts |
|---|
| 542 | with the instantaneous pressure data, followed by the |
|---|
| 543 | temporally averaged v-component of the velocity, etc.). Both |
|---|
| 544 | instantaneous and time averaged data are written on this |
|---|
| 545 | file!Additional to these binary files, PALM |
|---|
| 546 | creates NAMELIST parameter files |
|---|
| 547 | (local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>, |
|---|
| 548 | <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>, |
|---|
| 549 | <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>, |
|---|
| 550 | <a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>, |
|---|
| 551 | <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>, |
|---|
| 552 | <a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>) |
|---|
| 553 | which can be used as parameter input files for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>. |
|---|
| 554 | That needs local files with suffix _LOCAL to be appended to the |
|---|
| 555 | respective files with suffix _GLOBAL (by |
|---|
| 556 | suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span> |
|---|
| 557 | configuration file, e.g.: “<span style="font-family: monospace;">cat |
|---|
| 558 | PLOT2D_XY_LOCAL >> PLOT2D_XY_GLOBAL</span>”) |
|---|
| 559 | after PALM has |
|---|
| 560 | finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the |
|---|
| 561 | respective data and |
|---|
| 562 | parameter file. The plot layout is steered via the parameter input |
|---|
| 563 | file. |
|---|
| 564 | The values of these <span style="font-weight: bold;">iso2d</span> |
|---|
| 565 | parameters are determined by a set of mostly internal PALM parameters |
|---|
| 566 | (exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>). |
|---|
| 567 | All parameter values can be changed by editing the parameter input |
|---|
| 568 | file. Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found |
|---|
| 569 | in <a href="chapter_4.5.4.html">chapter |
|---|
| 570 | 4.5.4</a>.<br><br><span style="font-weight: bold;">Important:</span><br>There |
|---|
| 571 | is no guarantee that iso2d- and avs-output will be available in future |
|---|
| 572 | PALM versions (later than 3.0). </td> </tr> <tr> <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br> |
|---|
| 573 | </td> <td style="vertical-align: top;">C * 10 (10) </td> |
|---|
| 574 | <td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td> |
|---|
| 575 | <td style="vertical-align: top;">Format of output data.<br><br>By |
|---|
| 576 | default, all data (profiles, time |
|---|
| 577 | series, spectra, particle data, cross sections, volume data) are output |
|---|
| 578 | in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>). |
|---|
| 579 | Exception: restart data (local files <a href="chapter_3.4.html#BININ">BININ</a>, <a href="chapter_3.4.html#BINOUT">BINOUT</a>, <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>, |
|---|
| 580 | <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>) |
|---|
| 581 | are always output in FORTRAN binary format.<br><br>The |
|---|
| 582 | numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br><br>The |
|---|
| 583 | maximum file size for NetCDF files is 2 GByte by default. Use the |
|---|
| 584 | parameter <a href="#netcdf_64bit">netcdf_64bit</a> |
|---|
| 585 | if larger files have to be created.<br><br>For historical |
|---|
| 586 | reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span> |
|---|
| 587 | may be assigned the following values:<br><br><table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td><td>output |
|---|
| 588 | of profiles, time series and spectra in ASCII format to be |
|---|
| 589 | read by the graphic software <span style="font-weight: bold;">profil |
|---|
| 590 | </span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>, |
|---|
| 591 | <a href="#chapter_4.5.3.html">4.5.3</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td><td>output |
|---|
| 592 | of 2d cross-sections in FORTRAN binary format to be read by the graphic |
|---|
| 593 | software <span style="font-weight: bold;">iso2d</span> |
|---|
| 594 | (see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td><td>output |
|---|
| 595 | of 3d volume data in FORTRAN binary format to be read by the graphic |
|---|
| 596 | software <span style="font-weight: bold;">AVS</span> |
|---|
| 597 | (see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td></tr></tbody></table><br>Multiple |
|---|
| 598 | values can be assigned to <span style="font-weight: bold;">data_output_format</span>, |
|---|
| 599 | i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as |
|---|
| 600 | cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> = |
|---|
| 601 | <span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be |
|---|
| 602 | assigned.<br><br><span style="font-weight: bold;">Warning:</span> |
|---|
| 603 | There is no guarantee that the "old" formats will be available in |
|---|
| 604 | future PALM versions (beyond 3.0)!<br> </td> </tr> <tr> |
|---|
| 605 | <td style="vertical-align: top;"> <p><a name="data_output_pr"></a><b>data_output_pr</b></p> |
|---|
| 606 | </td> <td style="vertical-align: top;">C * |
|---|
| 607 | 10 <br> |
|---|
| 608 | (100)</td> <td style="vertical-align: top;"><i>100 |
|---|
| 609 | * ' '</i></td> <td style="vertical-align: top;"> |
|---|
| 610 | <p>Quantities for which vertical profiles (horizontally averaged) |
|---|
| 611 | are to be output. </p> <p>By default vertical |
|---|
| 612 | profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>. |
|---|
| 613 | The file's format is NetCDF. Further details about processing |
|---|
| 614 | NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>For |
|---|
| 615 | historical reasons, data can also be output in ASCII-format on local |
|---|
| 616 | file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a> |
|---|
| 617 | which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See |
|---|
| 618 | parameter <a href="#data_output_format">data_output_format</a> |
|---|
| 619 | for defining the format in which data shall be output.<br> </p> |
|---|
| 620 | <p>For horizontally averaged vertical |
|---|
| 621 | profiles always <span style="font-weight: bold;">all</span> |
|---|
| 622 | vertical |
|---|
| 623 | grid points (0 <= k <= nz+1) are output to file. Vertical |
|---|
| 624 | profile data refers to the total domain but profiles for subdomains can |
|---|
| 625 | also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>). |
|---|
| 626 | </p> <p>The temporal interval of the output times of |
|---|
| 627 | profiles is |
|---|
| 628 | assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>. |
|---|
| 629 | Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>, |
|---|
| 630 | the profiles are ordered with respect to their |
|---|
| 631 | output times.</p><p>Profiles can also be temporally |
|---|
| 632 | averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>). <br> |
|---|
| 633 | </p> <p>The following list shows the values which can be |
|---|
| 634 | assigned to <span style="font-weight: bold;">data_output_pr</span>. |
|---|
| 635 | The profile data is either defined on |
|---|
| 636 | u-v-levels (variables marked in <font color="#ff6600">red</font>) |
|---|
| 637 | or |
|---|
| 638 | on w-levels (<font color="#33ff33">green</font>). |
|---|
| 639 | According to this, |
|---|
| 640 | the |
|---|
| 641 | z-coordinates of the individual profiles vary. Beyond that, with a |
|---|
| 642 | Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>) |
|---|
| 643 | the lowest output |
|---|
| 644 | level is z = zu(1) instead of z = zw(0) for profiles <i>w'' |
|---|
| 645 | u'',w''v"</i>, <i>wu</i> and <i>wv</i> |
|---|
| 646 | . <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td> |
|---|
| 647 | <td style="vertical-align: top;">u-component of the |
|---|
| 648 | velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td> |
|---|
| 649 | <td style="vertical-align: top;">v-component of the |
|---|
| 650 | velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td> |
|---|
| 651 | <td style="vertical-align: top;">w-component of the |
|---|
| 652 | velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td> |
|---|
| 653 | <td style="vertical-align: top;">Potential temperature (in |
|---|
| 654 | K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td> |
|---|
| 655 | <td style="vertical-align: top;">Virtual potential |
|---|
| 656 | temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td> |
|---|
| 657 | <td style="vertical-align: top;">Potential liquid water |
|---|
| 658 | temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td> |
|---|
| 659 | <td style="vertical-align: top;">Total water content |
|---|
| 660 | (in kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td> |
|---|
| 661 | <td style="vertical-align: top;">Specific humidity (in |
|---|
| 662 | kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td> |
|---|
| 663 | <td style="vertical-align: top;">Liquid water content |
|---|
| 664 | (in kg/kg).</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600">s</font></td> |
|---|
| 665 | <td style="vertical-align: top;">Scalar concentration (in |
|---|
| 666 | kg/m<sup>3</sup>).</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td> |
|---|
| 667 | <td style="vertical-align: top;">Turbulent kinetic energy |
|---|
| 668 | (TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td> |
|---|
| 669 | </tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td> |
|---|
| 670 | <td style="vertical-align: top;">Perturbation energy |
|---|
| 671 | (resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td> |
|---|
| 672 | </tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td> |
|---|
| 673 | <td style="vertical-align: top;">Eddy diffusivity for |
|---|
| 674 | momentum (in m<sup>2</sup>/s).</td> </tr> <tr> |
|---|
| 675 | <td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td> |
|---|
| 676 | <td style="vertical-align: top;">Eddy diffusivity for heat |
|---|
| 677 | (in m<sup>2</sup>/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td> |
|---|
| 678 | <td style="vertical-align: top;">Mixing length (in m).</td> |
|---|
| 679 | </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td> |
|---|
| 680 | <td style="vertical-align: top;">u-component of the |
|---|
| 681 | subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td> |
|---|
| 682 | </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td> |
|---|
| 683 | <td style="vertical-align: top;">u-component of the |
|---|
| 684 | resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td> |
|---|
| 685 | </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td> |
|---|
| 686 | <td style="vertical-align: top;">u-component of the total |
|---|
| 687 | vertical momentum flux (<i>w"u"</i> + <i>w*u*</i>) |
|---|
| 688 | (in m<sup>2</sup>/s<sup>2</sup>).</td> </tr> |
|---|
| 689 | <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td> |
|---|
| 690 | <td style="vertical-align: top;">v-component of the |
|---|
| 691 | subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td> |
|---|
| 692 | </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td> |
|---|
| 693 | <td style="vertical-align: top;">v-component of the |
|---|
| 694 | resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td> |
|---|
| 695 | </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td> |
|---|
| 696 | <td style="vertical-align: top;">v-component of the total |
|---|
| 697 | vertical momentum flux (<i>w"v"</i> + <i>w*v*</i>) |
|---|
| 698 | (in m<sup>2</sup>/s<sup>2</sup>).</td> </tr> |
|---|
| 699 | <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td> |
|---|
| 700 | <td style="vertical-align: top;">Subgrid-scale vertical |
|---|
| 701 | sensible heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td> |
|---|
| 702 | <td style="vertical-align: top;">Resolved vertical |
|---|
| 703 | sensible |
|---|
| 704 | heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td> |
|---|
| 705 | <td style="vertical-align: top;">Total vertical sensible |
|---|
| 706 | heat flux (<i>w"pt"</i> + <i>w*pt*</i>) |
|---|
| 707 | (in K |
|---|
| 708 | m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td> |
|---|
| 709 | <td style="vertical-align: top;">Subgrid-scale vertical |
|---|
| 710 | sensible heat flux using the |
|---|
| 711 | Bott-Chlond scheme (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td> |
|---|
| 712 | <td style="vertical-align: top;">Total vertical sensible |
|---|
| 713 | heat flux using the Bott-Chlond scheme |
|---|
| 714 | (<i>w"pt"</i> |
|---|
| 715 | + <i>w*pt*BC</i>) (in K m/s).</td> </tr> <tr> |
|---|
| 716 | <td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td> |
|---|
| 717 | <td style="vertical-align: top;">Subgrid-scale vertical |
|---|
| 718 | buoyancy flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td> |
|---|
| 719 | <td style="vertical-align: top;">Resolved vertical |
|---|
| 720 | buoyancy |
|---|
| 721 | flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td> |
|---|
| 722 | <td style="vertical-align: top;">Total vertical buoyancy |
|---|
| 723 | flux (w"vpt" + w*vpt*) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td> |
|---|
| 724 | <td style="vertical-align: top;">Subgrid-scale vertical |
|---|
| 725 | water flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td> |
|---|
| 726 | <td style="vertical-align: top;">Resolved vertical water |
|---|
| 727 | flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td> |
|---|
| 728 | <td style="vertical-align: top;">Total vertical water flux |
|---|
| 729 | (w"q" + w*q*) (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td> |
|---|
| 730 | <td style="vertical-align: top;">Subgrid-scale vertical |
|---|
| 731 | latent heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td> |
|---|
| 732 | <td style="vertical-align: top;">Resolved vertical latent |
|---|
| 733 | heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td> |
|---|
| 734 | <td style="vertical-align: top;">Total vertical latent |
|---|
| 735 | heat |
|---|
| 736 | flux (w"qv" + w*qv*) (in kg/kg m/s).</td> </tr> <tr> |
|---|
| 737 | <td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td> |
|---|
| 738 | <td style="vertical-align: top;">Subgrid-scale vertical |
|---|
| 739 | scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td> |
|---|
| 740 | </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td> |
|---|
| 741 | <td style="vertical-align: top;">Resolved vertical scalar |
|---|
| 742 | concentration flux (in kg/m<sup>3</sup>)</td> </tr> |
|---|
| 743 | <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td> |
|---|
| 744 | <td style="vertical-align: top;">Total vertical scalar |
|---|
| 745 | concentration flux (w"s" + w*s*) (in kg/m<sup>3 </sup>m/s).</td> |
|---|
| 746 | </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td> |
|---|
| 747 | <td style="vertical-align: top;">Vertical flux of |
|---|
| 748 | perturbation energy (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td> |
|---|
| 749 | <td style="vertical-align: top;">Variance of the |
|---|
| 750 | u-velocity |
|---|
| 751 | component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td> |
|---|
| 752 | <td style="vertical-align: top;">Variance of the |
|---|
| 753 | v-velocity |
|---|
| 754 | component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td> |
|---|
| 755 | <td style="vertical-align: top;">Variance of the potential |
|---|
| 756 | temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td> |
|---|
| 757 | <td style="vertical-align: top;">Variance of the potential |
|---|
| 758 | temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td> |
|---|
| 759 | <td style="vertical-align: top;">Third moment of the |
|---|
| 760 | w-velocity component (resolved)</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td> |
|---|
| 761 | <td style="vertical-align: top;">Skewness of the |
|---|
| 762 | w-velocity |
|---|
| 763 | component (resolved, S<sub>w</sub> |
|---|
| 764 | = W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td> |
|---|
| 765 | </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td> |
|---|
| 766 | <td style="vertical-align: top;">Third moment (resolved)</td> |
|---|
| 767 | </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td> |
|---|
| 768 | <td style="vertical-align: top;">Third moment (resolved)</td> |
|---|
| 769 | </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*/dz</i></font></td> |
|---|
| 770 | <td style="vertical-align: top;">Energy production by |
|---|
| 771 | shear |
|---|
| 772 | (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*/dz</i></font></td> |
|---|
| 773 | <td style="vertical-align: top;">Energy production by |
|---|
| 774 | turbulent transport of pressure |
|---|
| 775 | fluctuations (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td> |
|---|
| 776 | <td style="vertical-align: top;">Energy production by |
|---|
| 777 | transport of resolved-scale TKE</td> </tr> </tbody> |
|---|
| 778 | </table> <br> |
|---|
| 779 | Beyond that, initial profiles (t=0) of some variables can be also be |
|---|
| 780 | output (this output is only done once |
|---|
| 781 | with the first plot output and not repeated with the profile output at |
|---|
| 782 | later |
|---|
| 783 | times). The names of these profiles result from the ones specified |
|---|
| 784 | above leaded by a hash "#". Allowed values are:<br> <ul> |
|---|
| 785 | <p><i>#u</i>, <i>#v</i>, <i>#pt</i>, |
|---|
| 786 | <i>#km</i>, <i>#kh</i>, <i>#l</i></p> |
|---|
| 787 | </ul> <p>These initial profiles have been either set by |
|---|
| 788 | the user or |
|---|
| 789 | have been calculated by a 1d-model prerun.<br> </p>In case |
|---|
| 790 | of ASCII data output to local file PLOT1D_DATA, |
|---|
| 791 | PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>) |
|---|
| 792 | which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>. |
|---|
| 793 | Profiles can be directly plotted with <span style="font-weight: bold;">profil</span> |
|---|
| 794 | using these two files. The |
|---|
| 795 | plot layout is |
|---|
| 796 | steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters |
|---|
| 797 | are determined by |
|---|
| 798 | a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>, |
|---|
| 799 | <a href="chapter_4.2.html#profile_rows">profile_rows</a>, |
|---|
| 800 | <a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>, |
|---|
| 801 | <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>, |
|---|
| 802 | etc.) All parameter values can be changed by editing the parameter |
|---|
| 803 | input |
|---|
| 804 | file. <br><br>Further details about plotting vertical |
|---|
| 805 | profiles with <span style="font-weight: bold;">profil </span>can |
|---|
| 806 | be found in <a href="chapter_4.5.2.html">chapter |
|---|
| 807 | 4.5.2</a></td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b> |
|---|
| 808 | <br> <b>_each_pe</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td> |
|---|
| 809 | <td style="vertical-align: top;">Output 2d cross section |
|---|
| 810 | data by one or |
|---|
| 811 | all processors. <p>In runs with several processors, by |
|---|
| 812 | default, each processor |
|---|
| 813 | outputs cross section data of its subdomain into an individual |
|---|
| 814 | file. After PALM |
|---|
| 815 | has finished, the contents of these files have to be sampled into one |
|---|
| 816 | file<span style="font-weight: bold;"></span> using |
|---|
| 817 | the program <tt>combine_plot_fields.x</tt>. </p> |
|---|
| 818 | <p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b> |
|---|
| 819 | = <i>.F.,</i> |
|---|
| 820 | the respective data is gathered on PE0 and output is done directly |
|---|
| 821 | into one file, so <tt>combine_plot_fields.x</tt> does not |
|---|
| 822 | have to be |
|---|
| 823 | called. However, in case of very large numbers of horizontal |
|---|
| 824 | gridpoints, sufficient |
|---|
| 825 | memory is required on PE0. </p> </td> </tr> |
|---|
| 826 | <tr> <td style="vertical-align: top;"> <p><a name="disturbance_amplitude"></a><b>disturbance<br> |
|---|
| 827 | _amplitude</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.25</i></td> |
|---|
| 828 | <td style="vertical-align: top;"> <p>Maximum |
|---|
| 829 | perturbation amplitude of the random perturbations |
|---|
| 830 | imposed to the horizontal velocity field (in m/s). </p> |
|---|
| 831 | <p>The parameter <a href="#create_disturbances">create_disturbances</a> |
|---|
| 832 | describes how to impose random perturbations to the horizontal velocity |
|---|
| 833 | field. Since the perturbation procedure includes two filter operations, |
|---|
| 834 | the amplitude assigned by <b>disturbance_amplitude</b> is |
|---|
| 835 | only an |
|---|
| 836 | approximate value of the real magnitude of the perturbation.</p> </td> |
|---|
| 837 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 838 | <p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b> |
|---|
| 839 | <br> <b>_limit</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.01</i></td> |
|---|
| 840 | <td style="vertical-align: top;"> <p lang="en-GB">Upper |
|---|
| 841 | limit value of the perturbation energy of |
|---|
| 842 | the velocity field used as a criterion for imposing random |
|---|
| 843 | perturbations (in m<sup>2</sup>/s<sup>2</sup>). |
|---|
| 844 | </p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB"> |
|---|
| 845 | describes how to impose |
|---|
| 846 | random perturbations to the horizontal velocity field. The perturbation |
|---|
| 847 | energy is defined as the volume average (over the total model domain) |
|---|
| 848 | of the squares of the deviations of the velocity components from the |
|---|
| 849 | mean flow (horizontal average). If the perturbation energy exceeds the |
|---|
| 850 | assigned value, random perturbations to the fields of horizontal |
|---|
| 851 | velocities are imposed no more. The value of this parameter usually |
|---|
| 852 | must be determined by trial and error (it depends e.g. on the total |
|---|
| 853 | number of grid points).</span> </font> </p> </td> |
|---|
| 854 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 855 | <p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p> |
|---|
| 856 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 857 | <td style="vertical-align: top;"><i>zu(3)</i></td> |
|---|
| 858 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower |
|---|
| 859 | limit of the vertical range for which random perturbations are to be |
|---|
| 860 | imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m). |
|---|
| 861 | </font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This |
|---|
| 862 | parameter must hold the condition zu<i>(3)</i> <= <b>disturbance_level_b</b> |
|---|
| 863 | <= <i>zu(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">. |
|---|
| 864 | Additionally, <b>disturbance_level_b</b> |
|---|
| 865 | <= </font></span><a href="#disturbance_level_t"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_t</font></span></a> |
|---|
| 866 | <span lang="en-GB"><font face="Thorndale, serif">must |
|---|
| 867 | also hold. <br> </font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">The |
|---|
| 868 | parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB"> |
|---|
| 869 | describes how to impose |
|---|
| 870 | random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span> |
|---|
| 871 | </font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p> |
|---|
| 872 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 873 | <td style="vertical-align: top;"><i>zu(nz/3)</i></td> |
|---|
| 874 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper |
|---|
| 875 | limit of the vertical range for which random perturbations are to be |
|---|
| 876 | imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m). |
|---|
| 877 | </font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This |
|---|
| 878 | parameter must hold the condition <b>disturbance_level_t</b> |
|---|
| 879 | <= zu<i>(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">. |
|---|
| 880 | Additionally, </font></span><a href="#disturbance_level_b"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_b</font></span></a> |
|---|
| 881 | <span lang="en-GB"><font face="Thorndale, serif"><= |
|---|
| 882 | <b>disturbance_level_t</b> |
|---|
| 883 | must also hold.<br> </font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">The |
|---|
| 884 | parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB"> |
|---|
| 885 | describes how to impose |
|---|
| 886 | random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span> |
|---|
| 887 | </font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p> |
|---|
| 888 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 889 | <td style="vertical-align: top;">.F.<br> </td> |
|---|
| 890 | <td style="vertical-align: top;"> <p>Output of 2d |
|---|
| 891 | cross section data at the beginning of a run. </p> <p>The |
|---|
| 892 | temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>) |
|---|
| 893 | are usually determined with parameters <a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_xy</a>, <a href="chapter_4.2.html#dt_do2d_xz">dt_do2d_xz</a> |
|---|
| 894 | and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>. |
|---|
| 895 | By assigning <b>do2d_at_begin</b> = <i>.T.</i> |
|---|
| 896 | an additional output |
|---|
| 897 | will be made at the |
|---|
| 898 | beginning of a run (thus at the time t = 0 or at the respective |
|---|
| 899 | starting times of restart runs).</p> </td> </tr> <tr> |
|---|
| 900 | <td style="vertical-align: top;"> <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p> |
|---|
| 901 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 902 | <td style="vertical-align: top;">.F.<br> </td> |
|---|
| 903 | <td style="vertical-align: top;">Output of 3d volume data |
|---|
| 904 | at the beginning |
|---|
| 905 | of a run.<br><br>The temporal intervals of output times of |
|---|
| 906 | 3d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>) |
|---|
| 907 | is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>. |
|---|
| 908 | By assigning <b>do3d_at_begin</b> = <i>.T.</i> |
|---|
| 909 | an additional output |
|---|
| 910 | will be made at the |
|---|
| 911 | beginning of a run (thus at the time t = 0 or at the respective |
|---|
| 912 | starting times of restart runs).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_compress"></a><b>do3d_compress</b></p> |
|---|
| 913 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 914 | <td style="vertical-align: top;">.F.<br> </td> |
|---|
| 915 | <td style="vertical-align: top;"> <p>Output of data |
|---|
| 916 | for 3d plots in compressed form. </p> <p>This |
|---|
| 917 | parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 918 | = <span style="font-style: italic;">'avs'</span>.</p><p>Output |
|---|
| 919 | of 3d volume data may need huge amounts of disc storage |
|---|
| 920 | (up to several Terabytes ore more). Data compression can serve to |
|---|
| 921 | reduce this requirement. PALM is able to output 3d data in compressed |
|---|
| 922 | form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span> |
|---|
| 923 | = <span style="font-style: italic;">.T.</span> is |
|---|
| 924 | assigned. This |
|---|
| 925 | yields a loss of accuracy, but the file size is clearly reduced. The |
|---|
| 926 | parameter <a href="chapter_4.2.html#do3d_precision">do3d_precision</a> |
|---|
| 927 | can be used to separately define the number of significant digits for |
|---|
| 928 | each quantity.<br> </p> <p>So far compressed data |
|---|
| 929 | output is only possible for Cray-T3E |
|---|
| 930 | machines. Additional information for |
|---|
| 931 | handling compressed data is given in <a href="chapter_4.5.6.html">chapter |
|---|
| 932 | 4.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_precision"></a><b>do3d_precision</b></p> |
|---|
| 933 | </td> <td style="vertical-align: top;">C * |
|---|
| 934 | 7 <br> |
|---|
| 935 | (100)</td> <td style="vertical-align: top;">see |
|---|
| 936 | right<br> </td> <td style="vertical-align: top;"> |
|---|
| 937 | <p>Significant digits in case of compressed data |
|---|
| 938 | output. </p> <p>This parameter only applies for |
|---|
| 939 | <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 940 | = <span style="font-style: italic;">'avs'</span>.</p><p>In |
|---|
| 941 | case that data compression is used for output of 3d data |
|---|
| 942 | (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>), |
|---|
| 943 | this parameter determines the number of significant digits |
|---|
| 944 | which are to be output.<br> </p> <p>Fewer digits |
|---|
| 945 | clearly reduce the amount |
|---|
| 946 | of data. Assignments have to be given separately for each individual |
|---|
| 947 | quantity via a character string of the form <span style="font-style: italic;">'<quantity |
|---|
| 948 | name><number of |
|---|
| 949 | significant digits>'</span>, e.g. <span style="font-style: italic;">'pt2'</span>. |
|---|
| 950 | Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a> |
|---|
| 951 | are admitted. Up to 9 significant digits are allowed (but large values |
|---|
| 952 | are not very reasonable |
|---|
| 953 | because they do not effect a significant compression).<br> </p> |
|---|
| 954 | <p>The default assignment is <span style="font-weight: bold;">do3d_precision</span> |
|---|
| 955 | = <span style="font-style: italic;">'u2'</span>, <span style="font-style: italic;">'v2'</span>, <span style="font-style: italic;">'w2'</span>, <span style="font-style: italic;">'p5'</span>, <span style="font-style: italic;">'pt2'</span>.</p> </td> |
|---|
| 956 | </tr> |
|---|
| 957 | <tr> <td style="vertical-align: top;"> <p><a name="dt_laufparameter"></a><b>dt</b></p> |
|---|
| 958 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 959 | <td style="vertical-align: top;"><i>variable</i></td> |
|---|
| 960 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Time |
|---|
| 961 | step to be used by the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s). |
|---|
| 962 | </font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This parameter</font></span> |
|---|
| 963 | <font face="Thorndale, serif"><span lang="en-GB">is |
|---|
| 964 | described in |
|---|
| 965 | detail with the initialization parameters (see</span></font><span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB">). |
|---|
| 966 | Additionally, it may be |
|---|
| 967 | used as a run parameter and then applies to all restart runs (until it |
|---|
| 968 | is changed again). A switch from a constant time step to a variable |
|---|
| 969 | time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span> |
|---|
| 970 | </font> </p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br> |
|---|
| 971 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 972 | <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td> |
|---|
| 973 | <td style="vertical-align: top;">Temporal interval |
|---|
| 974 | of data which are subject to temporal averaging (in s).<br><br>By |
|---|
| 975 | default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a> |
|---|
| 976 | are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span> |
|---|
| 977 | > <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>, |
|---|
| 978 | the number of time levels entering the average can be minimized. This |
|---|
| 979 | reduces the CPU-time of a run but may worsen the quality of the |
|---|
| 980 | average's statistics.<br><br><font face="Thorndale, serif"><span lang="en-GB">With |
|---|
| 981 | variable time step (see <span style="font-weight: bold;">dt</span>), |
|---|
| 982 | the number of time levels entering the average can vary from one |
|---|
| 983 | averaging interval to the next (for a more detailed explanation see </span></font><font><a href="#averaging_interval"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval</font></span></a>)</font><font face="Thorndale, serif"><span lang="en-GB">. It |
|---|
| 984 | is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> / |
|---|
| 985 | MAX(<span style="font-weight: bold;"> dt_averaging_input</span>, |
|---|
| 986 | <span style="font-weight: bold;">dt</span>) (which |
|---|
| 987 | gives a more or less exact value if a fixed timestep is used and if |
|---|
| 988 | this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font> |
|---|
| 989 | <br><br><span style="font-weight: bold;">Example:</span><br>With |
|---|
| 990 | an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> = |
|---|
| 991 | <span style="font-style: italic;">10.0</span>, |
|---|
| 992 | the time levels entering the average have a (minimum) distance of 10.0 |
|---|
| 993 | s (their distance may of course be larger if the current timestep is |
|---|
| 994 | larger than 10.0 s), so the average is calculated from the data of |
|---|
| 995 | (maximum) 10 time levels.<br><br><font face="Thorndale, serif"><span lang="en-GB">It |
|---|
| 996 | is allowed |
|---|
| 997 | to change <b>dt_averaging_input</b> during a job chain. If |
|---|
| 998 | the last averaging |
|---|
| 999 | interval of the run previous to the change could not be completed (i.e. |
|---|
| 1000 | has to be finished in the current run), the individual profiles and/or |
|---|
| 1001 | spectra entering the averaging are not uniformly distributed over the |
|---|
| 1002 | averaging interval.<br><br></span></font>Parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a> can |
|---|
| 1003 | be used to define a different temporal interval for |
|---|
| 1004 | vertical profile data and spectra.<br> </td> </tr> |
|---|
| 1005 | <tr> <td style="vertical-align: top;"> <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p> |
|---|
| 1006 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1007 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>averaging_<br>input</a></span></td> |
|---|
| 1008 | <td style="vertical-align: top;"> <p lang="en-GB">Temporal |
|---|
| 1009 | interval of data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical |
|---|
| 1010 | profiles and/or spectra (</font></font>in <font face="Thorndale, serif"><font size="3">s). |
|---|
| 1011 | </font></font> </p> <p>By default, data from |
|---|
| 1012 | each timestep within the interval defined by<font face="Thorndale, serif"><span lang="en-GB"> </span></font><a href="#averaging_interval_pr"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_pr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><span lang="en-GB"><font face="Thorndale, serif">and </font></span><a href="#averaging_interval_sp"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_sp</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> </font></span>are |
|---|
| 1013 | used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span> |
|---|
| 1014 | > <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>, |
|---|
| 1015 | the number of time levels entering the average can be minimized. This |
|---|
| 1016 | reduces the CPU-time of a run but may worsen the quality of the |
|---|
| 1017 | average's statistics. <span lang="en-GB"><font face="Thorndale, serif"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span></font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><br> </p><p>For |
|---|
| 1018 | more explanations see parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font></p></td> |
|---|
| 1019 | </tr> <tr> <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br> |
|---|
| 1020 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1021 | <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br> |
|---|
| 1022 | </td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> |
|---|
| 1023 | at which data (3d volume data (instantaneous or time |
|---|
| 1024 | averaged), |
|---|
| 1025 | cross sections (instantaneous or time averaged), vertical profiles, |
|---|
| 1026 | spectra) shall be output (</font>in <font face="Thorndale">s). </font></p> |
|---|
| 1027 | <span lang="en-GB"><font face="Thorndale">If |
|---|
| 1028 | data output is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">, <a href="#data_output_pr">data_output_pr</a>, <a href="#data_output_sp">data_output_sp</a>, and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this |
|---|
| 1029 | parameter can be used to |
|---|
| 1030 | assign the temporal interval at which these data shall be |
|---|
| 1031 | output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a |
|---|
| 1032 | simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>, |
|---|
| 1033 | which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1034 | time is the beginning of the simulation, i.e. output |
|---|
| 1035 | takes place at times t = <b>skip_time_data_output + |
|---|
| 1036 | dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span> |
|---|
| 1037 | + 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span> |
|---|
| 1038 | + 3*<b>dt_data_output</b>, |
|---|
| 1039 | etc. Since output is only done at the discrete time levels given by |
|---|
| 1040 | the timestep used, the actual output times can slightly |
|---|
| 1041 | deviate |
|---|
| 1042 | from these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br>Individual temporal |
|---|
| 1043 | intervals for the different output quantities can be assigned using |
|---|
| 1044 | parameters <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="dt_do2d_xz">dt_do2d_xz</a>, <a href="#dt_do2d_yz">dt_do2d_yz</a>, <a href="#dt_dopr">dt_dopr</a>, <a href="#dt_dosp">dt_dosp</a>, |
|---|
| 1045 | and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span> |
|---|
| 1046 | </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br> |
|---|
| 1047 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1048 | <td style="vertical-align: top;"><i>value of |
|---|
| 1049 | <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i> |
|---|
| 1050 | </td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> |
|---|
| 1051 | at which time averaged 3d volume data and/or 2d cross section data |
|---|
| 1052 | shall be output (</font>in <font face="Thorndale">s). </font></p><span lang="en-GB"><font face="Thorndale">If data |
|---|
| 1053 | output of time averaged 2d and 3d data is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a> <span lang="en-GB"><font face="Thorndale">and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this |
|---|
| 1054 | parameter can be used to |
|---|
| 1055 | assign the temporal interval at which they shall be |
|---|
| 1056 | output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a |
|---|
| 1057 | simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>, |
|---|
| 1058 | which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1059 | time is the beginning of the simulation, i.e. output |
|---|
| 1060 | takes place at times t = <b>skip_time_data_output_av + |
|---|
| 1061 | dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span> |
|---|
| 1062 | + 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span> |
|---|
| 1063 | + 3*<b>dt_data_output_av</b>, |
|---|
| 1064 | etc. Since output is only done at the discrete time levels given by |
|---|
| 1065 | the timestep used, the actual output times can slightly |
|---|
| 1066 | deviate from |
|---|
| 1067 | these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br></font></span>The |
|---|
| 1068 | length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td> |
|---|
| 1069 | </tr> |
|---|
| 1070 | <tr> <td style="vertical-align: top;"> <p><a name="dt_disturb"></a><b>dt_disturb</b></p> |
|---|
| 1071 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1072 | <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 1073 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1074 | interval</font> at which random |
|---|
| 1075 | perturbations are to be imposed on the horizontal velocity field |
|---|
| 1076 | (</font>in <font face="Thorndale">s). </font> |
|---|
| 1077 | </p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB"> |
|---|
| 1078 | describes how to impose |
|---|
| 1079 | random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span> |
|---|
| 1080 | </font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_dopr"></a><b>dt_dopr</b></p> |
|---|
| 1081 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1082 | <td style="vertical-align: top;"><i>value of |
|---|
| 1083 | <a href="#dt_data_output">dt_data_<br>output</a></i></td> |
|---|
| 1084 | <td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale">Temporal |
|---|
| 1085 | interval at |
|---|
| 1086 | which data of vertical profiles shall be output (to local |
|---|
| 1087 | file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a> |
|---|
| 1088 | or/and </font></span><a href="chapter_3.4.html#PLOT1D_DATA"><span lang="en-GB"><font face="Thorndale">PLOT1D_DATA</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in |
|---|
| 1089 | <span lang="en-GB"><font face="Thorndale">s). |
|---|
| 1090 | </font></span> </p> <p><span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 1091 | horizontally averaged vertical profiles is switched on (see </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this |
|---|
| 1092 | parameter can be used to |
|---|
| 1093 | assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> </font></span><span lang="en-GB"><font face="Thorndale">Output can |
|---|
| 1094 | be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has |
|---|
| 1095 | zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1096 | time is the beginning |
|---|
| 1097 | of the simulation, thus t = 0, </font></span><span lang="en-GB"><font face="Thorndale">i.e. output |
|---|
| 1098 | takes place at times t = <b>skip_time_dopr + dt_dopr</b>, <span style="font-weight: bold;">skip_time_dopr</span> + 2*<b>dt_dopr</b>, |
|---|
| 1099 | <span style="font-weight: bold;">skip_time_dopr</span> |
|---|
| 1100 | + 3*<b>dt_dopr</b>, |
|---|
| 1101 | etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since |
|---|
| 1102 | profiles can not be calculated for times lying within a time step |
|---|
| 1103 | interval, the output times can deviate from these theoretical values. |
|---|
| 1104 | If a time step ranges from t = 1799.8 to t = 1800.2, then in the |
|---|
| 1105 | example above the output would take place at t = 1800.2. In general, |
|---|
| 1106 | the output always lie between t = 1800.0 and t = 1800.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If the |
|---|
| 1107 | model uses a variable time step, these |
|---|
| 1108 | deviations from the theoretical output times will of course be |
|---|
| 1109 | different for each output time.<br> </font></span></p> |
|---|
| 1110 | <p><span lang="en-GB"><font face="Thorndale">In |
|---|
| 1111 | order to |
|---|
| 1112 | guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">, |
|---|
| 1113 | <span style="font-weight: bold;">end_time</span> |
|---|
| 1114 | should be equal or a little bit |
|---|
| 1115 | larger than the respective theoretical output time. For example, if <b>dt_dopr</b> |
|---|
| 1116 | = <i>900.0</i><span style="font-style: italic;"> |
|---|
| 1117 | </span>and 3600.0 |
|---|
| 1118 | seconds are to be simulated, then <b>end_time</b> |
|---|
| 1119 | >= 3600.0 should be chosen.</font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span> </font></span> |
|---|
| 1120 | </p> <p><span lang="en-GB"><font face="Thorndale">A selection of |
|---|
| 1121 | profiles to be output can be done via parameter </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">. </font></span> |
|---|
| 1122 | </p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br> |
|---|
| 1123 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1124 | <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 1125 | <td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale, serif">Temporal |
|---|
| 1126 | interval</font> at which data <font face="Thorndale">of |
|---|
| 1127 | vertical |
|---|
| 1128 | profiles shall be output (output for printouts, local file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in |
|---|
| 1129 | <span lang="en-GB"><font face="Thorndale">s). </font></span> |
|---|
| 1130 | </p> <p>T<span lang="en-GB"></span><a href="chapter_4.2.html#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his |
|---|
| 1131 | parameter can be used to |
|---|
| 1132 | assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference |
|---|
| 1133 | time is the beginning |
|---|
| 1134 | of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b> |
|---|
| 1135 | = 1800.0, |
|---|
| 1136 | then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since |
|---|
| 1137 | profiles can not be calculated for times lying within a time step |
|---|
| 1138 | interval, the output times can deviate from these theoretical values. |
|---|
| 1139 | If a time step ranges from t = 1799.8 to t = 1800.2, then in the |
|---|
| 1140 | example above the output would take place at t = 1800.2. In general, |
|---|
| 1141 | the output always lie between t = 1800.0 and t = 1800.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a> <span lang="en-GB"><font face="Thorndale">(numbers |
|---|
| 1142 | are related to |
|---|
| 1143 | the |
|---|
| 1144 | example above). If the model uses a variable time step, these |
|---|
| 1145 | deviations from the theoretical output times will of course be |
|---|
| 1146 | different for each output time.<br> </font></span></p> |
|---|
| 1147 | <p><span lang="en-GB"><font face="Thorndale">In |
|---|
| 1148 | order to |
|---|
| 1149 | guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">, |
|---|
| 1150 | <span style="font-weight: bold;">end_time</span> |
|---|
| 1151 | should be a little bit |
|---|
| 1152 | larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b> |
|---|
| 1153 | = <i>900.0</i><span style="font-style: italic;"> |
|---|
| 1154 | </span>and 3600.0 |
|---|
| 1155 | seconds are to be simulated, then it should be at least <b>end_time</b> |
|---|
| 1156 | > 3600.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If |
|---|
| 1157 | variable time steps are used |
|---|
| 1158 | (which is the default), <span style="font-weight: bold;">dt</span> |
|---|
| 1159 | should be properly estimated. </font></span> </p> |
|---|
| 1160 | <p><span lang="en-GB"><font face="Thorndale">Data |
|---|
| 1161 | and output |
|---|
| 1162 | format of the file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a> |
|---|
| 1163 | <span lang="en-GB"><font face="Thorndale">is |
|---|
| 1164 | internally fixed. In this file |
|---|
| 1165 | the profiles of the most important model variables are arranged in |
|---|
| 1166 | adjacent columns.</font></span> </p> </td> </tr> |
|---|
| 1167 | <tr> <td style="vertical-align: top;"> <p><a name="dt_dots"></a><b>dt_dots</b></p> |
|---|
| 1168 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1169 | <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td> |
|---|
| 1170 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1171 | interval</font> at which time series data shall be |
|---|
| 1172 | output (</font>in <font face="Thorndale">s). </font> |
|---|
| 1173 | </p> <p>The default interval for the output of timeseries |
|---|
| 1174 | is calculated as shown below (this tries to minimize the number of |
|---|
| 1175 | calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p><p style="font-family: Courier New,Courier,monospace;"> |
|---|
| 1176 | IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a> |
|---|
| 1177 | == 0.0 ) THEN<br> |
|---|
| 1178 | <span style="font-weight: bold;">dt_dots</span> = |
|---|
| 1179 | MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br> |
|---|
| 1180 | ELSE<br> |
|---|
| 1181 | <span style="font-weight: bold;">dt_dots</span> = |
|---|
| 1182 | MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a> |
|---|
| 1183 | )<br> |
|---|
| 1184 | ENDIF</p><p>This parameter can be used to |
|---|
| 1185 | assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1186 | time is the beginning of |
|---|
| 1187 | the simulation, i.e. output takes place at times t = <b>dt_dots</b>, |
|---|
| 1188 | 2*<b>dt_dots</b>, 3*<b>dt_dots</b>, etc. The |
|---|
| 1189 | actual output times can |
|---|
| 1190 | deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). |
|---|
| 1191 | Is <b>dt_dots</b> < </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then data |
|---|
| 1192 | of the time series are |
|---|
| 1193 | written after each time step (if this is requested it should be <b>dt_dots</b> |
|---|
| 1194 | = <i>0</i>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">The default |
|---|
| 1195 | value of <span style="font-weight: bold;">dt_dots</span> |
|---|
| 1196 | is calculated as follows:</font></span></p> |
|---|
| 1197 | IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a> |
|---|
| 1198 | == 0.0 ) THEN<br> |
|---|
| 1199 | <span style="font-weight: bold;">dt_dots</span> = |
|---|
| 1200 | MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br> |
|---|
| 1201 | ELSE<br> |
|---|
| 1202 | <span style="font-weight: bold;">dt_dots</span> = |
|---|
| 1203 | MIN( <span style="font-weight: bold;">dt_run_control</span>, |
|---|
| 1204 | <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a> |
|---|
| 1205 | )<br> |
|---|
| 1206 | ENDIF<br><br>(which minimizes the number of calls of |
|---|
| 1207 | routine flow_statistics).<br><p>By default time series data |
|---|
| 1208 | is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>. |
|---|
| 1209 | Because of the default settings of <span style="font-weight: bold;">dt_dots</span>, |
|---|
| 1210 | it will generally be created for each model run. The file's |
|---|
| 1211 | format is NetCDF. Further details about processing NetCDF |
|---|
| 1212 | data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>The |
|---|
| 1213 | file contains the following timeseries quantities (the first column |
|---|
| 1214 | gives the name of the quantities as used in the NetCDF file):<br><table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="font-style: italic; vertical-align: middle;">E<br> |
|---|
| 1215 | </td> <td style="vertical-align: top;">Total |
|---|
| 1216 | kinetic energy of |
|---|
| 1217 | the flow (in m<sup>2</sup>/s<sup>2</sup>) |
|---|
| 1218 | (normalized with respect to the total number of grid points).</td> |
|---|
| 1219 | </tr> <tr> <td style="font-style: italic; vertical-align: middle;">E*<br> |
|---|
| 1220 | </td> <td style="vertical-align: top;">Perturbation |
|---|
| 1221 | kinetic |
|---|
| 1222 | energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup> |
|---|
| 1223 | </sup>(normalized |
|---|
| 1224 | with respect to the total number of grid |
|---|
| 1225 | points)</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">dt<br> |
|---|
| 1226 | </td> <td style="vertical-align: top;">Time step |
|---|
| 1227 | size (in s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td> |
|---|
| 1228 | <td style="vertical-align: top;">Friction velocity (in |
|---|
| 1229 | m/s) |
|---|
| 1230 | (horizontal average).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td> |
|---|
| 1231 | <td style="vertical-align: top;">Vertical velocity scale |
|---|
| 1232 | of |
|---|
| 1233 | the CBL (in m/s) (horizontal average)</td> </tr> <tr> |
|---|
| 1234 | <td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td> |
|---|
| 1235 | <td style="vertical-align: top;">Temperature |
|---|
| 1236 | scale (Prandtl layer), defined as <i>w"pt"0 |
|---|
| 1237 | / </i><i>u<sub>*</sub></i> |
|---|
| 1238 | (horizontal |
|---|
| 1239 | average) (in K).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">umax<br> |
|---|
| 1240 | </td> <td style="vertical-align: top;">Maximum |
|---|
| 1241 | u-component of the |
|---|
| 1242 | velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">vmax<br> |
|---|
| 1243 | </td> <td style="vertical-align: top;">Maximum |
|---|
| 1244 | v-component of the |
|---|
| 1245 | velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wmax<br> |
|---|
| 1246 | </td> <td style="vertical-align: top;">Maximum |
|---|
| 1247 | w-component of the |
|---|
| 1248 | velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_old<br> |
|---|
| 1249 | </td> <td style="vertical-align: top;">Divergence |
|---|
| 1250 | of the velocity |
|---|
| 1251 | field before the pressure |
|---|
| 1252 | solver has been called (normalized with respect to the total number of |
|---|
| 1253 | grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_new</td> |
|---|
| 1254 | <td style="vertical-align: top;">Divergence of the |
|---|
| 1255 | velocity |
|---|
| 1256 | field after the pressure |
|---|
| 1257 | solver has been called (normalized with respect to the total number of |
|---|
| 1258 | grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_wpt</td> |
|---|
| 1259 | <td style="vertical-align: top;">Height of the convective |
|---|
| 1260 | boundary layer (horizontal average) |
|---|
| 1261 | determined by the height of the minimum sensible heat flux (in m).</td> |
|---|
| 1262 | </tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_pt</td> |
|---|
| 1263 | <td style="vertical-align: top;">Height of the convective |
|---|
| 1264 | boundary layer (horizontal average) |
|---|
| 1265 | determined by the temperature profile (in m).</td> </tr> <tr> |
|---|
| 1266 | <td style="vertical-align: top; font-style: italic;">w"pt"0</td> |
|---|
| 1267 | <td style="vertical-align: top;">Subgrid-scale sensible |
|---|
| 1268 | heat flux near the surface (horizontal |
|---|
| 1269 | average) |
|---|
| 1270 | between z = 0 and z = z<sub>p</sub> = zu(1) (there it |
|---|
| 1271 | corresponds to |
|---|
| 1272 | the total heat flux) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w"pt"</td> |
|---|
| 1273 | <td style="vertical-align: top;">Subgrid-scale heat flux |
|---|
| 1274 | (horizontal average) for z = zw(1) (in K |
|---|
| 1275 | m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wpt</td> |
|---|
| 1276 | <td style="vertical-align: top;">Total heat flux |
|---|
| 1277 | (horizontal average) for z = zw(1) (in K m/s).</td> </tr> <tr> |
|---|
| 1278 | <td style="vertical-align: top; font-style: italic;">pt(0)</td> |
|---|
| 1279 | <td style="vertical-align: top;">Potential temperature at |
|---|
| 1280 | the surface (horizontal average) (in K).</td> </tr> <tr> |
|---|
| 1281 | <td style="vertical-align: top; font-style: italic;">pt(zp)</td> |
|---|
| 1282 | <td style="vertical-align: top;">Potential temperature for |
|---|
| 1283 | z = zu(1) (horizontal average) (in K).</td> </tr> <tr> |
|---|
| 1284 | <td style="vertical-align: top; font-style: italic;">splptx</td> |
|---|
| 1285 | <td style="vertical-align: top;">Percentage of grid points |
|---|
| 1286 | using upstream scheme along x with |
|---|
| 1287 | upstream-spline advection switched on.</td> </tr> <tr> |
|---|
| 1288 | <td style="vertical-align: top; font-style: italic;">splpty</td> |
|---|
| 1289 | <td style="vertical-align: top;">Percentage of grid points |
|---|
| 1290 | using upstream scheme along y with |
|---|
| 1291 | upstream-spline |
|---|
| 1292 | advection switched on.</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">splptz</td> |
|---|
| 1293 | <td style="vertical-align: top;">Percentage of grid points |
|---|
| 1294 | using upstream scheme along z with |
|---|
| 1295 | upstream-spline |
|---|
| 1296 | advection switched on.<br> </td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">L</td> |
|---|
| 1297 | <td style="vertical-align: top;">Monin-Obukhov length.</td> |
|---|
| 1298 | </tr> </tbody> </table><br>Additionally, the |
|---|
| 1299 | user can add his own timeseries quantities to the file, by using the |
|---|
| 1300 | user-interface subroutines<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_init">user_init</a> </span>and<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_statistics">user_statistics</a></span>. |
|---|
| 1301 | These routines contain (as comment lines) a simple example how to do |
|---|
| 1302 | this.<br><br>Time series data refers to the total |
|---|
| 1303 | domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>). |
|---|
| 1304 | However, the following time series always present the values of the |
|---|
| 1305 | total model domain (even with output for subdomains): <i>umax</i>, |
|---|
| 1306 | <i>vmax</i>, <i>wmax</i>, <i>div_old</i>, |
|---|
| 1307 | <i>div_new</i>.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p> |
|---|
| 1308 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1309 | <td style="vertical-align: top;"><i>value of |
|---|
| 1310 | <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td> |
|---|
| 1311 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1312 | interval</font> at which horizontal cross section data |
|---|
| 1313 | shall be output (</font>in <font face="Thorndale">s). |
|---|
| 1314 | </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 1315 | horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a> |
|---|
| 1316 | <span lang="en-GB"><font face="Thorndale">and |
|---|
| 1317 | </font></span><a href="#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this |
|---|
| 1318 | parameter can be used to |
|---|
| 1319 | assign the temporal interval at which cross section data shall be |
|---|
| 1320 | output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a |
|---|
| 1321 | simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, |
|---|
| 1322 | which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1323 | time is the beginning of the simulation, i.e. output |
|---|
| 1324 | takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>, |
|---|
| 1325 | <span style="font-weight: bold;">skip_time_do2d_xy</span> |
|---|
| 1326 | + 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span> |
|---|
| 1327 | + 3*<b>dt_do2d_xy</b>, |
|---|
| 1328 | etc. The actual output times can deviate from these theoretical values |
|---|
| 1329 | (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br> |
|---|
| 1330 | </font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a> |
|---|
| 1331 | has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at |
|---|
| 1332 | the time t = 0 or at the |
|---|
| 1333 | respective starting times of restart runs).</font></span> </p> |
|---|
| 1334 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p> |
|---|
| 1335 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1336 | <td style="vertical-align: top;"><i>value of |
|---|
| 1337 | <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td> |
|---|
| 1338 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1339 | interval</font> at which vertical cross sections data |
|---|
| 1340 | (xz) shall be output (</font>in <font face="Thorndale">s). |
|---|
| 1341 | </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 1342 | horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a> |
|---|
| 1343 | <span lang="en-GB"><font face="Thorndale">and |
|---|
| 1344 | </font></span><a href="#section_xz"><span lang="en-GB"><font face="Thorndale">section_xz</font></span></a><span lang="en-GB"><font face="Thorndale">), |
|---|
| 1345 | this parameter can be used to assign the temporal interval at which |
|---|
| 1346 | cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can |
|---|
| 1347 | be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which |
|---|
| 1348 | has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of |
|---|
| 1349 | the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz |
|---|
| 1350 | + dt_do2d_xz</b>, |
|---|
| 1351 | <span style="font-weight: bold;">skip_time_do2d_xz</span> |
|---|
| 1352 | + 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span> |
|---|
| 1353 | + 3*<b>dt_do2d_xz</b>, etc. The actual output times |
|---|
| 1354 | can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br> |
|---|
| 1355 | </font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a> |
|---|
| 1356 | has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at |
|---|
| 1357 | the time t = 0 or at the |
|---|
| 1358 | respective starting times of restart runs).</font></span> </p> |
|---|
| 1359 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p> |
|---|
| 1360 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1361 | <td style="vertical-align: top;"><i>value of |
|---|
| 1362 | <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td> |
|---|
| 1363 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1364 | interval</font> at which vertical cross section data |
|---|
| 1365 | (yz) shall be output (</font>in s<font face="Thorndale">). |
|---|
| 1366 | </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 1367 | horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a> |
|---|
| 1368 | <span lang="en-GB"><font face="Thorndale">and |
|---|
| 1369 | </font></span><a href="#section_yz"><span lang="en-GB"><font face="Thorndale">section_yz</font></span></a><span lang="en-GB"><font face="Thorndale">), |
|---|
| 1370 | this parameter can be used to assign the temporal interval at which |
|---|
| 1371 | cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can |
|---|
| 1372 | be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which |
|---|
| 1373 | has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1374 | time is the beginning of |
|---|
| 1375 | the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz |
|---|
| 1376 | + dt_do2d_yz</b>, |
|---|
| 1377 | <span style="font-weight: bold;">skip_time_do2d_yz</span> |
|---|
| 1378 | + 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz |
|---|
| 1379 | </span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output |
|---|
| 1380 | times |
|---|
| 1381 | can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br> |
|---|
| 1382 | </font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a> |
|---|
| 1383 | has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at |
|---|
| 1384 | the time t = 0 or at the |
|---|
| 1385 | respective starting times of restart runs).</font></span> </p> |
|---|
| 1386 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do3d"></a><b>dt_do3d</b></p> |
|---|
| 1387 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1388 | <td style="vertical-align: top;"><i>value of |
|---|
| 1389 | <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td> |
|---|
| 1390 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1391 | interval</font> at which 3d volume data shall be output (</font>in |
|---|
| 1392 | <font face="Thorndale">s). </font> </p> |
|---|
| 1393 | <p><span lang="en-GB"><font face="Thorndale">If |
|---|
| 1394 | output of |
|---|
| 1395 | 3d-volume data is switched on (see </font></span><font><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>)<span style="font-family: thorndale;">, this parameter can be used |
|---|
| 1396 | to assign |
|---|
| 1397 | th</span></font><span lang="en-GB"><font face="Thorndale">e temporal |
|---|
| 1398 | interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can |
|---|
| 1399 | be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has |
|---|
| 1400 | zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 1401 | time is the |
|---|
| 1402 | beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d |
|---|
| 1403 | + dt_do3d</b>, |
|---|
| 1404 | <span style="font-weight: bold;">skip_time_do3d</span> |
|---|
| 1405 | + 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span> |
|---|
| 1406 | + 3*<b>dt_do3d</b>, etc. The actual output times can |
|---|
| 1407 | deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). <br> |
|---|
| 1408 | </font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do3d_at_begin"><span lang="en-GB"><font face="Thorndale">do3d_at_begin</font></span></a> |
|---|
| 1409 | has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at |
|---|
| 1410 | the time t = 0 or at the |
|---|
| 1411 | respective starting times of restart runs).</font></span> </p> |
|---|
| 1412 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_restart"></a><b>dt_restart</b></p> |
|---|
| 1413 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1414 | <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 1415 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1416 | interval</font> at which a new |
|---|
| 1417 | restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p> <p><span lang="en-GB"><font face="Thorndale">For a |
|---|
| 1418 | description |
|---|
| 1419 | how to assign restart times manually see run time parameter </font></span><a href="#restart_time"><span lang="en-GB"><font face="Thorndale">restart_time</font></span></a><span lang="en-GB"><font face="Thorndale">. <span style="font-weight: bold;">dt_restart</span> |
|---|
| 1420 | does not show any effect, if <span style="font-weight: bold;">restart_time</span> |
|---|
| 1421 | has not been set.</font></span> </p> </td> </tr> |
|---|
| 1422 | <tr> <td style="vertical-align: top;"> <p><a name="dt_run_control"></a><b>dt_run_control</b></p> |
|---|
| 1423 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1424 | <td style="vertical-align: top;"><i>60.0</i></td> |
|---|
| 1425 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 1426 | interval</font> at which run control |
|---|
| 1427 | output is to be made (</font>in <font face="Thorndale">s). |
|---|
| 1428 | </font> </p> <p><span lang="en-GB"><font face="Thorndale">Run control |
|---|
| 1429 | information is output to the local ASCII-file </font></span><a href="chapter_3.4.html#RUN_CONTROL"><span lang="en-GB"><font face="Thorndale">RUN_CONTROL</font></span></a><span lang="en-GB"><font face="Thorndale">. At each |
|---|
| 1430 | output time, one line |
|---|
| 1431 | with information about the size of the time step, maximum speeds, total |
|---|
| 1432 | kinetic energy etc. is written to this file. Reference time is the |
|---|
| 1433 | beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>, |
|---|
| 1434 | 2*<b>dt_run_control</b>, 3*<b>dt_run_control</b>, |
|---|
| 1435 | etc., and always at |
|---|
| 1436 | the beginning of a model run (thus at the time t = 0 or at the |
|---|
| 1437 | respective starting times of restart runs). The actual output times can |
|---|
| 1438 | deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br> |
|---|
| 1439 | </font></span></p> <p><span lang="en-GB"><font face="Thorndale">Run control |
|---|
| 1440 | information is output after each time step can be achieved via <b>dt_run_control</b> |
|---|
| 1441 | = <i>0.0</i>.</font></span> </p> </td> |
|---|
| 1442 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 1443 | <p><a name="end_time"></a><b>end_time</b></p> |
|---|
| 1444 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1445 | <td style="vertical-align: top;"><i>0.0</i></td> |
|---|
| 1446 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Simulation time of the 3D |
|---|
| 1447 | model (</font>in <font face="Thorndale">s). |
|---|
| 1448 | </font> </p> <p><span lang="en-GB"><font face="Thorndale">The simulation time |
|---|
| 1449 | is starting from the beginning of the initialization run (t = 0), not |
|---|
| 1450 | starting from the beginning of the respective restart run.</font></span> |
|---|
| 1451 | </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="force_print_header"></a><b>force_print_header</b></p> |
|---|
| 1452 | </td> <td style="vertical-align: top;">L</td> |
|---|
| 1453 | <td style="vertical-align: top;"><i>.F.</i></td> |
|---|
| 1454 | <td style="vertical-align: top;"> <p>Steering of |
|---|
| 1455 | header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. |
|---|
| 1456 | </p> <p>By default, informations about the model |
|---|
| 1457 | parameters in use are |
|---|
| 1458 | output to the beginning of file RUN_CONTROL for initial runs only |
|---|
| 1459 | (these informations are identical to that which are output to the local |
|---|
| 1460 | file <a href="chapter_3.4.html#HEADER">HEADER</a>). |
|---|
| 1461 | With <b>force_print_header</b> = <i>.T.</i>, |
|---|
| 1462 | these informations are |
|---|
| 1463 | also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a> |
|---|
| 1464 | at restart runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mg_cycles"></a><b>mg_cycles</b></p> |
|---|
| 1465 | </td> <td style="vertical-align: top;">I</td> |
|---|
| 1466 | <td style="vertical-align: top;"><i>-1</i></td> |
|---|
| 1467 | <td style="vertical-align: top;"> <p>Number of |
|---|
| 1468 | cycles to be used with the multi-grid scheme.<br> <br> |
|---|
| 1469 | This parameter determines the number of cycles to be carried out in the |
|---|
| 1470 | multi-grid method used for solving the Poisson equation for |
|---|
| 1471 | perturbation pressure (see <a href="#psolver">psolver</a>). |
|---|
| 1472 | The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br> |
|---|
| 1473 | </p> <br> |
|---|
| 1474 | By default (<b>mg_cyles</b> = <i>- 1</i>), the |
|---|
| 1475 | number of cycles |
|---|
| 1476 | depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>) |
|---|
| 1477 | and may vary from time step to time step. In this case, the CPU time |
|---|
| 1478 | for a run will be difficult to estimate, since it heavily depends on |
|---|
| 1479 | the total number of the cycles to be carried out.<br> <br> |
|---|
| 1480 | By assigning <b>mg_cycles</b> a value (>=<span style="font-style: italic;">1</span>), the number of |
|---|
| 1481 | cycles can be |
|---|
| 1482 | fixed so that the CPU time can be clearly estimated. <br> <br> |
|---|
| 1483 | <b>Note:</b> When using a fixed number of cycles, the user |
|---|
| 1484 | must |
|---|
| 1485 | examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a> |
|---|
| 1486 | regularly to check whether the divergence of the velocity field is |
|---|
| 1487 | sufficiently reduced by the pressure solver. It should be reduced at |
|---|
| 1488 | least by two orders of magnitude. For cyclic boundary conditions along |
|---|
| 1489 | both horizontal directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a> |
|---|
| 1490 | and <a href="chapter_4.1.html#bc_ns">bc_ns</a>) <span style="font-weight: bold;">mg_cycles</span> = <span style="font-style: italic;">2</span> is typically a |
|---|
| 1491 | good choice, for |
|---|
| 1492 | non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span> |
|---|
| 1493 | = <span style="font-style: italic;">4</span> may be |
|---|
| 1494 | sufficient.</td> </tr> <tr> <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br> |
|---|
| 1495 | level</b></td> <td style="vertical-align: top;">I</td> |
|---|
| 1496 | <td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;">Grid |
|---|
| 1497 | level at which data shall be gathered on PE0.<br> <br> |
|---|
| 1498 | In case of a run using several PEs and the multigrid method for solving |
|---|
| 1499 | the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>), |
|---|
| 1500 | the value of this parameter defines on which grid level the data are |
|---|
| 1501 | gathered on PE0 in order to allow for a further coarsening of the grid. |
|---|
| 1502 | The finest grid defines the largest grid level. By default, the |
|---|
| 1503 | gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. |
|---|
| 1504 | It is only possible to gather data from a level larger than the one |
|---|
| 1505 | determined automatically. A test run may be neccessary to determine |
|---|
| 1506 | this level.</td> </tr> <tr> <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</span><br> |
|---|
| 1507 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 1508 | <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td> |
|---|
| 1509 | <td style="vertical-align: top;">NetCDF files will have 64 |
|---|
| 1510 | bit offset format.<br><br>By |
|---|
| 1511 | default, the maximum file size of the NetCDF files opened by PALM is 2 |
|---|
| 1512 | GByte. Using netcdf_64bit = .TRUE. allows file sizes larger than 2 |
|---|
| 1513 | GByte.<br><br>The 64 bit offset format can be separately |
|---|
| 1514 | switched off for those NetCDF files containing 3d volume date (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>, |
|---|
| 1515 | <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>) |
|---|
| 1516 | using <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br><br><span style="font-weight: bold;">Warning:</span><br>Some |
|---|
| 1517 | (PD or commercial) software may not support the 64 bit offset format.<br> |
|---|
| 1518 | </td> </tr> |
|---|
| 1519 | <tr><td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;">.T.</td><td style="vertical-align: top;">NetCDF files containing 3d |
|---|
| 1520 | volume data will have 64 bit offset format.<br><br>This |
|---|
| 1521 | switch only comes into effect if <a href="#netcdf_64bit">netcdf_64bit</a> |
|---|
| 1522 | = .TRUE.. It allows to switch off separately the 64 bit offset format |
|---|
| 1523 | for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>, |
|---|
| 1524 | <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>).</td></tr><tr> |
|---|
| 1525 | <td style="vertical-align: top;"> <p><a name="ngsrb"></a><b>ngsrb</b></p> </td> |
|---|
| 1526 | <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>2</i></td> |
|---|
| 1527 | <td style="vertical-align: top;">Grid |
|---|
| 1528 | level at which data shall be gathered on PE0.<br> <br> |
|---|
| 1529 | In case of a run using several PEs and the multigrid method for solving |
|---|
| 1530 | the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>), |
|---|
| 1531 | the value of this parameter defines on which grid level the data are |
|---|
| 1532 | gathered on PE0 in order to allow for a further coarsening of the grid. |
|---|
| 1533 | The finest grid defines the largest grid level. By default, the |
|---|
| 1534 | gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. |
|---|
| 1535 | It is only possible to gather data from a level larger than the one |
|---|
| 1536 | determined automatically. A test run may be neccessary to determine |
|---|
| 1537 | this level.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="normalizing_region"></a><b>normalizing_region</b></p> |
|---|
| 1538 | </td> <td style="vertical-align: top;">I</td> |
|---|
| 1539 | <td style="vertical-align: top;"><span style="font-style: italic;">0</span><br> </td> |
|---|
| 1540 | <td style="vertical-align: top;"> <p>Determines the |
|---|
| 1541 | subdomain from which the normalization |
|---|
| 1542 | quantities are calculated. </p> <p>If output |
|---|
| 1543 | data of the horizontally averaged vertical profiles |
|---|
| 1544 | (see <a href="#data_output_pr">data_output_pr</a>) |
|---|
| 1545 | is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>, |
|---|
| 1546 | <a href="#cross_normalized_y">cross_normalized_y</a>), |
|---|
| 1547 | the respective normalization quantities are by default calculated from |
|---|
| 1548 | the averaged data of the total model domain (<b>normalizing_region</b> |
|---|
| 1549 | = <i>0</i>) and are thus representative for the total |
|---|
| 1550 | domain. Instead |
|---|
| 1551 | of that, normalization quantities can also be calculated for a |
|---|
| 1552 | subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>, |
|---|
| 1553 | where <i>1</i> |
|---|
| 1554 | <= <b>normalizing_region</b> <= <i>9 </i>must |
|---|
| 1555 | hold. These |
|---|
| 1556 | quantities are then used for normalizing of all profiles (even for that |
|---|
| 1557 | of the total domain).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nsor"></a><b>nsor</b></p> |
|---|
| 1558 | </td> <td style="vertical-align: top;">I</td> |
|---|
| 1559 | <td style="vertical-align: top;"><i>20</i></td> |
|---|
| 1560 | <td style="vertical-align: top;"> <p>Number of |
|---|
| 1561 | iterations to be used with the SOR-scheme. </p> <p>This |
|---|
| 1562 | parameter is only effective if the SOR-scheme is selected |
|---|
| 1563 | as pressure solver (<a href="#psolver">psolver</a> |
|---|
| 1564 | = <span style="font-style: italic;">'sor'</span>). |
|---|
| 1565 | The number of |
|---|
| 1566 | iterations necessary for a sufficient convergence of the scheme depends |
|---|
| 1567 | on the grid point numbers and is to be determined by appropriate test |
|---|
| 1568 | runs (the default value will not at all be sufficient for larger grid |
|---|
| 1569 | point numbers). The number of iterations used for the first call of the |
|---|
| 1570 | SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p> |
|---|
| 1571 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nz_do3d"></a><b>nz_do3d</b></p> |
|---|
| 1572 | </td> <td style="vertical-align: top;">I</td> |
|---|
| 1573 | <td style="vertical-align: top;"><i>nz+1</i></td> |
|---|
| 1574 | <td style="vertical-align: top;"> Limits the output of 3d |
|---|
| 1575 | volume data along the vertical direction (grid point index k).<br><br>By |
|---|
| 1576 | default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span> |
|---|
| 1577 | can be used to limit the output up to a certain vertical grid point |
|---|
| 1578 | (e.g. in order to reduce the amount of output data). It affects all |
|---|
| 1579 | output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output |
|---|
| 1580 | for <span style="font-weight: bold;">dvrp</span>-software, |
|---|
| 1581 | see <a href="#mode_dvrp">mode_dvrp</a>).</td> |
|---|
| 1582 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 1583 | <p><a name="omega_sor"></a><b>omega_sor</b></p> |
|---|
| 1584 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1585 | <td style="vertical-align: top;"><i>1.8</i></td> |
|---|
| 1586 | <td style="vertical-align: top;"> <p>Convergence |
|---|
| 1587 | factor to be used with the the SOR-scheme. </p> <p>If |
|---|
| 1588 | the SOR-scheme is selected (<a href="#psolver">psolver</a> |
|---|
| 1589 | = <span style="font-style: italic;">'sor'</span>), |
|---|
| 1590 | this parameter |
|---|
| 1591 | determines the value of the convergence factor, where <i>1.0</i> |
|---|
| 1592 | <= <b>omega_sor</b> < <i>2.0 </i>. |
|---|
| 1593 | The optimum value of <b>omega_sor</b> |
|---|
| 1594 | depends on the number of grid points along the different directions in |
|---|
| 1595 | space. For non-equidistant grids it can only be determined by |
|---|
| 1596 | appropriate test runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="prandtl_number"></a><b>prandtl_number</b></p> |
|---|
| 1597 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1598 | <td style="vertical-align: top;"><i>1.0</i></td> |
|---|
| 1599 | <td style="vertical-align: top;"> <p>Ratio of the |
|---|
| 1600 | eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>). |
|---|
| 1601 | </p> <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>), |
|---|
| 1602 | this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub> |
|---|
| 1603 | / K<sub>h</sub>).</p> </td> </tr> <tr> |
|---|
| 1604 | <td style="vertical-align: top;"> <p><a name="profile_columns"></a><b>profile_columns</b></p> |
|---|
| 1605 | </td> <td style="vertical-align: top;">I</td> |
|---|
| 1606 | <td style="vertical-align: top;"><i>3</i></td> |
|---|
| 1607 | <td style="vertical-align: top;"> <p>Number of |
|---|
| 1608 | coordinate systems to be plotted<span style="font-weight: bold;"></span> |
|---|
| 1609 | in one row by <span style="font-weight: bold;">profil</span>. |
|---|
| 1610 | </p> <p>This parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 1611 | = <span style="font-style: italic;">'profil'</span>.</p><p>It |
|---|
| 1612 | determines the layout of plots of |
|---|
| 1613 | horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>) |
|---|
| 1614 | when plotted with the plot software <span style="font-weight: bold;">profil</span>. |
|---|
| 1615 | Generally, the number and sequence of coordinate systems (panels) to be |
|---|
| 1616 | plotted on one page are |
|---|
| 1617 | determined by <a href="#cross_profiles">cross_profiles</a>. |
|---|
| 1618 | <b>profile_columns</b> |
|---|
| 1619 | determines how many panels are to be |
|---|
| 1620 | arranged next to each other in one row (number of columns). The |
|---|
| 1621 | respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>. |
|---|
| 1622 | According to their order given by <a href="#data_output_pr">data_output_pr</a>, |
|---|
| 1623 | the panels are arranged beginning in the top row from left to right and |
|---|
| 1624 | then continued in the following row. If the number of panels cranz |
|---|
| 1625 | > <b>profile_columns</b> * <b>profile_rows</b>, |
|---|
| 1626 | the remaining |
|---|
| 1627 | panels are drawn on an additional page. If cranz < <b>profile_columns</b>, |
|---|
| 1628 | then <b>profile_columns</b> = cranz is automatically set. |
|---|
| 1629 | If |
|---|
| 1630 | row contains any panel, then the value of <b>profile_rows</b> |
|---|
| 1631 | is reduced automatically.</p> </td> </tr> <tr> |
|---|
| 1632 | <td style="vertical-align: top;"> <p><a name="profile_rows"></a><b>profile_rows</b></p> |
|---|
| 1633 | </td> <td style="vertical-align: top;">I</td> |
|---|
| 1634 | <td style="vertical-align: top;"><i>2</i></td> |
|---|
| 1635 | <td style="vertical-align: top;"> <p>Number of rows |
|---|
| 1636 | of coordinate systems to be plotted on one page |
|---|
| 1637 | by <span style="font-weight: bold;">profil</span>. |
|---|
| 1638 | </p> <p>This parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 1639 | = <span style="font-style: italic;">'profil'</span>.</p><p>It |
|---|
| 1640 | determines the layout of plots of horizontally averaged |
|---|
| 1641 | profiles. See <a href="#profile_columns">profile_columns</a>.</p> |
|---|
| 1642 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psolver"></a><b>psolver</b></p> |
|---|
| 1643 | </td> <td style="vertical-align: top;">C * 10</td> |
|---|
| 1644 | <td style="vertical-align: top;"><i>'poisfft'</i></td> |
|---|
| 1645 | <td style="vertical-align: top;"> <p>Scheme to be |
|---|
| 1646 | used to solve the Poisson equation for the |
|---|
| 1647 | perturbation pressure. </p> <br> |
|---|
| 1648 | The user can choose between the following schemes:<br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>poisfft</i></td> |
|---|
| 1649 | <td style="vertical-align: top;">Direct method using FFT |
|---|
| 1650 | along x and y, solution of a |
|---|
| 1651 | tridiagonal matrix along z, and backward |
|---|
| 1652 | FFT (see Siano, institute reports, volume 54). The FFT routines to be |
|---|
| 1653 | used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br> |
|---|
| 1654 | This solver is specially optimized for 1d domain decompositions. |
|---|
| 1655 | Vectorization is optimized for domain decompositions along x only.</td> |
|---|
| 1656 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 1657 | <p><i>poisfft_</i> <br> <i>hybrid</i></p> |
|---|
| 1658 | </td> <td style="vertical-align: top;">Direct |
|---|
| 1659 | method using FFT |
|---|
| 1660 | along x and y, solution of a |
|---|
| 1661 | tridiagonal matrix along z, and backward |
|---|
| 1662 | FFT (see Siano, institute reports, volume 54). The FFT routines to be |
|---|
| 1663 | used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br> |
|---|
| 1664 | This solver is specially optimized for 1d domain decompositions. |
|---|
| 1665 | Vectorization is optimized for domain decompositions along x only.</td> |
|---|
| 1666 | </tr> <tr> <td style="vertical-align: top;"><i>multigrid</i></td> |
|---|
| 1667 | <td style="vertical-align: top;"> <p>Multi-grid |
|---|
| 1668 | scheme (see Uhlenbrock, diploma thesis). v- |
|---|
| 1669 | and |
|---|
| 1670 | w-cycles (see <a href="#cycle_mg">cycle_mg</a>) |
|---|
| 1671 | are implemented. The convergence of the iterative scheme can be |
|---|
| 1672 | steered by the number of v-/w-cycles to be carried out for each call of |
|---|
| 1673 | the scheme (<a href="#mg_cycles">mg_cycles</a>) |
|---|
| 1674 | and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>) |
|---|
| 1675 | to be carried out on each grid level. Instead the requested accuracy |
|---|
| 1676 | can be given via <a href="#residual_limit">residual_limit</a>. |
|---|
| 1677 | <span style="font-weight: bold;">This is the default!</span> |
|---|
| 1678 | The |
|---|
| 1679 | smaller this limit is, the more cycles have to be carried out in this |
|---|
| 1680 | case and the number of cycles may vary from timestep to timestep.</p> |
|---|
| 1681 | <br> |
|---|
| 1682 | If <a href="#mg_cycles">mg_cycles</a> |
|---|
| 1683 | is set to its optimal value, the computing time of the |
|---|
| 1684 | multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as |
|---|
| 1685 | the number of |
|---|
| 1686 | grid points in the three directions |
|---|
| 1687 | of space corresponds to a power-of-two (2<sup>n</sup>) |
|---|
| 1688 | where <i>n</i> >= 5 must hold. With large <i>n, |
|---|
| 1689 | </i>the |
|---|
| 1690 | multi-grid scheme can even be faster than the direct solver (although |
|---|
| 1691 | its accuracy is several orders of magnitude worse, but this does not |
|---|
| 1692 | affect the accuracy of the simulation). Nevertheless, the user should |
|---|
| 1693 | always carry out some test runs in order to find out the optimum value |
|---|
| 1694 | for <a href="#mg_cycles">mg_cycles</a>, |
|---|
| 1695 | because the CPU time of a run very critically depends on this |
|---|
| 1696 | parameter. <p>This scheme requires that the number of grid |
|---|
| 1697 | points of |
|---|
| 1698 | the |
|---|
| 1699 | subdomains (or of the total domain, if only one PE is uesd) along each |
|---|
| 1700 | of the directions can at least be devided once by 2 without rest.</p> |
|---|
| 1701 | With parallel runs, starting from a certain grid level the |
|---|
| 1702 | data of the subdomains are possibly gathered on PE0 in order to allow |
|---|
| 1703 | for a further coarsening of the grid. The grid level for gathering can |
|---|
| 1704 | be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br> |
|---|
| 1705 | <p>Using this procedure requires the subdomains to be of |
|---|
| 1706 | identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p> |
|---|
| 1707 | </td> </tr> <tr> <td style="vertical-align: top;"><i>sor</i></td> |
|---|
| 1708 | <td style="vertical-align: top;">Successive over |
|---|
| 1709 | relaxation |
|---|
| 1710 | method (SOR). The convergence of |
|---|
| 1711 | this |
|---|
| 1712 | iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>, |
|---|
| 1713 | <a href="chapter_4.1.html#nsor_ini">nsor_ini</a> |
|---|
| 1714 | and <a href="chapter_4.1.html#nsor">nsor</a>. |
|---|
| 1715 | <br>Compared to the direct method and the multi-grid method, this |
|---|
| 1716 | scheme |
|---|
| 1717 | needs substantially |
|---|
| 1718 | more computing time. It should only be used for test runs, e.g. if |
|---|
| 1719 | errors in the other pressure solver methods are assumed.</td> </tr> |
|---|
| 1720 | </tbody> </table> <br> |
|---|
| 1721 | In order to speed-up performance, the Poisson equation is by default |
|---|
| 1722 | only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver |
|---|
| 1723 | at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>). |
|---|
| 1724 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b> |
|---|
| 1725 | <br> <b>_factor</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.0 or</i><br> |
|---|
| 1726 | <i>0.01</i></td> <td style="vertical-align: top;"> |
|---|
| 1727 | <p>Factor for Rayleigh damping. </p> <p>A |
|---|
| 1728 | so-called Rayleigh damping is applied to all prognostic |
|---|
| 1729 | variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>. |
|---|
| 1730 | If switched on, variables are forced towards the value of their |
|---|
| 1731 | respective basic states (e.g. the geostrophic wind). The intensity of |
|---|
| 1732 | damping is controlled by the value the <b>rayleigh_damping_factor</b> |
|---|
| 1733 | is assigned to. |
|---|
| 1734 | The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a> |
|---|
| 1735 | and rises according to a sin<sup>2</sup>-function to its |
|---|
| 1736 | maximum value |
|---|
| 1737 | at |
|---|
| 1738 | the top boundary. </p> <p>This method |
|---|
| 1739 | effectively damps gravity waves, caused by boundary layer convection, |
|---|
| 1740 | which may spread out vertically in the inversion layer and which are |
|---|
| 1741 | reflected at the top |
|---|
| 1742 | boundary. This particularly happens with the upstream-spline scheme |
|---|
| 1743 | switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a> |
|---|
| 1744 | or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>). |
|---|
| 1745 | Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b> |
|---|
| 1746 | = <i>0.01</i>) by default. Otherwise it remains switched |
|---|
| 1747 | off. </p> <p>The Rayleigh damping factor must |
|---|
| 1748 | hold the condition <i>0.0</i> |
|---|
| 1749 | <= <b>rayleigh_damping_factor</b> |
|---|
| 1750 | <= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause |
|---|
| 1751 | numerical instabilities.</p> </td> </tr> <tr> |
|---|
| 1752 | <td style="vertical-align: top;"> <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b> |
|---|
| 1753 | <br> <b>_height</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"> <p><i>2/3 *</i> |
|---|
| 1754 | <br><span style="font-style: italic;"> |
|---|
| 1755 | zu</span><i style="font-style: italic;">(nz)</i></p> |
|---|
| 1756 | </td> <td style="vertical-align: top;"> <p>Height |
|---|
| 1757 | where the Rayleigh damping starts (in m). </p> <p>With |
|---|
| 1758 | Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>), |
|---|
| 1759 | this parameter determines the range where damping is applied. By |
|---|
| 1760 | default, Rayleigh damping will be applied in the upper third of the |
|---|
| 1761 | model |
|---|
| 1762 | domain.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="residual_limit"></a><b>residual_limit</b></p> |
|---|
| 1763 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1764 | <td style="vertical-align: top;"><i>1.0E-6</i></td> |
|---|
| 1765 | <td style="vertical-align: top;"> <p>Largest |
|---|
| 1766 | residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>). |
|---|
| 1767 | </p> <p>This is a parameter to steer the accuracy of the |
|---|
| 1768 | multi-grid |
|---|
| 1769 | scheme (see <a href="#psolver">psolver</a>). |
|---|
| 1770 | The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>) |
|---|
| 1771 | is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If |
|---|
| 1772 | this |
|---|
| 1773 | is not the case after 1000 cycles, the PALM aborts with a corresponding |
|---|
| 1774 | error message.</p> <p>The reciprocal value of this |
|---|
| 1775 | parameter can be interpreted as |
|---|
| 1776 | a factor by the divergence of the provisional |
|---|
| 1777 | velocity field is approximately reduced after the multi-grid scheme has |
|---|
| 1778 | been applied (thus the default value causes a reduction of the |
|---|
| 1779 | divergence by approx. 6 orders of magnitude). </p> </td> |
|---|
| 1780 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 1781 | <p><a name="restart_time"></a><b>restart_time</b></p> |
|---|
| 1782 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 1783 | <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 1784 | <td style="vertical-align: top;"> <p>Simulated time |
|---|
| 1785 | after which a restart run is to be carried out |
|---|
| 1786 | (in s). </p> <p>The simulated time refers to the |
|---|
| 1787 | beginning of the |
|---|
| 1788 | initial run (t = 0), not to the beginning of the respective |
|---|
| 1789 | restart run. Restart runs can additionally be forced to be carried out |
|---|
| 1790 | in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p> <p><span style="font-weight: bold;">Note:</span><br> |
|---|
| 1791 | A successful operation of this parameter requires additional |
|---|
| 1792 | modifications in the <span style="font-weight: bold;">mrun</span>-call |
|---|
| 1793 | for the respective run (see <a href="chapter_3.3.html">chapter |
|---|
| 1794 | 3.3</a>).<br> </p> <p>The choice of <b>restart_time</b> |
|---|
| 1795 | or <b>dt_restart</b> does |
|---|
| 1796 | not override the automatic start of restart runs in case that the job |
|---|
| 1797 | runs out of CPU time. <br> </p> </td> </tr> |
|---|
| 1798 | <tr> <td style="vertical-align: top;"> <p><a name="section_xy"></a><b>section_xy</b></p> |
|---|
| 1799 | </td> <td style="vertical-align: top;">I(100)<br> |
|---|
| 1800 | </td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br> |
|---|
| 1801 | </td> <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position |
|---|
| 1802 | of cross section(s) for output of 2d horizontal cross |
|---|
| 1803 | sections (grid point index k). </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output |
|---|
| 1804 | of |
|---|
| 1805 | horizontal cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this |
|---|
| 1806 | parameter can be used to |
|---|
| 1807 | define the position(s) of the cross section(s). Up to 100 positions of |
|---|
| 1808 | cross sections can be selected by assigning <b>section_xy</b> |
|---|
| 1809 | the |
|---|
| 1810 | corresponding vertical grid point index/indices k of the requested |
|---|
| 1811 | cross section(s). The exact location (height level) of the cross |
|---|
| 1812 | section depends on the variable for which the output is made: zu(k) for |
|---|
| 1813 | scalars and horizontal velocities, zw(k) for the vertical velocity. |
|---|
| 1814 | Information about the exact location of the cross section is contained |
|---|
| 1815 | in the NetCDF output file (if the default NetCDF output is switched on; |
|---|
| 1816 | see <a href="#data_output_format">data_output_format</a>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span> |
|---|
| 1817 | creates the output of horizontal cross sections averaged along z. In |
|---|
| 1818 | the |
|---|
| 1819 | NetCDF output file these (averaged) cross sections are given the |
|---|
| 1820 | z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b> |
|---|
| 1821 | does not effect the output of horizontal cross sections of variable u<sub>*</sub> |
|---|
| 1822 | and theta<sub>*</sub> and the liquid water path lwp*. For |
|---|
| 1823 | these quantities always only one cross |
|---|
| 1824 | section (for z=zu(1)) is output.</font></span></p><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> = |
|---|
| 1825 | <span style="font-style: italic;">'iso2d'</span> and |
|---|
| 1826 | if several cross sections are selected (e.g. <b>section_xy</b> |
|---|
| 1827 | = <i>1</i>, <i>10</i>, <i>15</i>), |
|---|
| 1828 | then the respective data are |
|---|
| 1829 | successively written to file. The output order follows the order given |
|---|
| 1830 | by <b>section_xy</b>. </font></span></td> |
|---|
| 1831 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 1832 | <p><a name="section_xz"></a><b>section_xz</b></p> |
|---|
| 1833 | </td> <td style="vertical-align: top;">I(100)<br> |
|---|
| 1834 | </td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td> |
|---|
| 1835 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of cross section(s) |
|---|
| 1836 | for output of 2d (xz) vertical cross sections (grid point |
|---|
| 1837 | index j). </font> </p> <span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 1838 | vertical xz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this |
|---|
| 1839 | parameter can be used to |
|---|
| 1840 | define the position(s) of the cross section(s). Up to 100 positions of |
|---|
| 1841 | cross sections can be selected by assigning <b>section_xz</b> |
|---|
| 1842 | the |
|---|
| 1843 | corresponding horizontal grid point index/indices j of the requested |
|---|
| 1844 | cross section(s). The exact position (in y-direction) of the cross |
|---|
| 1845 | section is given by j*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a> <span lang="en-GB"><font face="Thorndale">or (j-0.5)*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a><span lang="en-GB"><font face="Thorndale">, depending |
|---|
| 1846 | on which grid the output quantity is defined. However, in |
|---|
| 1847 | the NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the |
|---|
| 1848 | default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>) |
|---|
| 1849 | no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all |
|---|
| 1850 | positions.<br><br>Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span> |
|---|
| 1851 | creates the output of vertical cross sections averaged along y. In the |
|---|
| 1852 | NetCDF output file these (averaged) cross sections are given the |
|---|
| 1853 | y-coordinate <span style="font-style: italic;">-1.0</span>.<br></font></span><span lang="en-GB"><font face="Thorndale"><br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> = |
|---|
| 1854 | <span style="font-style: italic;">'iso2d'</span> and |
|---|
| 1855 | </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are |
|---|
| 1856 | selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>, |
|---|
| 1857 | <i>27</i>), |
|---|
| 1858 | then the respective data are successively written to file. The output |
|---|
| 1859 | order follows the order given by <b>section_xz</b>.</font></span></td> |
|---|
| 1860 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 1861 | <p><a name="section_yz"></a><b>section_yz</b></p> |
|---|
| 1862 | </td> <td style="vertical-align: top;">I(100)<br> |
|---|
| 1863 | </td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td> |
|---|
| 1864 | <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of cross section(s) |
|---|
| 1865 | for output of 2d (yz) vertical cross sections (grid point |
|---|
| 1866 | index i). </font> </p> <span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 1867 | vertical yz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), |
|---|
| 1868 | this parameter can be used to define the position(s) of the cross |
|---|
| 1869 | section(s). Up to 100 positions of cross sections can be selected by |
|---|
| 1870 | assigning <b>section_yz</b> the corresponding horizontal |
|---|
| 1871 | grid point |
|---|
| 1872 | index/indices i of the requested cross section(s). The exact position |
|---|
| 1873 | (in x-direction) of the cross section is given by i*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a> <span lang="en-GB"><font face="Thorndale">or (i-0.5)*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a><span lang="en-GB"><font face="Thorndale">, depending |
|---|
| 1874 | on which grid the output quantity is defined. </font></span><span lang="en-GB"><font face="Thorndale">However, in |
|---|
| 1875 | the NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the |
|---|
| 1876 | default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>) |
|---|
| 1877 | no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all |
|---|
| 1878 | positions.<br><br></font></span><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_yz</span> = <span style="font-style: italic;">-1</span> |
|---|
| 1879 | creates the output of vertical cross sections averaged along x. In the |
|---|
| 1880 | NetCDF output file these (averaged) cross sections are given the |
|---|
| 1881 | x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> = |
|---|
| 1882 | <span style="font-style: italic;">'iso2d'</span> and |
|---|
| 1883 | </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are |
|---|
| 1884 | selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the |
|---|
| 1885 | respective data are successively written to file. The output order |
|---|
| 1886 | follows the order given by <b>section_yz</b>.</font></span></td> |
|---|
| 1887 | </tr> <tr> <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br> |
|---|
| 1888 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1889 | <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td> |
|---|
| 1890 | <td style="vertical-align: top;">No data output before |
|---|
| 1891 | this interval has passed (in s).<br><br>This |
|---|
| 1892 | parameter causes that data output activities are starting not before |
|---|
| 1893 | this interval |
|---|
| 1894 | (counting from the beginning of the simulation, t=0) has passed. By |
|---|
| 1895 | default, this |
|---|
| 1896 | applies for output of instantaneous 3d volume data, cross section data, |
|---|
| 1897 | spectra and vertical profile data as well as for temporally averaged 2d |
|---|
| 1898 | and 3d data. Individual intervals can be assigned using parameters <a href="#skip_time_do3d">skip_time_do3d</a>, <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, <a href="#skip_time_dosp">skip_time_dosp</a>, <a href="#skip_time_dopr">skip_time_dopr</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1899 | the user has set <a href="#dt_data_output">dt_data_output</a> |
|---|
| 1900 | = <span style="font-style: italic;">3600.0</span> |
|---|
| 1901 | and <span style="font-weight: bold;">skip_time_data_output</span> |
|---|
| 1902 | = <span style="font-style: italic;">1800.0</span>, |
|---|
| 1903 | then the first output will be done at t = 5400 s.<br> </td> |
|---|
| 1904 | </tr> <tr><td style="vertical-align: top;"><a name="skip_time_data_output_av"></a><span style="font-weight: bold;">skip_time_data_output_av</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>data_output</a></span></td><td style="vertical-align: top;">No output of temporally |
|---|
| 1905 | averaged 2d/3d data before this interval has passed (in s).<br><br>This |
|---|
| 1906 | parameter causes that data output activities are starting not before |
|---|
| 1907 | this interval |
|---|
| 1908 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1909 | the user has set <a href="#dt_data_output_av">dt_data_output_av</a> |
|---|
| 1910 | = <span style="font-style: italic;">3600.0</span> |
|---|
| 1911 | and <span style="font-weight: bold;">skip_time_data_output_av</span> |
|---|
| 1912 | = <span style="font-style: italic;">1800.0</span>, |
|---|
| 1913 | then the first output will be done at t = 5400 s.</td></tr><tr> |
|---|
| 1914 | <td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br> |
|---|
| 1915 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1916 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span> |
|---|
| 1917 | </td> <td style="vertical-align: top;">No output of |
|---|
| 1918 | vertical profile data before this interval has passed (in s).<br><br>This |
|---|
| 1919 | parameter causes that data output activities are starting not before |
|---|
| 1920 | this interval |
|---|
| 1921 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1922 | the user has set <a href="#dt_dopr">dt_dopr</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dopr</span> = <span style="font-style: italic;">1800.0</span>, then the |
|---|
| 1923 | first output will be done at t = 5400 s. </td> </tr> <tr> |
|---|
| 1924 | <td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br> |
|---|
| 1925 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1926 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span> |
|---|
| 1927 | </td> <td style="vertical-align: top;">No output of |
|---|
| 1928 | instantaneous horizontal cross section data before this interval has |
|---|
| 1929 | passed (in s).<br><br>This |
|---|
| 1930 | parameter causes that data output activities are starting not before |
|---|
| 1931 | this interval |
|---|
| 1932 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1933 | the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a> |
|---|
| 1934 | = <span style="font-style: italic;">3600.0</span> |
|---|
| 1935 | and <span style="font-weight: bold;">skip_time_do2d_xy</span> |
|---|
| 1936 | = <span style="font-style: italic;">1800.0</span>, |
|---|
| 1937 | then the first output will be done at t = 5400 s. </td> </tr> |
|---|
| 1938 | <tr> <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br> |
|---|
| 1939 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1940 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span> |
|---|
| 1941 | </td> <td style="vertical-align: top;">No output of |
|---|
| 1942 | instantaneous vertical (xz) cross section data before this interval has |
|---|
| 1943 | passed (in s).<br><br>This |
|---|
| 1944 | parameter causes that data output activities are starting not before |
|---|
| 1945 | this interval |
|---|
| 1946 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1947 | the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a> |
|---|
| 1948 | = <span style="font-style: italic;">3600.0</span> |
|---|
| 1949 | and <span style="font-weight: bold;">skip_time_do2d_xz</span> |
|---|
| 1950 | = <span style="font-style: italic;">1800.0</span>, |
|---|
| 1951 | then the first output will be done at t = 5400 s. </td> </tr> |
|---|
| 1952 | <tr> <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br> |
|---|
| 1953 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1954 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span> |
|---|
| 1955 | </td> <td style="vertical-align: top;">No output of |
|---|
| 1956 | instantaneous vertical (yz) cross section data before this interval has |
|---|
| 1957 | passed (in s).<br><br>This |
|---|
| 1958 | parameter causes that data output activities are starting not before |
|---|
| 1959 | this interval |
|---|
| 1960 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1961 | the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a> |
|---|
| 1962 | = <span style="font-style: italic;">3600.0</span> |
|---|
| 1963 | and <span style="font-weight: bold;">skip_time_do2d_yz</span> |
|---|
| 1964 | = <span style="font-style: italic;">1800.0</span>, |
|---|
| 1965 | then the first output will be done at t = 5400 s. </td> </tr> |
|---|
| 1966 | <tr> <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br> |
|---|
| 1967 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 1968 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span> |
|---|
| 1969 | </td> <td style="vertical-align: top;">No output of |
|---|
| 1970 | instantaneous 3d volume data before this interval has passed (in s).<br><br>This |
|---|
| 1971 | parameter causes that data output activities are starting not before |
|---|
| 1972 | this interval |
|---|
| 1973 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 1974 | the user has set <a href="#dt_do3d">dt_do3d</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_do3d</span> = <span style="font-style: italic;">1800.0</span>, then the |
|---|
| 1975 | first output will be done at t = 5400 s. </td> </tr> |
|---|
| 1976 | <tr> <td style="vertical-align: top;"> <p><a name="termination_time_needed"></a><b>termination_time</b> |
|---|
| 1977 | <br> <b>_needed</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br> </td> |
|---|
| 1978 | <td style="vertical-align: top;"> <p>CPU time |
|---|
| 1979 | needed for terminal actions at the end of a run in |
|---|
| 1980 | batch mode (in s).<br> </p> <p>If the environment |
|---|
| 1981 | variable <b>write_binary </b>is |
|---|
| 1982 | set <i>true</i> (see <a href="chapter_3.3.html">chapter |
|---|
| 1983 | 3.3</a>), PALM checks the remaining CPU time of the job after |
|---|
| 1984 | each |
|---|
| 1985 | timestep. Time integration must not consume the CPU time completely, |
|---|
| 1986 | since several actions still have to be carried out after time |
|---|
| 1987 | integration has finished (e.g. writing of binary data for the restart |
|---|
| 1988 | run, carrying out output commands, copying of local files to their |
|---|
| 1989 | permanent destinations, etc.) which also takes some time. The maximum |
|---|
| 1990 | possible time needed for these activities plus a reserve is to be given |
|---|
| 1991 | with the parameter <b>termination_time_needed</b>. Among |
|---|
| 1992 | other things, |
|---|
| 1993 | it depends on |
|---|
| 1994 | the number of grid points used. If its value is selected too small, |
|---|
| 1995 | then the |
|---|
| 1996 | respective job will be prematurely aborted by the queuing system, which |
|---|
| 1997 | may result in a data loss and will possibly interrupt the job chain.<br> |
|---|
| 1998 | </p> <p>An abort happens in any way, if the environment |
|---|
| 1999 | variable <span style="font-weight: bold;">write_binary</span> |
|---|
| 2000 | is not set to <span style="font-style: italic;">true</span> |
|---|
| 2001 | and if moreover the job has |
|---|
| 2002 | been assigned an insufficient CPU time by <b>mrun</b> |
|---|
| 2003 | option <tt><tt>-t</tt></tt>. <i><br> |
|---|
| 2004 | </i> </p> <p><span style="font-weight: bold;">Note:</span><br> |
|---|
| 2005 | On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of |
|---|
| 2006 | PALM |
|---|
| 2007 | have also to be accounted for (e.g. for |
|---|
| 2008 | compilation and copying of input files).</p> </td> </tr> |
|---|
| 2009 | <tr> <td style="vertical-align: top;"> <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b> |
|---|
| 2010 | <br> <b>_parameters</b></p> </td> <td style="vertical-align: top;">L</td> <td style="vertical-align: top;"><i>.F.</i></td> |
|---|
| 2011 | <td style="vertical-align: top;"> <p>Additional |
|---|
| 2012 | plot of vertical profile data with <span style="font-weight: bold;">profil</span> |
|---|
| 2013 | from preceding runs of the |
|---|
| 2014 | job chain. </p> <p>This parameter only applies |
|---|
| 2015 | for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 2016 | = <span style="font-style: italic;">'profil'</span>.</p><p>By |
|---|
| 2017 | default, plots of horizontally averaged vertical profiles |
|---|
| 2018 | (see <a href="#data_output_pr">data_output_pr</a>) |
|---|
| 2019 | only contain profiles of data produced by the model |
|---|
| 2020 | run. If profiles of prior times (i.e. data of preceding jobs of a |
|---|
| 2021 | job chain) shall be plotted additionally (e.g. for comparison |
|---|
| 2022 | purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>. |
|---|
| 2023 | must be |
|---|
| 2024 | set.<br> </p> <p>For further explanation see <a href="chapter_4.5.2.html">chapter |
|---|
| 2025 | 4.5.2</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p> |
|---|
| 2026 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 2027 | <td style="vertical-align: top;"><i>zu(nzt+1) (model |
|---|
| 2028 | top)</i></td> <td style="vertical-align: top;"> |
|---|
| 2029 | <p>Height level up to which horizontally averaged profiles are to |
|---|
| 2030 | be |
|---|
| 2031 | plotted with <span style="font-weight: bold;">profil</span> |
|---|
| 2032 | (in |
|---|
| 2033 | m). </p> <p>This parameter only applies for |
|---|
| 2034 | <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 2035 | = <span style="font-style: italic;">'profil'</span>.</p><p>It |
|---|
| 2036 | affects plots of horizontally averaged profiles |
|---|
| 2037 | (<a href="#data_output_pr">data_output_pr</a>) |
|---|
| 2038 | when plotted with the plot software <span style="font-weight: bold;">profil</span>. |
|---|
| 2039 | By default, profiles are plotted up to the top boundary. The height |
|---|
| 2040 | level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller |
|---|
| 2041 | value. |
|---|
| 2042 | Nevertheless, <span style="font-weight: bold;">all</span> |
|---|
| 2043 | vertical |
|---|
| 2044 | grid points (0 <= k <= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p> |
|---|
| 2045 | <p>If a normalization for the vertical axis was selected (see <a href="#cross_normalized_y">cross_normalized_y</a>), <b>z_max_do1d</b> |
|---|
| 2046 | has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a> |
|---|
| 2047 | must be used.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b> |
|---|
| 2048 | <br> <b>_normalized</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>determined by plot</i> |
|---|
| 2049 | <br> <i>data</i> <br> </td> <td style="vertical-align: top;"> <p>Normalized height |
|---|
| 2050 | level up to which horizontally averaged |
|---|
| 2051 | profiles are to be plotted with <span style="font-weight: bold;">profil</span>. |
|---|
| 2052 | </p> <p>This parameter only applies for <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 2053 | = <span style="font-style: italic;">'profil'</span>.</p><p>It |
|---|
| 2054 | affects plots of horizontally averaged profiles |
|---|
| 2055 | (<a href="#data_output_pr">data_output_pr</a>) |
|---|
| 2056 | when plotted with the plot software <span style="font-weight: bold;">profil</span>, |
|---|
| 2057 | if a normalization for the vertical axis is selected |
|---|
| 2058 | (see <a href="#cross_normalized_y">cross_normalized_y</a>). |
|---|
| 2059 | If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b> |
|---|
| 2060 | = <i>1.5</i> means that all profiles up to the height |
|---|
| 2061 | level of z = |
|---|
| 2062 | 1.5* z<sub>i </sub>are plotted.</p> </td> </tr> |
|---|
| 2063 | <tr> <td style="vertical-align: top;"> <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p> |
|---|
| 2064 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 2065 | <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br> </td> |
|---|
| 2066 | <td style="vertical-align: top;"> <p>Height level |
|---|
| 2067 | up to which 2d cross sections are to be plotted |
|---|
| 2068 | with <span style="font-weight: bold;">iso2d</span> |
|---|
| 2069 | (in m). </p> <p>This parameter only applies for |
|---|
| 2070 | <a href="#data_output_format">data_output_format</a> |
|---|
| 2071 | = <span style="font-style: italic;">'iso2d'</span>.</p><p>It |
|---|
| 2072 | affects plots of 2d vertical cross |
|---|
| 2073 | sections (<a href="#data_output">data_output</a>) |
|---|
| 2074 | when plotted with <span style="font-weight: bold;">iso2d</span>. |
|---|
| 2075 | By |
|---|
| 2076 | default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d |
|---|
| 2077 | </b>the |
|---|
| 2078 | visualization within |
|---|
| 2079 | the plot can be limited to a certain height level (0 <= z |
|---|
| 2080 | <= <b>z_max_do2d</b>). |
|---|
| 2081 | Nevertheless, <span style="font-weight: bold;">all</span> |
|---|
| 2082 | grid points |
|---|
| 2083 | of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a> |
|---|
| 2084 | or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>. |
|---|
| 2085 | The level up to which the section is visualized can later be changed by |
|---|
| 2086 | manually editing the |
|---|
| 2087 | file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a> |
|---|
| 2088 | or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a> |
|---|
| 2089 | (the respective <span style="font-weight: bold;">iso2d</span>-parameter |
|---|
| 2090 | is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p> |
|---|
| 2091 | </td> </tr> </tbody> |
|---|
| 2092 | </table><br> |
|---|
| 2093 | <br><h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package |
|---|
| 2094 | parameters: </h3> |
|---|
| 2095 | Package (<span style="font-weight: bold;">mrun</span> |
|---|
| 2096 | option -p): <span style="font-weight: bold;"><a name="particles_package"></a>particles</span> |
|---|
| 2097 | NAMELIST group name: <span style="font-weight: bold;">particles_par<br> |
|---|
| 2098 | </span><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> |
|---|
| 2099 | <tr> <td style="vertical-align: top;"><font size="4"><b>Parameter name</b></font></td> |
|---|
| 2100 | <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td> |
|---|
| 2101 | <td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td> |
|---|
| 2102 | <td style="vertical-align: top;"> <p><font size="4"><b>Explanation</b></font></p> |
|---|
| 2103 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_prel"></a><b>dt_prel</b></p> |
|---|
| 2104 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 2105 | <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 2106 | <td style="vertical-align: top;"> <p><font face="Thorndale, serif"><span lang="en-GB">Temporal |
|---|
| 2107 | interval at |
|---|
| 2108 | which particles are to be released <span lang="en-GB">from |
|---|
| 2109 | a particle |
|---|
| 2110 | source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span> |
|---|
| 2111 | </font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">By default |
|---|
| 2112 | particles are released only at the beginning of a simulation |
|---|
| 2113 | (t_init=0). The time of the first release (t_init) can be changed with |
|---|
| 2114 | package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>. |
|---|
| 2115 | </font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be |
|---|
| 2116 | set with the package parameter <a href="#end_time_prel">end_time_prel</a>. |
|---|
| 2117 | If <span style="font-weight: bold;">dt_prel</span> |
|---|
| 2118 | has been set, additional |
|---|
| 2119 | releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>, |
|---|
| 2120 | t_init+2*<span style="font-weight: bold;">dt_prel</span>, |
|---|
| 2121 | t_init+3*<span style="font-weight: bold;">dt_prel</span>, |
|---|
| 2122 | etc.. Actual release times |
|---|
| 2123 | may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see |
|---|
| 2124 | e.g. </font></span><a href="#dt_dopr"><span lang="en-GB"><font face="Thorndale, serif">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">).</font></span></p> |
|---|
| 2125 | <p><span lang="en-GB"><font face="Thorndale, serif"> The domain |
|---|
| 2126 | of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as |
|---|
| 2127 | well as the distance of released particles |
|---|
| 2128 | within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package |
|---|
| 2129 | parameters </font></span><a href="#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a> |
|---|
| 2130 | <span lang="en-GB"><font face="Thorndale, serif">and |
|---|
| 2131 | </font></span><a href="#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"><font face="Thorndale, serif"> By |
|---|
| 2132 | default, one particle is released at all points defined by these |
|---|
| 2133 | parameters. The package parameter <a href="#particles_per_point">particles_per_point</a> |
|---|
| 2134 | can be used to start more than one particle per point.<br> |
|---|
| 2135 | </font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10 |
|---|
| 2136 | different groups of particles can be released at the same time (see </font></span><a href="chapter_4.2.html#number_of_particle_groups"><span lang="en-GB"><font face="Thorndale, serif">number_of_particle_groups</font></span></a><span lang="en-GB"><font face="Thorndale, serif">) |
|---|
| 2137 | where each group may have a different source. All particles belonging |
|---|
| 2138 | to one group have the same density ratio and the same radius. All other |
|---|
| 2139 | particle features (e.g. location of the source) are |
|---|
| 2140 | identical for all groups of particles.</font></span></p>Subgrid |
|---|
| 2141 | scale velocities can (optionally) be included for calculating the |
|---|
| 2142 | particle advection, using the method of Weil et al. (2004, JAS, 61, |
|---|
| 2143 | 2877-2887). This method is switched on by the package |
|---|
| 2144 | parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>. |
|---|
| 2145 | This also forces the Euler/upstream method to be used for time |
|---|
| 2146 | advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>). |
|---|
| 2147 | The minimum timestep during the sub-timesteps is controlled by package |
|---|
| 2148 | parameter <a href="#dt_min_part">dt_min_part</a>. <p><span lang="en-GB"><font face="Thorndale, serif">By |
|---|
| 2149 | default, particles are weightless and transported passively with the |
|---|
| 2150 | resolved scale flow. Particles can be given a mass and thus an inertia |
|---|
| 2151 | by assigning the |
|---|
| 2152 | package parameter </font></span><a href="#density_ratio"><span lang="en-GB"><font face="Thorndale, serif">density_ratio</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> a |
|---|
| 2153 | non-zero value (it |
|---|
| 2154 | defines the ratio of the density of the fluid and the density of the |
|---|
| 2155 | particles). In these cases their </font></span><a href="#radius"><span lang="en-GB"><font face="Thorndale, serif">radius</font></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif"> |
|---|
| 2156 | must also be defined, which affects their flow resistance. </font></span><a href="#diameter"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif"> </font></span> </p> |
|---|
| 2157 | <p><span lang="en-GB"><font face="Thorndale, serif">Boundary |
|---|
| 2158 | conditions for the particle transport can be defined with package |
|---|
| 2159 | parameters </font></span><a href="#bc_par_t"><span lang="en-GB"><font face="Thorndale, serif">bc_par_t</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#bc_par_lr"><span lang="en-GB"><font face="Thorndale, serif">bc_par_lr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="bc_par_ns"><span lang="en-GB"><font face="Thorndale, serif">bc_par_ns</font></span></a> |
|---|
| 2160 | <span lang="en-GB"><font face="Thorndale, serif">and |
|---|
| 2161 | </font></span><a href="#bc_par_b"><span lang="en-GB"><font face="Thorndale, serif">bc_par_b</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span></p><span lang="en-GB"><font face="Thorndale, serif">Timeseries |
|---|
| 2162 | of particle quantities in NetCDF format can be output to local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a> |
|---|
| 2163 | by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br></font></span><p>For |
|---|
| 2164 | analysis, additional output of |
|---|
| 2165 | particle |
|---|
| 2166 | information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a> |
|---|
| 2167 | (file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br> |
|---|
| 2168 | </p> <p><span style="font-family: thorndale,serif;">Statistical |
|---|
| 2169 | informations</span> (e.g. the total number of particles used, the |
|---|
| 2170 | number of particles exchanged between the PEs, etc.) are output to the |
|---|
| 2171 | local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>, |
|---|
| 2172 | if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>. |
|---|
| 2173 | <br> </p> <p><span lang="en-GB"><font face="Thorndale, serif">If a job |
|---|
| 2174 | chain is to be carried out, particle |
|---|
| 2175 | informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current |
|---|
| 2176 | location of |
|---|
| 2177 | all |
|---|
| 2178 | particles at the end of the |
|---|
| 2179 | run) is output to |
|---|
| 2180 | the local file</font></span> <font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font><a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a><font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font>, |
|---|
| 2181 | <span lang="en-GB"><font face="Thorndale, serif">which |
|---|
| 2182 | must be saved at the |
|---|
| 2183 | end of the run <tt><span lang="en-GB"></span></tt>and |
|---|
| 2184 | given as an |
|---|
| 2185 | input file to the restart run |
|---|
| 2186 | under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a> |
|---|
| 2187 | u<span lang="en-GB"><font face="Thorndale, serif">sing |
|---|
| 2188 | respective file |
|---|
| 2189 | connection statements in the <span style="font-weight: bold;">mrun</span> |
|---|
| 2190 | configuration file. </font></span> <span lang="en-GB"></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of |
|---|
| 2191 | particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by |
|---|
| 2192 | the package |
|---|
| 2193 | parameter </font></span><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"><font face="Thorndale, serif">dt_dvrp</font></span></a><font face="Thorndale, serif"><span lang="en-GB">. |
|---|
| 2194 | For visualization |
|---|
| 2195 | purposes particles can be given a |
|---|
| 2196 | diameter by the parameter <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a> |
|---|
| 2197 | (this diameter only affects the visualization). All particles have the |
|---|
| 2198 | same size. Alternatively, particles can be given an individual size and |
|---|
| 2199 | a </span>color <span lang="en-GB">by modifying the |
|---|
| 2200 | user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">. |
|---|
| 2201 | Particles can pull a |
|---|
| 2202 | “tail” behind themselves to improve their |
|---|
| 2203 | visualization. |
|---|
| 2204 | This is steered via the parameter <a href="chapter_4.2.html#use_particle_tails">use_particle_tails</a>.</font></span><a href="chapter_4.2.html#maximum_number_of_tailpoints"><span lang="en-GB"></span></a></p> <span lang="en-GB"></span><p><b>So far, the |
|---|
| 2205 | particle transport realized in PALM does only |
|---|
| 2206 | work |
|---|
| 2207 | duly in case of a constant vertical grid spacing!</b></p> </td> |
|---|
| 2208 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2209 | <p><a name="bc_par_b"></a><b>bc_par_b</b></p> |
|---|
| 2210 | </td> <td style="vertical-align: top;">C*15</td> |
|---|
| 2211 | <td style="vertical-align: top;"><i>´reflect´</i></td> |
|---|
| 2212 | <td style="vertical-align: top;"> <p>Bottom |
|---|
| 2213 | boundary condition for particle transport. </p> <p>By |
|---|
| 2214 | default, particles are reflected at the bottom boundary. |
|---|
| 2215 | Alternatively, a particle absorption can set by <b>bc_par_b</b> |
|---|
| 2216 | = <i>´absorb´</i>.</p> </td> |
|---|
| 2217 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2218 | <p><a name="bc_par_lr"></a><b>bc_par_lr</b></p> |
|---|
| 2219 | </td> <td style="vertical-align: top;">C*15</td> |
|---|
| 2220 | <td style="vertical-align: top;"><i>´cyclic´</i></td> |
|---|
| 2221 | <td style="vertical-align: top;"> <p>Lateral |
|---|
| 2222 | boundary condition (x-direction) for particle |
|---|
| 2223 | transport. </p> <p>By default, cyclic boundary conditions |
|---|
| 2224 | are used along x. |
|---|
| 2225 | Alternatively, reflection (<b>bc_par_lr</b> |
|---|
| 2226 | = <i>´reflect´</i>) or absorption (<b>bc_par_lr</b> |
|---|
| 2227 | = <i>´absorb´</i>) |
|---|
| 2228 | can be set. <br> </p> <p>This lateral boundary |
|---|
| 2229 | conditions should correspond to the |
|---|
| 2230 | lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p> </td> |
|---|
| 2231 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2232 | <p><a name="bc_par_ns"></a><b>bc_par_ns</b></p> |
|---|
| 2233 | </td> <td style="vertical-align: top;">C*15</td> |
|---|
| 2234 | <td style="vertical-align: top;"><i>´cyclic´</i></td> |
|---|
| 2235 | <td style="vertical-align: top;"> <p>Lateral |
|---|
| 2236 | boundary condition (y-direction) for particle |
|---|
| 2237 | transport. </p> <p>By default, cyclic boundary conditions |
|---|
| 2238 | are used along y. |
|---|
| 2239 | Alternatively, reflection (<b>bc_par_ns</b> |
|---|
| 2240 | = <i>´reflect´</i>) or absorption (<b>bc_par_ns</b> |
|---|
| 2241 | = <i>´absorb´</i>) |
|---|
| 2242 | can be set.<br> </p> |
|---|
| 2243 | This lateral boundary conditions should correspond to the lateral |
|---|
| 2244 | boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td> </tr> |
|---|
| 2245 | <tr> <td style="vertical-align: top;"> <p><a name="bc_par_t"></a><b>bc_par_t</b></p> |
|---|
| 2246 | </td> <td style="vertical-align: top;">C*15</td> |
|---|
| 2247 | <td style="vertical-align: top;"><i>´absorb´</i></td> |
|---|
| 2248 | <td style="vertical-align: top;"> <p>Top boundary |
|---|
| 2249 | condition for particle transport. </p> <p>By default, |
|---|
| 2250 | particles are absorbed at the top boundary. |
|---|
| 2251 | Alternatively, a reflection condition can be set by <b>bc_par_t</b> |
|---|
| 2252 | = <i>´reflect´</i>.</p> </td> |
|---|
| 2253 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2254 | <p><a name="density_ratio"></a><b>density_ratio</b></p> |
|---|
| 2255 | </td> <td style="vertical-align: top;">R (10)</td> |
|---|
| 2256 | <td style="vertical-align: top;"> <p><i>0.0, 9</i> |
|---|
| 2257 | *<br> <i>9999999.9</i></p> </td> <td style="vertical-align: top;"> <p>Ratio of the density |
|---|
| 2258 | of the fluid and the density of the |
|---|
| 2259 | particles. </p> <p>With the default value<i> </i>the |
|---|
| 2260 | particles are weightless and transported passively with the resolved |
|---|
| 2261 | scale flow. |
|---|
| 2262 | In case of <span style="font-weight: bold;">density_ratio</span> |
|---|
| 2263 | /= |
|---|
| 2264 | 0.0 particles have a mass and hence inertia so that their velocity |
|---|
| 2265 | deviates more or less from the velocity of the surrounding flow. |
|---|
| 2266 | Particle velocity is calculated analytically and depends on (besides |
|---|
| 2267 | the density ratio and the current velocity difference between particles |
|---|
| 2268 | and surrounding fluid) the |
|---|
| 2269 | particle radius which is determined via <a href="#radius">radius</a> |
|---|
| 2270 | as well as on the molecular viscosity (assumed as 1.461E-5 m<sup>2</sup>/s). |
|---|
| 2271 | </p> <p>If <b>density_ratio</b> = <i>1.0</i>, |
|---|
| 2272 | the particle density |
|---|
| 2273 | corresponds to the density of the surrounding fluid and the particles |
|---|
| 2274 | do not feel any buoyancy. Otherwise, particles will be accelerated |
|---|
| 2275 | upwards (<b>density_ratio</b> > <i>1.0</i>) |
|---|
| 2276 | or downwards (<b>density_ratio</b> < <i>1.0</i>).<br> |
|---|
| 2277 | </p> <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>), |
|---|
| 2278 | each group can be assigned a different value. If the number of values |
|---|
| 2279 | given for <span style="font-weight: bold;">density_ratio</span> |
|---|
| 2280 | is less than the number of |
|---|
| 2281 | groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>, |
|---|
| 2282 | then the last assigned value is used for all remaining groups. This |
|---|
| 2283 | means that by default the particle density ratio for all groups will be |
|---|
| 2284 | <span style="font-style: italic;">0.0</span>.</p> |
|---|
| 2285 | </td> </tr> <tr><td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><i>value of <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td><td align="left" valign="top"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal |
|---|
| 2286 | interval</font> at which time series data of particle quantities |
|---|
| 2287 | shall be output (</font>in <font face="Thorndale">s). </font></p> |
|---|
| 2288 | <span lang="en-GB"><font face="Thorndale">If |
|---|
| 2289 | particle advection is switched on (see</font></span><font><span style="font-family: thorndale;"> <a href="#dt_prel">dt_prel</a>) |
|---|
| 2290 | this parameter can be used to assign |
|---|
| 2291 | th</span></font><span lang="en-GB"><font face="Thorndale">e temporal |
|---|
| 2292 | interval at which time series of particle quantities shall be output. |
|---|
| 2293 | Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br><br>The |
|---|
| 2294 | following list gives a short description of the quantities |
|---|
| 2295 | available. Most quantities are averages over all particles. The |
|---|
| 2296 | quantity name given in the first column is identical to the respective |
|---|
| 2297 | name of the variable on the NetCDF file (see section <a href="chapter_4.5.1.html">4.5.1</a> for a general |
|---|
| 2298 | description of the NetCDF files).<br><br>In case of using |
|---|
| 2299 | more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>), |
|---|
| 2300 | seperate time series are output for each of the groups. The long names |
|---|
| 2301 | of the variables in the NetCDF file containing the respective |
|---|
| 2302 | timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle |
|---|
| 2303 | group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br> </font></span><table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td><td align="undefined" valign="undefined">total number of |
|---|
| 2304 | particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td><td align="undefined" valign="undefined">particle |
|---|
| 2305 | x-coordinate with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td><td align="undefined" valign="undefined">particle |
|---|
| 2306 | y-coordinate with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td><td align="undefined" valign="undefined">particle |
|---|
| 2307 | z-coordinate with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td><td align="undefined" valign="undefined">absolute |
|---|
| 2308 | particle z-coordinate (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td><td align="undefined" valign="undefined">u particle |
|---|
| 2309 | velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td><td align="undefined" valign="undefined">v particle |
|---|
| 2310 | velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td><td align="undefined" valign="undefined">w particle |
|---|
| 2311 | velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td><td align="undefined" valign="undefined">subgrid-scale u |
|---|
| 2312 | particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td><td align="undefined" valign="undefined">subgrid-scale v |
|---|
| 2313 | particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td><td align="undefined" valign="undefined">subgrid-scale w |
|---|
| 2314 | particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td><td align="undefined" valign="undefined">total number of |
|---|
| 2315 | upward moving particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td><td align="undefined" valign="undefined">vertical |
|---|
| 2316 | velocity of the upward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td><td align="undefined" valign="undefined">vertical |
|---|
| 2317 | velocity of the downward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td><td align="undefined" valign="undefined">maximum number |
|---|
| 2318 | of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td><td align="undefined" valign="undefined">minimum number |
|---|
| 2319 | of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td><td align="undefined" valign="undefined">variance of the |
|---|
| 2320 | particle x-coordinate with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td><td align="undefined" valign="undefined">variance of the |
|---|
| 2321 | particle y-coordinate with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td><td align="undefined" valign="undefined">variance of the |
|---|
| 2322 | particle z-coordinate with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td><td align="undefined" valign="undefined">variance of the |
|---|
| 2323 | u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v*2</td><td align="undefined" valign="undefined">variance of the |
|---|
| 2324 | v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w*2</td><td align="undefined" valign="undefined">variance of the |
|---|
| 2325 | w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">u"2</td><td align="undefined" valign="undefined">variance of the |
|---|
| 2326 | subgrid-scale u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v"2</td><td align="undefined" valign="undefined">variance of the |
|---|
| 2327 | subgrid-scale v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w"2</td><td align="undefined" valign="undefined">variance of the |
|---|
| 2328 | subgrid-scale w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">npt*2</td><td align="undefined" valign="undefined">variance of the |
|---|
| 2329 | number of particles with respect to the average number of particles per |
|---|
| 2330 | subdomain</td></tr></tbody></table><span lang="en-GB"></span><span lang="en-GB"></span></td></tr><tr><td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td><td align="left" valign="top">Minimum value for the |
|---|
| 2331 | particle timestep when SGS velocities are used (in s).<br><br>For |
|---|
| 2332 | a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td></tr><tr> |
|---|
| 2333 | <td style="vertical-align: top;"> <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b> |
|---|
| 2334 | <b>data</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 2335 | <td style="vertical-align: top;"> <p>Temporal |
|---|
| 2336 | interval for output of particle data (in s). </p> <p>T<span lang="en-GB"></span><a href="#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his |
|---|
| 2337 | parameter can be used to |
|---|
| 2338 | assign the temporal interval at which particle data shall be output.</font></span> |
|---|
| 2339 | Data are output to |
|---|
| 2340 | the local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>. |
|---|
| 2341 | <span style="font-family: mon;">See the file description |
|---|
| 2342 | for more |
|---|
| 2343 | details about its format</span>. </p> <p>By |
|---|
| 2344 | default, no particle data are output.</p> </td> </tr> |
|---|
| 2345 | <tr> <td style="vertical-align: top;"> <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p> |
|---|
| 2346 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 2347 | <td style="vertical-align: top;">0.2 * dx<br> </td> |
|---|
| 2348 | <td style="vertical-align: top;"> <p>Diameter that |
|---|
| 2349 | the particles is given in visualizations with |
|---|
| 2350 | the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2351 | software (in |
|---|
| 2352 | m). </p> <p>In case that particles are |
|---|
| 2353 | visualized with the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2354 | software (see <a href="chapter_4.5.7.html">chapter |
|---|
| 2355 | 4.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>. |
|---|
| 2356 | All |
|---|
| 2357 | particles are displayed with this same size.<br> </p> <p>Alternatively, |
|---|
| 2358 | the particle diameters can be set with the |
|---|
| 2359 | user-interface in routine <span style="font-family: monospace;">user_init_particles</span> |
|---|
| 2360 | (at the beginning of the simulation) and/or can be redefined after each |
|---|
| 2361 | timestep in routine <tt>user<font style="font-size: 11pt;" size="2">_particle_attributes</font></tt> |
|---|
| 2362 | (both routines can be found in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt><font style="font-size: 11pt;" size="2">)</font>. </p> |
|---|
| 2363 | <p><b>Note:</b> This parameter determines exclusively |
|---|
| 2364 | the size |
|---|
| 2365 | under which particles appear in the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2366 | visualization. The flow relevant particle radius is determined via the |
|---|
| 2367 | particle package parameter <a href="#radius">radius</a>!</p> |
|---|
| 2368 | </td> </tr> <tr><td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td><td align="left" valign="top">Time of the last release of |
|---|
| 2369 | particles (in s).<br><br>See also <a href="#particle_advection_start">particle_advection_start</a>.</td></tr><tr> |
|---|
| 2370 | <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td> |
|---|
| 2371 | <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br> </td> |
|---|
| 2372 | <td style="vertical-align: top;">Factor to define the real |
|---|
| 2373 | number of initial droplets in a grid box.<br> <br> |
|---|
| 2374 | In case of explicitly simulating cloud droplets (see <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>), |
|---|
| 2375 | the real number of initial droplets in a grid box is equal to the |
|---|
| 2376 | initial number of droplets in this box (defined by the particle source |
|---|
| 2377 | parameters <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a> |
|---|
| 2378 | <span lang="en-GB"><font face="Thorndale, serif">and |
|---|
| 2379 | </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>) |
|---|
| 2380 | times the <span style="font-weight: bold;">initial_weighting_factor</span>.</td> |
|---|
| 2381 | </tr> |
|---|
| 2382 | <tr> <td style="vertical-align: top;"> <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b> |
|---|
| 2383 | <br> <b>particles</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>1000</i></td> |
|---|
| 2384 | <td style="vertical-align: top;"> <p>Maximum number |
|---|
| 2385 | of particles (on a PE). </p> <p>This parameter |
|---|
| 2386 | allows to set the number of particles for which |
|---|
| 2387 | memory must be allocated at the beginning of the run. |
|---|
| 2388 | If this memory becomes insufficient during the run, due to the |
|---|
| 2389 | release of further particles (see <a href="#dt_prel">dt_prel</a>), |
|---|
| 2390 | then more memory is automatically allocated.<br> </p> |
|---|
| 2391 | For runs on several processors, <span style="font-weight: bold;">maximum_number_of_particles</span> |
|---|
| 2392 | defines |
|---|
| 2393 | the maximum number on each PE. This number must be larger than the |
|---|
| 2394 | maximum number of particles initially released in a subdomain.</td> |
|---|
| 2395 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2396 | <p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b> |
|---|
| 2397 | <br> <b>tailpoints</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>100</i></td> |
|---|
| 2398 | <td style="vertical-align: top;"> <p>Maximum number |
|---|
| 2399 | of tailpoints that a particle tail can |
|---|
| 2400 | have. </p> <p> <b>maximum_number_of_tailpoints</b> |
|---|
| 2401 | sets the number of descrete points the tail consists of. A new point is |
|---|
| 2402 | added to the particle tails after each time step. If the maximum number |
|---|
| 2403 | of tail |
|---|
| 2404 | points is reached after the corresponding number of timesteps, the |
|---|
| 2405 | oldest respective tail points is deleted within the following |
|---|
| 2406 | timestep. </p> <p>All particle tails have the |
|---|
| 2407 | same number of points. The maximum |
|---|
| 2408 | length of |
|---|
| 2409 | these |
|---|
| 2410 | tails is determined by the value of <b>maximum_number_of_tailpoints</b> |
|---|
| 2411 | and by the minimum distance between each of the adjoining |
|---|
| 2412 | tailpoints, which can be set by <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>. |
|---|
| 2413 | Additionally, it can be determined that the temporal displacement |
|---|
| 2414 | between the current position of the particle and the oldest point of |
|---|
| 2415 | the tail may become not larger than a value to be assigned by <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>.</p> |
|---|
| 2416 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b> |
|---|
| 2417 | <br> <b>age</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;">100000.0</td> <td style="vertical-align: top;"> <p>Maximum age that the |
|---|
| 2418 | end point of a particle tail is allowed to have (in s). </p> |
|---|
| 2419 | <p>If the temporal displacement between the oldest point of a |
|---|
| 2420 | particle tail and the current position of the particle becomes larger |
|---|
| 2421 | than the value given by <b>maximum_tailpoint_age</b>, this |
|---|
| 2422 | oldest |
|---|
| 2423 | point (which defines the end of the tail) is |
|---|
| 2424 | removed. If this time is so small that the number of points defining |
|---|
| 2425 | the particle tail do not exceed the value given by <b>maximum_number_of_tailpoints</b>, |
|---|
| 2426 | then the length the particle tails is a measure for the distance the |
|---|
| 2427 | particle travelled along during the time interval defined via <b>maximum_tailpoint_age</b>, |
|---|
| 2428 | i.e. for the |
|---|
| 2429 | particle velocity. Fast particles will have long tails, slow particles |
|---|
| 2430 | shorter ones (note: this will not neccessarily hold if <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a> |
|---|
| 2431 | = <i>0.0</i>).</p> </td> </tr> <tr> |
|---|
| 2432 | <td style="vertical-align: top;"> <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</b></p> |
|---|
| 2433 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 2434 | <td style="vertical-align: top;"><i>0.0</i></td> |
|---|
| 2435 | <td style="vertical-align: top;"> <p>Minimum |
|---|
| 2436 | distance allowed between two adjacent points of a |
|---|
| 2437 | particle tail (in m). </p> <p>In case of <b>minimum_tailpoint_distance</b> |
|---|
| 2438 | > <i>0.0 </i>the |
|---|
| 2439 | particle tail is extended by a new point only if the distance between |
|---|
| 2440 | its current position and the most recent tail point exceed the |
|---|
| 2441 | distance given via <b>minimum_tailpoint_distance</b>.<br> |
|---|
| 2442 | </p> <p>If the length of the particle tails shall be |
|---|
| 2443 | proportional to |
|---|
| 2444 | the respective particle velocity, the parameter <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a> |
|---|
| 2445 | must also be set appropriately. </p> <b>Note:</b><br> |
|---|
| 2446 | A suitable choice of <b>minimum_tailpoint_distance</b> |
|---|
| 2447 | > <i>0.0</i> is recommended, because then the tail |
|---|
| 2448 | coordinates of |
|---|
| 2449 | slowly moving particles require less memory and can also be drawn |
|---|
| 2450 | faster. The upper limit of <b>minimum_tailpoint_distance</b> |
|---|
| 2451 | should be chosen in a way that the visualized particle |
|---|
| 2452 | tails still appear as smooth lines. Example: with a model domain of |
|---|
| 2453 | 1000 m and a monitor resolution of 1280 * 1024 pixels it |
|---|
| 2454 | should be sufficient to set <b>minimum_tailpoint_distance</b> |
|---|
| 2455 | = <i>5.0</i> |
|---|
| 2456 | (m). </td> </tr> <tr> <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br> |
|---|
| 2457 | </td> <td style="vertical-align: top;">I<br> </td> |
|---|
| 2458 | <td style="vertical-align: top;">1<br> </td> <td style="vertical-align: top;">Number of particle groups to be |
|---|
| 2459 | used.<br> <br> |
|---|
| 2460 | Each particle group can be assigned its own source region (see <a href="#pdx">pdx</a>, <a href="#psl">psl</a>, |
|---|
| 2461 | <a href="#psr">psr</a>, etc.), particle diameter (<a href="#radius">radius</a>) and particle density ratio (<a href="density_ratio">density_ratio</a>).<br><br>If |
|---|
| 2462 | less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>, |
|---|
| 2463 | etc. than the number of particle groups, then the last value is used |
|---|
| 2464 | for the remaining values (or the default value, if the user did not set |
|---|
| 2465 | the parameter).<br> <br> |
|---|
| 2466 | The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br> </td> |
|---|
| 2467 | </tr> |
|---|
| 2468 | <tr><td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td><td align="left" valign="top">I</td><td align="left" valign="top">1</td><td align="left" valign="top">Number of particles to be |
|---|
| 2469 | started per point.<br><br>By default, one particle is |
|---|
| 2470 | started at all points of the particle source, defined by <span style="font-family: Thorndale,serif;">the </span><span lang="en-GB"><font face="Thorndale, serif">package |
|---|
| 2471 | parameters </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a> |
|---|
| 2472 | <span lang="en-GB"><font face="Thorndale, serif">and |
|---|
| 2473 | </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"></span></td></tr><tr> <td style="vertical-align: top;"> <p><a name="particle_advection_start"></a><b>particle_advection_</b> |
|---|
| 2474 | <br> <b>start</b></p> </td> <td style="vertical-align: top;">R </td> <td style="vertical-align: top;">0.0 </td> <td style="vertical-align: top;"> <p>Time of the first |
|---|
| 2475 | release of particles (in s). </p> <p>If particles are not |
|---|
| 2476 | to be released at the beginning of the |
|---|
| 2477 | run, the release time can be set via <b>particle_advection_start</b>.<br> |
|---|
| 2478 | If particle transport is switched on in a restart run, then <a href="#read_particles_from_restartfile">read_particles_from_restartfile</a> |
|---|
| 2479 | = <span style="font-style: italic;">.F.</span> is |
|---|
| 2480 | also required.</p><p>See also <a href="#end_time_prel">end_time_prel</a>. |
|---|
| 2481 | </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p> |
|---|
| 2482 | </td> <td style="vertical-align: top;">R </td> |
|---|
| 2483 | <td style="vertical-align: top;"><i>9999999.9</i> |
|---|
| 2484 | </td> <td style="vertical-align: top;"> <p>Maximum |
|---|
| 2485 | allowed age of particles (in s). </p> <p>If the |
|---|
| 2486 | age of a particle exceeds the time set by <b>particle_maximum_age</b>, |
|---|
| 2487 | the particle as well as its tail is deleted.</p> </td> </tr> |
|---|
| 2488 | <tr> <td style="vertical-align: top;"> <p><a name="pdx"></a><b>pdx</b></p> </td> |
|---|
| 2489 | <td style="vertical-align: top;">R (10)<br> </td> |
|---|
| 2490 | <td style="vertical-align: top;"><i>10 * dx</i> |
|---|
| 2491 | </td> <td style="vertical-align: top;"> <p>Distance |
|---|
| 2492 | along x between particles within a particle source |
|---|
| 2493 | (in m). </p> <p>If the particle source shall be |
|---|
| 2494 | confined to one grid point, |
|---|
| 2495 | the distances given by <span style="font-weight: bold;">pdx</span>, |
|---|
| 2496 | <a href="#pdy">pdy</a> |
|---|
| 2497 | and <a href="#pdz">pdz</a> |
|---|
| 2498 | must be set larger than the respective domain size or <a href="#psl">psl</a> |
|---|
| 2499 | = <a href="#psr">psr</a> has to be set |
|---|
| 2500 | alternatively.<br> |
|---|
| 2501 | </p> <p><span style="font-weight: bold;">pdx</span> |
|---|
| 2502 | can be assigned a different value for each particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>).<br> |
|---|
| 2503 | </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pdy"></a><b>pdy</b></p> |
|---|
| 2504 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2505 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2506 | * dy</i> </td> <td style="vertical-align: top;">Distance |
|---|
| 2507 | along y between |
|---|
| 2508 | particles within a |
|---|
| 2509 | particle source (in m). </td> </tr> <tr> |
|---|
| 2510 | <td style="vertical-align: top;"> <p><a name="pdz"></a><b>pdz</b></p> </td> |
|---|
| 2511 | <td style="vertical-align: top;">R (10)<br> |
|---|
| 2512 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2513 | * ( zu(2) - zu(1) )</i> </td> <td style="vertical-align: top;">Distance along z between |
|---|
| 2514 | particles within a particle source |
|---|
| 2515 | (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psb"></a><b>psb</b></p> |
|---|
| 2516 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2517 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2518 | * zu(nz/2)</i> </td> <td style="vertical-align: top;">Bottom |
|---|
| 2519 | edge of a particle |
|---|
| 2520 | source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psl"></a><b>psl</b></p> |
|---|
| 2521 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2522 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2523 | * 0.0</i> </td> <td style="vertical-align: top;">Left |
|---|
| 2524 | edge of a particle source |
|---|
| 2525 | (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psn"></a><b>psn</b></p> |
|---|
| 2526 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2527 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2528 | * (ny * dy)</i> </td> <td style="vertical-align: top;">Rear |
|---|
| 2529 | (“north”) edge of a |
|---|
| 2530 | particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psr"></a><b>psr</b></p> |
|---|
| 2531 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2532 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2533 | * (nx * dx)</i> </td> <td style="vertical-align: top;">Right |
|---|
| 2534 | edge of a particle |
|---|
| 2535 | source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pss"></a><b>pss</b></p> |
|---|
| 2536 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2537 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2538 | * 0.0</i> </td> <td style="vertical-align: top;">Front |
|---|
| 2539 | (“south”) edge of a |
|---|
| 2540 | particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pst"></a><b>pst</b></p> |
|---|
| 2541 | </td> <td style="vertical-align: top;">R (10)<br> |
|---|
| 2542 | </td> <td style="vertical-align: top;"><i>10 |
|---|
| 2543 | * zu(nz/2)</i> </td> <td style="vertical-align: top;">Top |
|---|
| 2544 | edge of a particle source |
|---|
| 2545 | (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="radius"></a><b>radius</b></p> |
|---|
| 2546 | </td> <td style="vertical-align: top;">R (10)</td> |
|---|
| 2547 | <td style="vertical-align: top;"><i>0.0, 9</i>*<br> |
|---|
| 2548 | <i>9999999.9</i></td> <td style="vertical-align: top;">Particle radius (in m).<br> |
|---|
| 2549 | <br> |
|---|
| 2550 | The viscous friction (in case of a velocity difference between |
|---|
| 2551 | particles and surrounding fluid) depends on the particle radius which |
|---|
| 2552 | must be assigned as soon as <a href="chapter_4.2.html#density_ratio">density_ratio</a> |
|---|
| 2553 | /= <i>0.0</i>.<br> <br> |
|---|
| 2554 | With several groups of particles (see <a href="#number_of_particle_groups">number_of_particle_groups</a>), |
|---|
| 2555 | each group can be assigned a different value. If the number of values |
|---|
| 2556 | given for <span style="font-weight: bold;">radius</span> |
|---|
| 2557 | is less than the number of |
|---|
| 2558 | groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>, |
|---|
| 2559 | then the last assigned value is used for all remaining groups. This |
|---|
| 2560 | means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br> </td> |
|---|
| 2561 | </tr> |
|---|
| 2562 | <tr> <td style="vertical-align: top;"> <p><a name="random_start_position"></a><b>random_start_position</b></p> |
|---|
| 2563 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 2564 | <td style="vertical-align: top;"><i>.F.</i> </td> |
|---|
| 2565 | <td style="vertical-align: top;"> <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span> |
|---|
| 2566 | particles is |
|---|
| 2567 | varied randomly within certain limits. </p> <p>By |
|---|
| 2568 | default, the initial positions of particles within the |
|---|
| 2569 | source excatly correspond with the positions given by <a href="#psl">psl</a>, |
|---|
| 2570 | <a href="#psr">psr</a>, <a href="#psn">psn</a>, |
|---|
| 2571 | <a href="#pss">pss</a>, <a href="#psb">psb</a>, |
|---|
| 2572 | <a href="#pst">pst</a>, <a href="#pdx">pdx</a>, |
|---|
| 2573 | <a href="#pdy">pdy</a>, |
|---|
| 2574 | and<a href="#pdz"> |
|---|
| 2575 | pdz</a>. With <b>random_start_position</b> = <i>.T. |
|---|
| 2576 | </i>the initial |
|---|
| 2577 | positions of the particles are allowed to randomly vary from these |
|---|
| 2578 | positions within certain limits. </p> <p><b>Very |
|---|
| 2579 | important:<br> </b>In case of <b>random_start_position</b> |
|---|
| 2580 | = <i>.T.</i>, the |
|---|
| 2581 | random-number generators on the individual PEs no longer |
|---|
| 2582 | run synchronously. If random disturbances are applied to the velocity |
|---|
| 2583 | field |
|---|
| 2584 | (see <a href="#create_disturbances">create_disturbances</a>), |
|---|
| 2585 | <font color="#000000">then as consequence for parallel |
|---|
| 2586 | runs the |
|---|
| 2587 | realizations of the turbulent flow |
|---|
| 2588 | fields will deviate between runs which used different numbers of PEs!</font></p> |
|---|
| 2589 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b> |
|---|
| 2590 | <br> <b>restartfile</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td> |
|---|
| 2591 | <td style="vertical-align: top;"> <p>Read particle |
|---|
| 2592 | data from the previous run. </p> <p>By default, |
|---|
| 2593 | with restart runs particle data is read |
|---|
| 2594 | from file <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>, |
|---|
| 2595 | which is created by the preceding run. If this is not requested or if |
|---|
| 2596 | in a restart run particle transport is switched on for the |
|---|
| 2597 | first time (see <a href="#particle_advection_start">particle_advection_start</a>), |
|---|
| 2598 | then <b>read_particles_from_restartfile</b> = <i>.F.</i> |
|---|
| 2599 | is required.</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br> |
|---|
| 2600 | </td> <td style="vertical-align: top;">I<br> </td> |
|---|
| 2601 | <td style="vertical-align: top;"><span style="font-style: italic;">1</span><br> </td> |
|---|
| 2602 | <td style="vertical-align: top;">Limit the number of |
|---|
| 2603 | particle tails.<br> <br> |
|---|
| 2604 | If particle tails are switched on (see <a href="#use_particle_tails">use_particle_tails</a>), |
|---|
| 2605 | every particle is given a tail by default. <span style="font-weight: bold;">skip_particles_for_tail </span>can |
|---|
| 2606 | be used to give only every n'th particle a tail.<br> <br> <span style="font-weight: bold;">Example:</span><br> <span style="font-weight: bold;">skip_particles_for_tail</span> |
|---|
| 2607 | = <span style="font-style: italic;">10</span> means |
|---|
| 2608 | that only every 10th particle will be given a tail.<br> </td> |
|---|
| 2609 | </tr> <tr> <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</span><br> |
|---|
| 2610 | </td> <td style="vertical-align: top;">L<br> </td> |
|---|
| 2611 | <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td> |
|---|
| 2612 | <td style="vertical-align: top;">Give particles a tail.<br> |
|---|
| 2613 | <br> |
|---|
| 2614 | A particle tail is defined by the path a particle has moved |
|---|
| 2615 | along starting from some point of time in the past. It consists of a |
|---|
| 2616 | set of descrete points in space which may e.g. be connected by a line |
|---|
| 2617 | in order visualize how the particle has moved.<br> <br> |
|---|
| 2618 | By default, particles have no tail. Parameter <a href="#skip_particles_for_tail">skip_particles_for_tail</a> |
|---|
| 2619 | can be used to give only every n'th particle a tail.<br> <br> |
|---|
| 2620 | The length of the tail is controlled by parameters <a href="#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>, <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>, |
|---|
| 2621 | and <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.<br> |
|---|
| 2622 | </td> </tr> |
|---|
| 2623 | <tr><td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</span></td><td align="left" valign="top">L</td><td align="left" valign="top"><span style="font-style: italic;">.F.</span></td><td align="left" valign="top">Use subgrid-scale |
|---|
| 2624 | velocities for particle advection.<br><br>These |
|---|
| 2625 | velocities are calculated from the resolved and subgrid-scale TKE using |
|---|
| 2626 | the Monte-Carlo random-walk method described by Weil et al. (2004, JAS, |
|---|
| 2627 | 61, |
|---|
| 2628 | 2877-2887). When using this method, the timestep for the advancement of |
|---|
| 2629 | the particles is limited by the so-called Lagrangian time scale. This |
|---|
| 2630 | may be smaller than the current LES timestep so that several particle |
|---|
| 2631 | (sub-) timesteps have to be carried out within one LES timestep. In |
|---|
| 2632 | order to limit the number of sub-timesteps (and to limit the CPU-time), |
|---|
| 2633 | the minimum value for the particle timestep is defined by the package |
|---|
| 2634 | parameter <a href="#dt_min_part">dt_min_part</a>.<br><br>Setting |
|---|
| 2635 | <span style="font-weight: bold;">use_sgs_for_particles</span> |
|---|
| 2636 | = <span style="font-style: italic;">.TRUE.</span> |
|---|
| 2637 | automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a> |
|---|
| 2638 | = <span style="font-style: italic;">.TRUE.</span>. |
|---|
| 2639 | This inhibits the occurrence of large (artificial) spatial gradients of |
|---|
| 2640 | the subgrid-scale TKE which otherwise would lead to wrong results for |
|---|
| 2641 | the particle advection.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b> |
|---|
| 2642 | <br> <b>advection</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td> |
|---|
| 2643 | <td style="vertical-align: top;"> <p>Switch on/off |
|---|
| 2644 | vertical particle transport. </p> <p>By default, |
|---|
| 2645 | particles are transported along all three |
|---|
| 2646 | directions in space. With <b>vertical_particle_advection</b> |
|---|
| 2647 | = <i>.F., </i>the |
|---|
| 2648 | particles will only be transported horizontally.</p> </td> |
|---|
| 2649 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2650 | <p><a name="write_particle_statistics"></a><b>write_particle_</b> |
|---|
| 2651 | <br> <b>statistics</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.F.</i> </td> |
|---|
| 2652 | <td style="vertical-align: top;"> <p>Switch on/off |
|---|
| 2653 | output of particle informations.<br> </p> <p><br> |
|---|
| 2654 | For <span style="font-weight: bold;">write_particle_statistics</span> |
|---|
| 2655 | = <span style="font-style: italic;">.T.</span> s<span style="font-family: thorndale,serif;">tatistical |
|---|
| 2656 | informations</span> (e.g. the total number of particles used, the |
|---|
| 2657 | number of particles exchanged between the PEs, etc.) which may be used |
|---|
| 2658 | for debugging are output to the |
|---|
| 2659 | local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>. |
|---|
| 2660 | </p> <p><b>Note:</b> For parallel runs files |
|---|
| 2661 | may become very large |
|---|
| 2662 | and performance of PALM may decrease.</p> </td> </tr> |
|---|
| 2663 | </tbody> |
|---|
| 2664 | </table><span style="font-weight: bold;"><br> |
|---|
| 2665 | <br></span><span style="font-weight: bold;">Package |
|---|
| 2666 | (<span style="font-weight: bold;">mrun</span> option |
|---|
| 2667 | -p): <span style="font-weight: bold;"><a name="dvrp_graphics"></a>dvrp_graphics</span> |
|---|
| 2668 | |
|---|
| 2669 | NAMELIST group name: <span style="font-weight: bold;">dvrp_graphics_par<br> |
|---|
| 2670 | <br></span></span> |
|---|
| 2671 | <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr> |
|---|
| 2672 | <td style="vertical-align: top;"><font size="4"><b>Parameter |
|---|
| 2673 | name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td> |
|---|
| 2674 | <td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td> |
|---|
| 2675 | <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td> |
|---|
| 2676 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2677 | <p><a name="dt_dvrp"></a><b>dt_dvrp</b></p> |
|---|
| 2678 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 2679 | <td style="vertical-align: top;"><i>9999999.9</i></td> |
|---|
| 2680 | <td style="vertical-align: top;"> <p>Temporal |
|---|
| 2681 | interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in |
|---|
| 2682 | s). </p> <p>Isosurfaces, cross sections and |
|---|
| 2683 | particles can be displayed |
|---|
| 2684 | simultaneous. The display of particles requires that the particle |
|---|
| 2685 | transport is switched on (see <a href="#dt_prel">dt_prel</a>). |
|---|
| 2686 | Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p> <p>If |
|---|
| 2687 | output of scenes created by dvrp software is switched on |
|---|
| 2688 | (see <a href="#mode_dvrp">mode_dvrp</a>), |
|---|
| 2689 | this parameter can be used to assign the temporal interval at which |
|---|
| 2690 | scenes are to be created (and the respective graphical data |
|---|
| 2691 | is to |
|---|
| 2692 | be output to the streaming server). <span lang="en-GB"><font face="Thorndale">Reference time is the beginning of |
|---|
| 2693 | the simulation, i.e. output takes place at times t = <b>dt_dvrp</b>, |
|---|
| 2694 | 2*<b>dt_dvrp</b>, 3*<b>dt_dvrp</b>, etc. The |
|---|
| 2695 | actual output times can |
|---|
| 2696 | deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). |
|---|
| 2697 | Is <b>dt_dvrp</b> < </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then |
|---|
| 2698 | scenes are created and |
|---|
| 2699 | output after each time step (if this is requested it should be <b>dt_dvrp</b> |
|---|
| 2700 | = <i>0</i>).</font></span> </p> </td> |
|---|
| 2701 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2702 | <p><a name="dvrp_directory"></a><b>dvrp_directory</b></p> |
|---|
| 2703 | </td> <td style="vertical-align: top;">C*80</td> |
|---|
| 2704 | <td style="vertical-align: top;"><i>'default'</i></td> |
|---|
| 2705 | <td style="vertical-align: top;"> <p>Name of the |
|---|
| 2706 | directory into which data created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2707 | software shall be saved. </p> <p>By default, |
|---|
| 2708 | the directory name is generated from the user |
|---|
| 2709 | name |
|---|
| 2710 | (see package parameter <a href="#dvrp_username">dvrp_username</a>) |
|---|
| 2711 | and the base file name (given as the argument of <span style="font-weight: bold;">mrun</span> option -d) as <span style="font-style: italic;">'<user |
|---|
| 2712 | name>/<base file name>'</span>.</p> </td> |
|---|
| 2713 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2714 | <p><a name="dvrp_file"></a><b>dvrp_file</b></p> |
|---|
| 2715 | </td> <td style="vertical-align: top;">C*80</td> |
|---|
| 2716 | <td style="vertical-align: top;"><i>'default'</i></td> |
|---|
| 2717 | <td style="vertical-align: top;"> <p>Name of the |
|---|
| 2718 | file into which data created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2719 | software shall be output. </p> <p>This |
|---|
| 2720 | parameter can be given a value only in case of <a href="#dvrp_output">dvrp_output</a> |
|---|
| 2721 | = <span style="font-style: italic;">'local'</span><i> |
|---|
| 2722 | </i>which |
|---|
| 2723 | determines that the data created by <span style="font-weight: bold;">dvrp</span> |
|---|
| 2724 | is output to a local file (on the machine where PALM is executed). |
|---|
| 2725 | Apart from the default, it is only allowed to assign <span style="font-style: italic;">'/dev/null'</span> (which |
|---|
| 2726 | means that no output is really stored). This can be used for special |
|---|
| 2727 | runtime measurements of the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2728 | software.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_host"></a><b>dvrp_host</b></p> |
|---|
| 2729 | </td> <td style="vertical-align: top;">C*80</td> |
|---|
| 2730 | <td style="vertical-align: top;"> <p><i>'origin.rvs.</i> |
|---|
| 2731 | <br> |
|---|
| 2732 | u<i>ni- hanover.de'</i></p> </td> <td style="vertical-align: top;"> <p>Name of the computer |
|---|
| 2733 | to which data created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2734 | software shall be |
|---|
| 2735 | transferred. </p> <p>In case of <a href="#dvrp_output">dvrp_output</a> |
|---|
| 2736 | = <span style="font-style: italic;">'rtsp'</span> |
|---|
| 2737 | only the default |
|---|
| 2738 | value is allowed (streaming server of |
|---|
| 2739 | the RRZN). For <a href="#dvrp_output">dvrp_output</a> |
|---|
| 2740 | = <span style="font-style: italic;">'local'</span><i> |
|---|
| 2741 | </i>the |
|---|
| 2742 | assigned value is ignored.</p> </td> </tr> <tr> |
|---|
| 2743 | <td style="vertical-align: top;"> <p><a name="dvrp_output"></a><b>dvrp_output</b></p> |
|---|
| 2744 | </td> <td style="vertical-align: top;">C*10</td> |
|---|
| 2745 | <td style="vertical-align: top;"><i>'rtsp'</i></td> |
|---|
| 2746 | <td style="vertical-align: top;"> <p>Output mode |
|---|
| 2747 | for the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2748 | software. <br> <br> </p> |
|---|
| 2749 | The following settings are allowed:<br> <br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'rtsp'</i></td> |
|---|
| 2750 | <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2751 | software is transferred using |
|---|
| 2752 | a special transmission protocol to a so-called streaming server, which |
|---|
| 2753 | is able to continuously transfer visualization data with a |
|---|
| 2754 | high transmission rate. <br> |
|---|
| 2755 | Additionally, with this output mode a |
|---|
| 2756 | set of files is generated automatically |
|---|
| 2757 | within a directory on the streaming server (beside the visualization |
|---|
| 2758 | data e.g. some html-files) which can be used to |
|---|
| 2759 | visualize the data via an internet-browser plugin. Host |
|---|
| 2760 | (streaming-server) and directory can be defined by the user with <a href="#dvrp_host">dvrp_host</a> |
|---|
| 2761 | and <a href="#dvrp_directory">dvrp_directory</a>.</td> |
|---|
| 2762 | </tr> <tr> <td style="vertical-align: top;"><i>'ftp'</i></td> |
|---|
| 2763 | <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2764 | software is transferred to the destination host (see <a href="#dvrp_host">dvrp_host</a> |
|---|
| 2765 | and <a href="#dvrp_directory">dvrp_directory</a>) |
|---|
| 2766 | using ftp.</td> </tr> <tr> <td style="vertical-align: top;"><i>'local'</i></td> |
|---|
| 2767 | <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2768 | software is output locally on a file defined by <a href="#dvrp_file">dvrp_file |
|---|
| 2769 | </a>.</td> </tr> </tbody> </table> <br> |
|---|
| 2770 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_password"></a><b>dvrp_password</b></p> |
|---|
| 2771 | </td> <td style="vertical-align: top;">C*80</td> |
|---|
| 2772 | <td style="vertical-align: top;">'********'</td> <td style="vertical-align: top;"> <p>Password for the |
|---|
| 2773 | computer to which data created by the <span style="font-weight: bold;">dvrp</span> software is to |
|---|
| 2774 | be |
|---|
| 2775 | transferred. </p> <p>Assigning a password is |
|---|
| 2776 | only necessary in case of <a href="#dvrp_output">dvrp_output</a> |
|---|
| 2777 | = <span style="font-style: italic;">'ftp'</span>. |
|---|
| 2778 | For <a href="#dvrp_output">dvrp_output</a> |
|---|
| 2779 | = <span style="font-style: italic;">'rtsp'</span><i> |
|---|
| 2780 | </i>the default |
|---|
| 2781 | value must not be changed!</p> </td> </tr> <tr> |
|---|
| 2782 | <td style="vertical-align: top;"> <p><a name="dvrp_username"></a><b>dvrp_username</b></p> |
|---|
| 2783 | </td> <td style="vertical-align: top;">C*80</td> |
|---|
| 2784 | <td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>User name of a valid |
|---|
| 2785 | account on the computer to which data |
|---|
| 2786 | created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2787 | software |
|---|
| 2788 | is to be |
|---|
| 2789 | transferred. </p> <p>Assigning a value to this |
|---|
| 2790 | parameter is required in case of <a href="#dvrp_output">dvrp_output</a> |
|---|
| 2791 | = <span style="font-style: italic;">'rtsp'</span> |
|---|
| 2792 | or <span style="font-style: italic;">'ftp'</span>.</p> |
|---|
| 2793 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p> |
|---|
| 2794 | </td> <td style="vertical-align: top;">C*20 |
|---|
| 2795 | <br>(10)</td> <td style="vertical-align: top;"><i>10 |
|---|
| 2796 | * ''</i></td> <td style="vertical-align: top;"> |
|---|
| 2797 | <p>Graphical objects (isosurfaces, slicers, particles) which are |
|---|
| 2798 | to be created by the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2799 | software. </p> <p>Several different objects can |
|---|
| 2800 | be assigned simultaneously and |
|---|
| 2801 | will be displayed in the same scene. Allowed values for <span style="font-weight: bold;">mode_dvrp</span> are <span style="font-style: italic;">'isosurface#'</span> |
|---|
| 2802 | (isosurface), <span style="font-style: italic;">'slicer#'</span> |
|---|
| 2803 | (cross sections), and <span style="font-style: italic;">'particles'</span>. |
|---|
| 2804 | Within the strings the hash character ("#") has to be replaced by a |
|---|
| 2805 | digit ≤9. Up to 10 objects |
|---|
| 2806 | can be assigned at the same time, e.g. : </p> <blockquote><b>mode_dvrp</b> |
|---|
| 2807 | = <span style="font-style: italic;">'isosurface2'</span><i>, |
|---|
| 2808 | 'slicer1', |
|---|
| 2809 | 'particles', 'slicer2'</i></blockquote> <p>In this |
|---|
| 2810 | case one isosurface, two cross sections, and particles |
|---|
| 2811 | will be created. The quantities for which an isosurface are to be |
|---|
| 2812 | created have to be selected with |
|---|
| 2813 | the parameter <a href="#data_output">data_output</a>, |
|---|
| 2814 | those for cross sections with <a href="#data_output">data_output</a> |
|---|
| 2815 | (<span style="font-weight: bold;">data_output</span> |
|---|
| 2816 | also determines the |
|---|
| 2817 | orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> lists of |
|---|
| 2818 | variables may be |
|---|
| 2819 | assigned, the digit at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string |
|---|
| 2820 | selects the quantity, which is given |
|---|
| 2821 | at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface2'</span> |
|---|
| 2822 | selects the quantity |
|---|
| 2823 | given in the second position of <span style="font-weight: bold;">data_output</span>). |
|---|
| 2824 | If e.g. <span style="font-weight: bold;">data_output</span> |
|---|
| 2825 | and <span style="font-weight: bold;">data_output</span> |
|---|
| 2826 | are assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>, |
|---|
| 2827 | 'w_xz', 'v_yz'</i> and <b>data_output</b> = <span style="font-style: italic;">'pt'</span><i>, |
|---|
| 2828 | 'u', 'w' </i>are |
|---|
| 2829 | indicated, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an |
|---|
| 2830 | isosurface of u, a |
|---|
| 2831 | horizontal cross section of u and |
|---|
| 2832 | a vertical cross section (xz) of w is created. For locations of the |
|---|
| 2833 | cross sections see <a href="#data_output">data_output</a>. |
|---|
| 2834 | The theshold value for which the isosurface is |
|---|
| 2835 | to be created can be defined with parameter <a href="#threshold">threshold</a>.<br> |
|---|
| 2836 | </p> <p>The vertical extension of the displayed domain is |
|---|
| 2837 | given by <a href="#nz_do3d">nz_do3d</a>.<br> </p> |
|---|
| 2838 | <p>The vertical extension of the displayed domain is given by <a href="#nz_do3d">nz_do3d</a>. </p> <p><b>Assignments |
|---|
| 2839 | of mode_dvrp must correspond to those of data_output |
|---|
| 2840 | and |
|---|
| 2841 | data_output! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span> |
|---|
| 2842 | and <b>data_output</b> |
|---|
| 2843 | = 'w'<i> </i>was set, then only the digit "1" is allowed |
|---|
| 2844 | for <b>mode_dvrp</b>, |
|---|
| 2845 | thus <span style="font-style: italic;">'isosurface1'</span> |
|---|
| 2846 | and/or <span style="font-style: italic;">'slicer1'</span><i>.</i> |
|---|
| 2847 | </p> <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are |
|---|
| 2848 | given in <a href="chapter_4.5.7.html">chapter |
|---|
| 2849 | 4.5.7</a>.<br> </p> <b>Note:</b><br> |
|---|
| 2850 | The declaration color charts to be |
|---|
| 2851 | used still have to be given "manually" in subroutine <span style="font-family: monospace;">user_dvrp_coltab</span> |
|---|
| 2852 | (file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>). |
|---|
| 2853 | <br>A change of particle colors and/or particle diameters (e.g. |
|---|
| 2854 | according |
|---|
| 2855 | to the local characteristics of the flow field) to be used for the |
|---|
| 2856 | visualization, must be carried out by adding respective code extensions |
|---|
| 2857 | to <tt><font style="font-size: 11pt;" size="2">user_particle_attributes</font></tt> |
|---|
| 2858 | (in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>). </td> |
|---|
| 2859 | </tr> <tr> <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br> |
|---|
| 2860 | dvrp</span></td> <td style="vertical-align: top;">R(2,10)</td> |
|---|
| 2861 | <td style="vertical-align: top;"><span style="font-style: italic;">10 |
|---|
| 2862 | * (-1,1)</span></td> <td style="vertical-align: top;">Ranges |
|---|
| 2863 | of values to which a color table has to be mapped (units of the |
|---|
| 2864 | respective quantity).<br> <br> |
|---|
| 2865 | In case that slicers have to be displayed (see <a href="#threshold">mode_dvrp</a>), |
|---|
| 2866 | this parameter defines the ranges of values of the respective |
|---|
| 2867 | quantities to which the colortable in use has to be mapped. If e.g. a |
|---|
| 2868 | temperature slice shall be displayed, the colortable defines colors |
|---|
| 2869 | from blue to red, and <span style="font-weight: bold;">slicer_range_limits_dvrp</span> |
|---|
| 2870 | = 290.0, 305.0 then areas with temperature of 290 K are displayed in |
|---|
| 2871 | dark blue and those with 305.0 are displayed in dark red. Temperatures |
|---|
| 2872 | within these limits will be displayed by a continuous color gradient |
|---|
| 2873 | from blue to red and Temperatures outside the limits will |
|---|
| 2874 | be displayed either in dark blue or in dark red.<br> <br> |
|---|
| 2875 | Up to ten different ranges can be assigned in case that more than one |
|---|
| 2876 | slicer has to be displayed.<br> <br> |
|---|
| 2877 | See <a href="#threshold">mode_dvrp</a> |
|---|
| 2878 | for the declaration of color charts.</td> </tr> <tr> |
|---|
| 2879 | <td style="vertical-align: top;"> <p><a name="superelevation"></a><b>superelevation</b></p> |
|---|
| 2880 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 2881 | <td style="vertical-align: top;"><i>1.0</i></td> |
|---|
| 2882 | <td style="vertical-align: top;"> <p>Superelevation |
|---|
| 2883 | factor for the vertical coordinate. </p> <p>For |
|---|
| 2884 | domains with unfavorable ratio between the vertical and |
|---|
| 2885 | the horizontal size |
|---|
| 2886 | (the vertical size is determined by <a href="#nz_do3d">nz_do3d</a>) |
|---|
| 2887 | a <span style="font-weight: bold;">superelevation</span> |
|---|
| 2888 | /= <span style="font-style: italic;">1.0</span> may |
|---|
| 2889 | be used. If e.g. the |
|---|
| 2890 | horizontal size is substantially larger |
|---|
| 2891 | than the vertical size, a <span style="font-weight: bold;">superelevation</span> |
|---|
| 2892 | much larger than <span style="font-style: italic;">1.0</span> |
|---|
| 2893 | should |
|---|
| 2894 | be used, since otherwise the domain appears as a |
|---|
| 2895 | "flat disk" in the visualization and thus the vertical direction is |
|---|
| 2896 | only very poorly resolved.</p> </td> </tr> <tr> |
|---|
| 2897 | <td style="vertical-align: top;"> <p><a name="superelevation_x"></a><b>superelevation_x</b></p> |
|---|
| 2898 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 2899 | <td style="vertical-align: top; font-style: italic;">1.0<br> |
|---|
| 2900 | </td> <td style="vertical-align: top;"> <p>Superelevation |
|---|
| 2901 | factor for the horizontal (x) coordinate. </p> <p>This |
|---|
| 2902 | parameter can be used to stretch the displayed domain |
|---|
| 2903 | along the x-direction. See also <a href="#superelevation">superelevation</a>.</p> |
|---|
| 2904 | </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="superelevation_y"></a><b>superelevation_y</b></p> |
|---|
| 2905 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 2906 | <td style="vertical-align: top; font-style: italic;">1.0<br> |
|---|
| 2907 | </td> <td style="vertical-align: top;">Superelevation |
|---|
| 2908 | factor for the |
|---|
| 2909 | horizontal (y) coordinate. <p>This parameter can be |
|---|
| 2910 | used to |
|---|
| 2911 | stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p> </td> |
|---|
| 2912 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2913 | <p><a name="threshold"></a><b>threshold</b></p> |
|---|
| 2914 | </td> <td style="vertical-align: top;">R(10)<br> |
|---|
| 2915 | </td> <td style="vertical-align: top; font-style: italic;">0.0<br> |
|---|
| 2916 | </td> <td style="vertical-align: top;"> <p>Threshold |
|---|
| 2917 | value for which an isosurface is to be created by |
|---|
| 2918 | the <span style="font-weight: bold;">dvrp</span> |
|---|
| 2919 | software. </p> <p>If the creation of |
|---|
| 2920 | isosurfaces is switched on via |
|---|
| 2921 | parameter <a href="#mode_dvrp">mode_dvrp</a>, |
|---|
| 2922 | then the respective threshold value for which the isosurface is to be |
|---|
| 2923 | created can be assigned via <b>threshold</b>. If several |
|---|
| 2924 | isosurfaces |
|---|
| 2925 | are given by <b>mode_dvrp</b>, then an individual |
|---|
| 2926 | threshold value for |
|---|
| 2927 | each isosurface can be assigned. The order of the threshold values |
|---|
| 2928 | refers to the order of the isosurfaces given by <b>mode_dvrp</b>.</p> |
|---|
| 2929 | </td> </tr> </tbody> |
|---|
| 2930 | </table><span style="font-weight: bold;"><span style="font-weight: bold;"><br> |
|---|
| 2931 | </span></span><span style="font-weight: bold;"><span style="font-weight: bold;">Package (<span style="font-weight: bold;">mrun</span> |
|---|
| 2932 | option -p): <span style="font-weight: bold;"><a name="spectra"></a>spectra</span> |
|---|
| 2933 | NAMELIST group name: <span style="font-weight: bold;">spectra_par<br> |
|---|
| 2934 | <br></span></span></span> |
|---|
| 2935 | <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr> |
|---|
| 2936 | <td style="vertical-align: top;"><font size="4"><b>Parameter |
|---|
| 2937 | name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td> |
|---|
| 2938 | <td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td> |
|---|
| 2939 | <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td> |
|---|
| 2940 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 2941 | <p><a name="averaging_interval_sp"></a><b>averaging_interval_sp</b></p> |
|---|
| 2942 | </td> <td style="vertical-align: top;">R<br> </td> |
|---|
| 2943 | <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br> |
|---|
| 2944 | interval</a></span> </td> <td style="vertical-align: top;"> <p>Averaging interval |
|---|
| 2945 | for spectra output to local |
|---|
| 2946 | file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a> |
|---|
| 2947 | </font></font>and/or <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a> |
|---|
| 2948 | / <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a> |
|---|
| 2949 | (in s). </p> <p>If |
|---|
| 2950 | this parameter is given a non-zero value, temporally |
|---|
| 2951 | averaged spectra data are output. By default, spectra data data are not |
|---|
| 2952 | subject to temporal averaging. The interval length is limited by the |
|---|
| 2953 | parameter <a href="#dt_dosp">dt_dosp</a>. In any |
|---|
| 2954 | case <b>averaging_interval_sp</b> <= <b>dt_dosp |
|---|
| 2955 | </b>must |
|---|
| 2956 | hold.</p>If an interval is defined, then by default the average |
|---|
| 2957 | is calculated |
|---|
| 2958 | from the data values of all timesteps lying within this interval. The |
|---|
| 2959 | number of time levels entering into the average can be reduced with the |
|---|
| 2960 | parameter <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>. |
|---|
| 2961 | <p>If |
|---|
| 2962 | an averaging interval can not be completed at the end of a run, it will |
|---|
| 2963 | be finished at the beginning of the next restart run. Thus for restart |
|---|
| 2964 | runs, averaging intervals do not |
|---|
| 2965 | necessarily begin at the beginning of the run.</p></td> </tr> |
|---|
| 2966 | <tr> <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td> |
|---|
| 2967 | <td style="vertical-align: top;">I(10)</td> <td style="vertical-align: top;"><i>no level</i></td> |
|---|
| 2968 | <td style="vertical-align: top;"> <p>Vertical level |
|---|
| 2969 | for which horizontal spectra are to be |
|---|
| 2970 | calculated and output (gridpoints).<br> </p> <br> |
|---|
| 2971 | Spectra can be calculated for up to ten levels.</td> </tr> |
|---|
| 2972 | <tr><td style="vertical-align: top;"><p><a name="data_output_sp"></a><b>data_output_sp</b></p></td><td style="vertical-align: top;">C*10 (10)</td><td style="vertical-align: top;"><i>10 * ' '</i></td><td style="vertical-align: top;"><p>Quantities for which |
|---|
| 2973 | horizontal spectra are to be calculated |
|---|
| 2974 | and output.</p> <p>Allowed values are: <b>data_output_sp</b> |
|---|
| 2975 | = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>, <span style="font-style: italic;">'w'</span>, <span style="font-style: italic;">'pt'</span>, <span style="font-style: italic;">'q'</span>.<br> </p> |
|---|
| 2976 | <p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p> |
|---|
| 2977 | <p>By default spectra data are output to the local file <a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>. |
|---|
| 2978 | The file's format is NetCDF. Further details about processing |
|---|
| 2979 | NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>The |
|---|
| 2980 | temporal interval of the output times of profiles is |
|---|
| 2981 | assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>. </p><p>The |
|---|
| 2982 | vertical levels for which spectra are to be computed and output must be |
|---|
| 2983 | given by parameter <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>. |
|---|
| 2984 | </p><span style="font-weight: bold;">Note:</span><br> |
|---|
| 2985 | Beside <span style="font-weight: bold;">data_output_sp</span>, |
|---|
| 2986 | values <span style="font-weight: bold;">must</span> |
|---|
| 2987 | be given for each of the |
|---|
| 2988 | parameters, <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>, |
|---|
| 2989 | and <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a></font>, |
|---|
| 2990 | otherwise <span style="font-weight: bold;">no</span> |
|---|
| 2991 | output will be |
|---|
| 2992 | created!<br><br><br> |
|---|
| 2993 | Calculation of spectra requires cyclic boundary conditions |
|---|
| 2994 | along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a> |
|---|
| 2995 | and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For |
|---|
| 2996 | historical reasons, data can also be output in ASCII-format on local |
|---|
| 2997 | files <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a> |
|---|
| 2998 | and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a> |
|---|
| 2999 | (depending on the direction(s) along which spectra are to be |
|---|
| 3000 | calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font> |
|---|
| 3001 | which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See |
|---|
| 3002 | parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a> |
|---|
| 3003 | for defining the format in which data shall be output. Within |
|---|
| 3004 | these file, the spectra are ordered with respect to their |
|---|
| 3005 | output times. Spectra can also be temporally averaged (see <a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a> |
|---|
| 3006 | ). <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a |
|---|
| 3007 | spectrum is output in a single line (1st column: |
|---|
| 3008 | wavenumber, 2nd column: spectral coefficient). If spectra are to be |
|---|
| 3009 | calculated and output for more than one height (see </font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font><font>), |
|---|
| 3010 | the spectral coefficients for the further heighs can be found in the |
|---|
| 3011 | subsequent columns. </font>The order |
|---|
| 3012 | of the data in the file follows the order used in the assignment for <b>data_output_sp</b> |
|---|
| 3013 | (<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,… |
|---|
| 3014 | means that the file starts with the spectra of the u-component, |
|---|
| 3015 | followed by the v-component spectra, etc.). Additional to the files |
|---|
| 3016 | PLOTSP_X_DATA and PLOTSP_Y_DATA which contain |
|---|
| 3017 | the data, |
|---|
| 3018 | PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a> |
|---|
| 3019 | and <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_Y_PAR</a>) |
|---|
| 3020 | which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>. |
|---|
| 3021 | Spectra can be directly plotted with <span style="font-weight: bold;">profil</span> |
|---|
| 3022 | using the data and the corresponding parameter file. The |
|---|
| 3023 | plot layout is |
|---|
| 3024 | steered via the parameter input file. The vertical levels for which |
|---|
| 3025 | spectra are to be plotted must be given by <font><a href="chapter_4.2.html#plot_spectra_level"><span lang="en-GB"><font face="Thorndale">plot_spectra_level</font></span></a></font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"></span></a></font>. <span style="font-weight: bold;"></span>Otherwise, no |
|---|
| 3026 | spectra |
|---|
| 3027 | will appear on the plot, although data are available on file. All |
|---|
| 3028 | parameter values can be changed by editing the parameter |
|---|
| 3029 | input |
|---|
| 3030 | file.<span style="font-weight: bold;"><br></span></td></tr><tr> |
|---|
| 3031 | <td style="vertical-align: top;"> <p><a name="dt_dosp"></a><b>dt_dosp</b></p> |
|---|
| 3032 | </td> <td style="vertical-align: top;">R</td> |
|---|
| 3033 | <td style="vertical-align: top;"><i>value of |
|---|
| 3034 | <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td> |
|---|
| 3035 | <td style="vertical-align: top;"> <p>Temporal |
|---|
| 3036 | interval at which spectra data shall be output |
|---|
| 3037 | (in s). </p> <p><span lang="en-GB"><font face="Thorndale">If output of |
|---|
| 3038 | horizontal spectra is switched on (see </font></span><a href="#data_output_sp"><span lang="en-GB"><font face="Thorndale">data_output_sp</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this |
|---|
| 3039 | parameter can be used to |
|---|
| 3040 | assign the temporal interval at which spectral data shall be |
|---|
| 3041 | output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a |
|---|
| 3042 | simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>, |
|---|
| 3043 | which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference |
|---|
| 3044 | time is the beginning of |
|---|
| 3045 | the simulation, i.e. output takes place at times t = <span style="font-weight: bold;">skip_time_dosp</span> + <b>dt_dosp</b>, |
|---|
| 3046 | <span style="font-weight: bold;">skip_time_dosp</span> |
|---|
| 3047 | + 2*<b>dt_dosp</b>, skip_time_dosp + 3*<b>dt_dosp</b>, |
|---|
| 3048 | etc. The actual output times can |
|---|
| 3049 | deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). |
|---|
| 3050 | If <b>dt_dosp</b> < </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then |
|---|
| 3051 | spectral data are output |
|---|
| 3052 | after each time step (if this is requested it should be <b>dt_dosp</b> |
|---|
| 3053 | = <i>0</i>).</font></span> </p> </td> |
|---|
| 3054 | </tr> <tr> <td style="vertical-align: top;"> |
|---|
| 3055 | <p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p> |
|---|
| 3056 | </td> <td style="vertical-align: top;">I(10)</td> |
|---|
| 3057 | <td style="vertical-align: top;"><i>no level</i></td> |
|---|
| 3058 | <td style="vertical-align: top;"> <p>Vertical |
|---|
| 3059 | level(s) for which horizontal spectra are to be |
|---|
| 3060 | plotted (in gridpoints). </p> <p>This parameter |
|---|
| 3061 | only affects the display of spectra in plots |
|---|
| 3062 | created with <span style="font-weight: bold;">profil</span>. |
|---|
| 3063 | The |
|---|
| 3064 | spectral data created and output to file are exclusively determined via |
|---|
| 3065 | <font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p> |
|---|
| 3066 | </td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td> |
|---|
| 3067 | <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span> |
|---|
| 3068 | </td> <td style="vertical-align: top;">No output of |
|---|
| 3069 | spectra data before this interval has passed (in s).<br><br>This |
|---|
| 3070 | parameter causes that data output activities are starting not before |
|---|
| 3071 | this interval |
|---|
| 3072 | (counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If |
|---|
| 3073 | the user has set <a href="#dt_dosp">dt_dosp</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dosp</span> = <span style="font-style: italic;">1800.0</span>, then the |
|---|
| 3074 | first output will be done at t = 5400 s. </td> </tr> |
|---|
| 3075 | <tr> <td style="vertical-align: top;"> <p><a name="spectra_direction"></a><b>spectra_direction</b></p> |
|---|
| 3076 | </td> <td style="vertical-align: top;">C*2 (10)</td> |
|---|
| 3077 | <td style="vertical-align: top;"><i>10 * ' '</i></td> |
|---|
| 3078 | <td style="vertical-align: top;"> <p>Direction(s) |
|---|
| 3079 | along which spectra are to be calculated. </p> <p>Allowed |
|---|
| 3080 | values are <span style="font-style: italic;">'x'</span>, |
|---|
| 3081 | <span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For |
|---|
| 3082 | every quantity given by <a href="#data_output_sp">data_output_sp</a> |
|---|
| 3083 | a corresponding |
|---|
| 3084 | direction<span style="font-weight: bold;"> </span>must |
|---|
| 3085 | be assigned.<br> </p> <p>Calculation of spectra |
|---|
| 3086 | requires cyclic boundary conditions |
|---|
| 3087 | along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a> |
|---|
| 3088 | and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</p> |
|---|
| 3089 | </td> </tr> </tbody> |
|---|
| 3090 | </table><span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br> |
|---|
| 3091 | </span></span></span><h3 style="line-height: 100%;"><br> |
|---|
| 3092 | <a href="chapter_4.1.html"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></a><a href="index.html"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></a><a href="chapter_4.3.html"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></a></h3><span style="font-style: italic;">Last change:</span> |
|---|
| 3093 | 22/08/06 (SR)<span style="font-weight: bold;"><span style="font-weight: bold;"><br> |
|---|
| 3094 | </span></span><br> |
|---|
| 3095 | </body></html> |
|---|
