Changes between Version 3 and Version 4 of doc/app/particle_parameters

Timestamp:

Sep 13, 2010 10:01:38 AM (14 years ago)

Author:

suehring

Comment:

--

doc/app/particle_parameters

@@ -21 +21 @@
 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. \\\\
 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].\\\\
-Timeseries of particle quantities in NetCDF format can be output to local file [#DATA_1D_PTS_NETCDF DATA_1D_PTS_NETCDF] by using package parameter [#dt_dopts dt_dopts].\\\\
-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 [#PARTICLE_DATA PARTICLE_DATA]).\\\\
+Timeseries of particle quantities in NetCDF format can be output to local file [../iofile#DATA_1D_PTS_NETCDF DATA_1D_PTS_NETCDF] by using package parameter [#dt_dopts dt_dopts].\\\\
+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 [../iofile#PARTICLE_DATA PARTICLE_DATA]).\\\\
 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 [#PARTICLE_INFOS PARTICLE_INFOS], if switched on by the parameter [#write_particle_statistics write_particle_statistics]. \\\\
-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 [#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 [#PARTICLE_RESTART_DATA_IN PARTICLE_RESTART_DATA_IN] using respective file connection statements in the '''mrun''' configuration file. \\\\
+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 [../iofile#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 [../iofile#PARTICLE_RESTART_DATA_IN PARTICLE_RESTART_DATA_IN] using respective file connection statements in the '''mrun''' configuration file. \\\\
 The output of particles for visualization with the graphic software '''dvrp''' is steered by the package parameter dt_dvrp. For visualization purposes particles can be given a diameter using the parameters dvrp_psize and 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.\\\\
 '''So far, the particle transport realized in PALM does only work duly in case of a constant vertical grid spacing!'''