Changes between Version 89 and Version 90 of doc/app/particle_parameters

Timestamp:

Sep 13, 2010 3:45:27 PM (14 years ago)

Author:

suehring

Comment:

--

doc/app/particle_parameters

@@ -24 +24 @@
 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 [../iofile#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 [../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 [../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].\\\\
+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].\\\\
 '''So far, the particle transport realized in PALM does only work duly in case of a constant vertical grid spacing! '''
 }}}
@@ -35 +35 @@
 }}}
 {{{#!td style="vertical-align:top"
-reflect
+'reflect'
 }}}
 {{{#!td
 Bottom boundary condition for particle transport. \\
-By default, particles are reflected at the bottom boundary. Alternatively, a particle absorption can set by '''bc_par_b''' = '' 'absorb' ''.
+By default, particles are reflected at the bottom boundary. Alternatively, a particle absorption can set by '''bc_par_b''' = '' 'absorb'. ''
 }}}
 |----------------
@@ -49 +49 @@
 }}}
 {{{#!td style="vertical-align:top"
-cyclic
+'cyclic'
 }}}
 {{{#!td
@@ -64 +64 @@
 }}}
 {{{#!td style="vertical-align:top"
-cyclic
+'cyclic'
 }}}
 {{{#!td
@@ -79 +79 @@
 }}}
 {{{#!td style="vertical-align:top"
-absorb
+'absorb'
 }}}
 {{{#!td
 Top boundary condition for particle transport.\\
-By default, particles are absorbed at the top boundary. Alternatively, a reflection condition can be set by '''bc_par_t''' = '' 'reflect' ''.
+By default, particles are absorbed at the top boundary. Alternatively, a reflection condition can be set by '''bc_par_t''' = '' 'reflect'. ''
 }}}
 |----------------
@@ -112 +112 @@
 }}}
 {{{#!td style="vertical-align:top"
-value of [../d3par#dt_data_output #]
+value of [../d3par#dt_data_output dt_data] \\ [../d3par#dt_data_output _output] 
 }}}
 {{{#!td