| 19 | | }}} |
| 20 | | |---------------- |
| 21 | | {{{#!td style="vertical-align:top" |
| 22 | | [=#dt_prel '''dt_prel'''] |
| 23 | | }}} |
| 24 | | {{{#!td style="vertical-align:top" |
| 25 | | R |
| 26 | | }}} |
| 27 | | {{{#!td style="vertical-align:top" |
| 28 | | 9999999.9 |
| 29 | | }}} |
| 30 | | {{{#!td |
| 31 | | Temporal interval at which particles are to be released from a particle source (in s).\\ |
| 32 | | By default particles are released only at the beginning of a simulation (t_init=0). The time of the first release (t_init) can be changed with package parameter [#particle_advection_start particle_advection_start]. The time of the last release can be set with the package parameter [#end_time_prel end_time_prel]. If '''dt_prel''' has been set, additional releases will be at ''t = t_init+'''dt_prel''', t_init+2*'''dt_prel''', t_init+3*'''dt_prel''', etc..'' Actual release times may slightly deviate from thesel values (see e.g. [../d3par#dt_dopr dt_dopr]).\\\\ |
| 33 | | The domain of the particle source as well as the distance of released particles within this source are determined via package parameters [#pst pst], [#psl psl], [#psr psr], [#pss pss], [#psn psn], [#psb psb], [#pdx pdx], [#pdy pdy] and [#pdz pdz]. By default, one particle is released at all points defined by these parameters. The package parameter [#particles_per_point particles_per_point] can be used to start more than one particle per point.\\\\ |
| 34 | | Up to 10 different groups of particles can be released at the same time (see [#number_of_particle_groups number_of_particle_groups]) where each group may have a different source. All particles belonging to one group have the same density ratio and the same radius. All other particle features (e.g. location of the source) are identical for all groups of particles.\\\\ |
| 35 | | Subgrid scale velocities can (optionally) be included for calculating the particle advection, using the method of Weil et al. (2004, JAS, 61, 2877-2887). This method is switched on by the package parameter [#use_sgs_for_particles use_sgs_for_particles]. This also forces the Euler/upstream method to be used for time advancement of the TKE (see initialization parameter [../inipar#use_upstream_for_tke use_upstream_for_tke]). The minimum timestep during the sub-timesteps is controlled by package parameter [#dt_min_part dt_min_part]. \\\\ |
| 36 | | By default, particles are weightless and transported passively with the resolved scale flow. Particles can be given a mass and thus an inertia by assigning the package parameter density_ratio a non-zero value (it defines the ratio of the density of the fluid and the density of the particles). In these cases their radius must also be defined, which affects their flow resistance. \\\\ |
| 37 | | Boundary conditions for the particle transport can be defined with package parameters [#bc_par_t bc_par_t], [#bc_par_lr bc_par_lr], [#bc_par_ns bc_par_ns] and [#bc_par_b bc_par_b].\\\\ |
| 38 | | Timeseries of particle quantities in netCDF format can be output to local file [../iofiles#DATA_1D_PTS_NETCDF DATA_1D_PTS_NETCDF] by using package parameter [#dt_dopts dt_dopts].\\\\ |
| 39 | | For analysis, additional output of particle information in equidistant temporal intervals can be carried out using [#dt_write_particle_data dt_write_particle_data] (file [../iofiles#PARTICLE_DATA PARTICLE_DATA]).\\\\ |
| 40 | | Statistical informations (e.g. the total number of particles used, the number of particles exchanged between the PEs, etc.) are output to the local file [../iofiles#PARTICLE_INFOS PARTICLE_INFOS], if switched on by the parameter [#write_particle_statistics write_particle_statistics]. \\\\ |
| 41 | | If a job chain is to be carried out, particle informations for the restart run (e.g. current location of all particles at the end of the run) is output to the local file [../iofiles#PARTICLE_RESTART_DATA_OUT PARTICLE_RESTART_DATA_OUT], which must be saved at the end of the run and given as an input file to the restart run under local file name [../iofiles#PARTICLE_RESTART_DATA_IN PARTICLE_RESTART_DATA_IN] using respective file connection statements in the '''mrun''' configuration file. \\\\ |
| 42 | | The output of particles for visualization with the graphic software '''dvrp''' is steered by the package parameter [../dvrpar#dt_dvrp dt_dvrp]. For visualization purposes particles can be given a diameter using the parameters [../dvrpar#dvrp_psize dvrp_psize] and [../dvrpar#particle_dvrpsize particle_dvrpsize] (this diameter only affects the visualization). All particles have the same size. Alternatively, particles can be given an individual size and a color by modifying the user-interface (subroutine {{{user_init_particles}}}). Particles can pull a ''tail'' behind themselves to improve their visualization. This is steered via the parameter [#use_particle_tails use_particle_tails].\\\\ |
| 43 | | '''So far, the particle transport realized in PALM does only work duly in case of a constant vertical grid spacing! ''' |
| | 208 | [=#dt_prel '''dt_prel'''] |
| | 209 | }}} |
| | 210 | {{{#!td style="vertical-align:top" |
| | 211 | R |
| | 212 | }}} |
| | 213 | {{{#!td style="vertical-align:top" |
| | 214 | 9999999.9 |
| | 215 | }}} |
| | 216 | {{{#!td |
| | 217 | Temporal interval at which particles are to be released from a particle source (in s).\\ |
| | 218 | By default particles are released only at the beginning of a simulation (t_init=0). The time of the first release (t_init) can be changed with package parameter [#particle_advection_start particle_advection_start]. The time of the last release can be set with the package parameter [#end_time_prel end_time_prel]. If '''dt_prel''' has been set, additional releases will be at ''t = t_init+'''dt_prel''', t_init+2*'''dt_prel''', t_init+3*'''dt_prel''', etc..'' Actual release times may slightly deviate from thesel values (see e.g. [../d3par#dt_dopr dt_dopr]).\\\\ |
| | 219 | The domain of the particle source as well as the distance of released particles within this source are determined via package parameters [#pst pst], [#psl psl], [#psr psr], [#pss pss], [#psn psn], [#psb psb], [#pdx pdx], [#pdy pdy] and [#pdz pdz]. By default, one particle is released at all points defined by these parameters. The package parameter [#particles_per_point particles_per_point] can be used to start more than one particle per point.\\\\ |
| | 220 | Up to 10 different groups of particles can be released at the same time (see [#number_of_particle_groups number_of_particle_groups]) where each group may have a different source. All particles belonging to one group have the same density ratio and the same radius. All other particle features (e.g. location of the source) are identical for all groups of particles.\\\\ |
| | 221 | Subgrid scale velocities can (optionally) be included for calculating the particle advection, using the method of Weil et al. (2004, JAS, 61, 2877-2887). This method is switched on by the package parameter [#use_sgs_for_particles use_sgs_for_particles]. This also forces the Euler/upstream method to be used for time advancement of the TKE (see initialization parameter [../inipar#use_upstream_for_tke use_upstream_for_tke]). The minimum timestep during the sub-timesteps is controlled by package parameter [#dt_min_part dt_min_part]. \\\\ |
| | 222 | By default, particles are weightless and transported passively with the resolved scale flow. Particles can be given a mass and thus an inertia by assigning the package parameter density_ratio a non-zero value (it defines the ratio of the density of the fluid and the density of the particles). In these cases their radius must also be defined, which affects their flow resistance. \\\\ |
| | 223 | Boundary conditions for the particle transport can be defined with package parameters [#bc_par_t bc_par_t], [#bc_par_lr bc_par_lr], [#bc_par_ns bc_par_ns] and [#bc_par_b bc_par_b].\\\\ |
| | 224 | Timeseries of particle quantities in netCDF format can be output to local file [../iofiles#DATA_1D_PTS_NETCDF DATA_1D_PTS_NETCDF] by using package parameter [#dt_dopts dt_dopts].\\\\ |
| | 225 | For analysis, additional output of particle information in equidistant temporal intervals can be carried out using [#dt_write_particle_data dt_write_particle_data] (file [../iofiles#PARTICLE_DATA PARTICLE_DATA]).\\\\ |
| | 226 | Statistical informations (e.g. the total number of particles used, the number of particles exchanged between the PEs, etc.) are output to the local file [../iofiles#PARTICLE_INFOS PARTICLE_INFOS], if switched on by the parameter [#write_particle_statistics write_particle_statistics]. \\\\ |
| | 227 | If a job chain is to be carried out, particle informations for the restart run (e.g. current location of all particles at the end of the run) is output to the local file [../iofiles#PARTICLE_RESTART_DATA_OUT PARTICLE_RESTART_DATA_OUT], which must be saved at the end of the run and given as an input file to the restart run under local file name [../iofiles#PARTICLE_RESTART_DATA_IN PARTICLE_RESTART_DATA_IN] using respective file connection statements in the '''mrun''' configuration file. \\\\ |
| | 228 | The output of particles for visualization with the graphic software '''dvrp''' is steered by the package parameter [../dvrpar#dt_dvrp dt_dvrp]. For visualization purposes particles can be given a diameter using the parameters [../dvrpar#dvrp_psize dvrp_psize] and [../dvrpar#particle_dvrpsize particle_dvrpsize] (this diameter only affects the visualization). All particles have the same size. Alternatively, particles can be given an individual size and a color by modifying the user-interface (subroutine {{{user_init_particles}}}). Particles can pull a ''tail'' behind themselves to improve their visualization. This is steered via the parameter [#use_particle_tails use_particle_tails].\\\\ |
| | 229 | '''So far, the particle transport realized in PALM does only work duly in case of a constant vertical grid spacing! ''' |
| | 230 | }}} |
| | 231 | |---------------- |
| | 232 | {{{#!td style="vertical-align:top" |
