| 761 | | The first record of this file contains an identification string (PALM version number, run identifier, etc., 80 characters long). The second record also contains a version string (80 characters long) followed by two records with particle group information (see file {{{check_open.f90}}}). Then, for each output time, two records follow, where the first one gives some general information (numbers of particles, etc.) and the second one contains the actual particle data. A FORTRAN TYPE structure is used for storing the particle attributes. See file {{{advec_particles.f90}}} for the detailed format. |
| | 761 | The first record of this file contains an identification string (PALM version number, run identifier, etc., 80 characters long). The second record also contains a version string (80 characters long) followed by two records with particle group information and a record containing the index bounds of the 3d subdomain arrays (see [source:palm/trunk/SOURCE/check_open.f90@4182#L553]). Then, for each output time, two records follow, where the first one gives the output time and the second one the number of particles that are output for the subdomain. After that, particle data is output, one record for each model grid box (if particles exist in that box) of the respective subdomain. See [source:palm/trunk/SOURCE/lagrangian_particle_model_mod.f90@4182#L2364] for the respective output statements. A FORTRAN TYPE structure is used for storing the particle attributes. See [source:palm/trunk/SOURCE/mod_particle_attributes.f90@4182#L77] for the detailed TYPE structure. |
