Changes between Version 46 and Version 47 of doc/app/iofiles

Timestamp:

Sep 16, 2010 7:23:24 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -1 +1 @@
 == Input and output files ==
-The model works with a set of files, which are all located in the temporary working directory and which are either expected at the beginning of the run (the so-called input files) or which are produced during the run and/or at the end of the simulation (output files). The following table lists all default files addressed by the model. They are arranged according to the associated FORTRAN unit (unit number). The unit 90 is used for different files, which are opened only briefly and uniquely in the model and closed directly afterwards. Unit numbers 101 - 109, 111 - 113, and 116 refer to data files which have netCDF format. These are not opened by a FORTRAN-OPEN-statement but by a corresponding netCDF call (NF90_CREATE or NF90_OPEN). These files are only created on machines where a netCDF library is available. \\\\
+The model works with a set of files, which are all located in the temporary working directory and which are either expected at the beginning of the run (the so-called input files) or which are produced during the run and/or at the end of the simulation (output files). The following table lists all default files addressed by the model. They are arranged according to the associated FORTRAN unit (unit number). The unit 90 is used for different files, which are opened only briefly and uniquely in the model and closed directly afterwards. Unit numbers 101 - 109, 111 - 113, and 116 refer to data files which have netCDF format. These are not opened by a FORTRAN-OPEN-statement but by a corresponding netCDF call ({{{NF90_CREATE}}} or {{{NF90_OPEN}}}). These files are only created on machines where a netCDF library is available. \\\\
 The file names described in the list correspond to the names indicated in the respective OPEN instruction, i.e. the files are expected and saved under these names in the temporary working directory of the model. By default, file names are always written in capital letters. The third column indicates whether it is an input or output file (I and/or O). The netCDF files can be both input and output files (I/O). If restart jobs shall append data to an existing netCDF file (created by a previous job of the job chain), the respective file has to be given as an input file (see also [wiki:chapter451 chapter 4.5.1] which gives more details about the PALM-netCDF-output). \\\\
 On parallel computers many of the files are read and/or written by the central processing element 0 (PE0) only. These files have processor-independent content (and therefore they can be read or written by other PEs just as well). However, certain files have processor-dependent content. For the binary output of data for restart runs (local file [#BINOUT BINOUT]), for example, each PE outputs only the data of its subdomain. So each processing element writes into its own file with its own file name. These files lie in a subdirectory of the temporary working directory. Their names are build off from the underline ("_") and the four digit processor ID. The data written for restart runs would be e.g. on the files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc. Such files, which have processor-dependent content on parallel computers, are marked in the following list by the fact, that to the file name a line ("/") is attached. If appropriate output files are to be copied through '''mrun''' to permanent files, and/or files with processor-dependent content are supposed to be copied as input files into the temporary working directory of the model, you have to indicate a special file attribute in the appropriate file connection statement (see [wiki:arpe arpe], [wiki:flpe flpe] in the '''mrun''' description). Then the permanent file name will be interpreted as a directory name, in which the input files are expected and/or to which output files are written. The file names in these directories are always named _0000, _0001, _0002 etc. \\\\