| 812 | | Binary data, which are read in by the model at the beginning of a [../runs restart run]). 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 information (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. \\\\ |
| 813 | | 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 information 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 information. 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}}}. |
| | 812 | Binary data, which are read in by the model at the beginning of a [../runs restart run]). 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 [../particle_parameters particles package]) and contains all particle information (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. \\\\ |
| | 813 | 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 information 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 [../particle_parameters#maximum_number_of_tailpoints maximum_number_of_tailpoints]), a further record may follow, which contains the particle tail information. 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}}}. |
| 1195 | | This file contains data of the time series of particle quantities (see [../parpar#dt_prel dt_prel]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). For a list of available output quantities see [../parpar#dt_dopts dt_dopts]. \\\\ |
| 1196 | | In case of using more than one particle group (see [../parpar#number_of_particle_groups number_of_particle_groups]), separate time series are output for each of the groups. The long names of the variables in the netCDF file containing the respective time series all end with the string '' ' PG '' ## '' ' '', where ## is the number of the particle group (01, 02, etc.). \\\\ |
| | 1195 | This file contains data of the time series of particle quantities (see [../particle_parameters#dt_prel dt_prel]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). For a list of available output quantities see [../particle_parameters#dt_dopts dt_dopts]. \\\\ |
| | 1196 | In case of using more than one particle group (see [../particle_parameters#number_of_particle_groups number_of_particle_groups]), separate time series are output for each of the groups. The long names of the variables in the netCDF file containing the respective time series all end with the string '' ' PG '' ## '' ' '', where ## is the number of the particle group (01, 02, etc.). \\\\ |
