Changes between Version 21 and Version 22 of doc/app/iofiles

Timestamp:

Sep 14, 2010 11:08:54 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -649 +649 @@
 }}}
 |----------------
+{{{#!td style="vertical-align:top; width: 50px"
+80
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PARTICLE_INFOS PARTICLE_INFOS/] \\
+[=#PARTICLE_INFOS_O PARTICLE_INFOS_O/]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+ASCII
+}}}
+{{{#!td
+This file is created in case of particle transport (see the [../parpar particles package]). It contains statistical informations about the number of particles used and about the number of particles exchanged between each single PE. These informations are output after every timestep if switched on by parameter {../parpar#write_particle_statistics write_particle_statistics]. 
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
+85
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PARTICLE_DATA PARTICLE_DATA/] \\
+[=#PARTICLE_DATA_O PARTICLE_DATA_O/]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+Binary
+}}}
+{{{#!td
+This file is created if particle transport is switched on (see the [../parpar particles package]) and contains all particle data for one or several output times (see [../parpar#dt_write_particle_data dt_write_particle_data]). \\\\
+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 informations (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.
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
+90
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PARTICLE_RESTART_DATA_IN PARTICLE_RESTART_DATA_IN/]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+I
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+Binary
+}}}
+{{{#!td
+Binary data, which are read in by the model at the beginning of a restart run (see [wiki:chapter_33 chapter 3.3]). The appropriate file must have been written by the preceding job of the job chain (see [#PARTICLE_RESTART_DATA_OUT PARTICLE_RESTART_DATA_OUT]). This file is needed if particle transport is switched on (see the [../parpar particles package]) and contains all particle informations (particle positions, velocities, etc.) from the end of the preceding run. Concerning runs on several processors it has to be noted that each processing element reads its own file and that the file content is processor-dependent. The number of processors which can be used must not be changed during a job chain and/or if a job chain is continued. \\\\
+The first record of this file contains a version number (four character string) of the subroutine, which output the data that follows ({{{write_particles}}}, see end of file {{{advec_particles.f90}}}). This number has to agree with the version number of the subroutine which is reading the file ({{{init_parrticles.f90}}}) in case of a restart run. Otherwise the model run is aborted. Version numbers are changed whenever new code revisions require a change of the file format. Some general informations like the number of particles stored in the file, the number of particle groups, etc. are stored in the second record. The third record includes the particles to be released at the source and the fourth record contains all current particles. In case that particle tails are used (see [../parpar#maximum_number_of_tailpoints maximum_number_of_tailpoints]), a further record may follow, which contains the particle tail informations. A FORTRAN TYPE structure is used for storing the particle attributes. For detailed informations about the file format see the corresponding READ statements in file {{{init_particles.f90}}}. 
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
+90
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PARTICLE_RESTART_DATA_OUT PARTICLE_RESTART_DATA_OUT/]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+Binary
+}}}
+{{{#!td
+Binary data, which are output at the end of the run and possibly needed by restart runs (see [wiki:chapter_33 chapter 3.3]) for the initialization. This output file is then read as file [#PARTICLE_RESTART_DATA_IN PARTICLE_RESTART_DATA_IN]. The file is only written if particle transport is switched on (see the [../parpar particles package]). For a more detailed description of the file structure see PARTICLE_RESTART_DATA_IN.
+}}}
+|----------------