| 176 | |---------------- |
| 177 | {{{#!td style="vertical-align:top; text-align:left;width: 150px" |
| 178 | Middle of {{{advec_particles.f90}}}, after particle reflection from walls. |
| 179 | }}} |
| 180 | {{{#!td style="vertical-align:top; text-align:left;style="width: 50px" |
| 181 | [=#user_advec_particles {{{user_advec_particles}}}] |
| 182 | }}} |
| 183 | {{{#!td |
| 184 | User-defined actions after the calculation of the new particle position. |
| 185 | }}} |
| 186 | |---------------- |
| 187 | {{{#!td style="vertical-align:top; text-align:left;width: 150px" |
| 188 | End of {{{check_parameters.f90}}} where 2d/3d output quantities are checked |
| 189 | }}} |
| 190 | {{{#!td style="vertical-align:top; text-align:left;style="width: 50px" |
| 191 | [=#user_check_data_output {{{user_check_data_output}}}]\\{{{( variable, unit )}}} |
| 192 | }}} |
| 193 | {{{#!td |
| 194 | Here the physical unit(s) of user-defined 2d/3d output quantities (see [../../userpar#data_output_user data_output_user) have to be set. Input parameter {{{variable}}} contains the string identifier of the respective variable. For those variables not recognized by the user, the parameter {{{unit}}} is set to ''illegal'', which tells the calling routine that the output variable is not defined and leads to a program abort.\\ |
| 195 | See [wiki:chapter_354 chapter 3.5.4] about creating user-defined output quantities. |
| 196 | }}} |