Changes between Version 63 and Version 64 of doc/app/iofiles

Timestamp:

Sep 20, 2010 11:40:55 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -572 +572 @@
 Information about the selected model parameters (physical and numerical values) as well as general information about the run. \\\\
 This file contains the values of all important steering parameters (numerical procedures, computing grid and model dimensions, boundary conditions, physical dimension, turbulence quantities, actions during the simulation, 1D-model-parameters) as well as data concerning the selected plot and list outputs. The headlines of the file list the program version used, date and time of the beginning of the run, the name of the executing computer, the run identifier (corresponds to the selected base file name) and the number of the run (number of the restart run). With parallel runs the number of processors as well as the assigned virtual processor net also appear. After these headlines run time and time step information appear (point of starting time, related to t=0 of the initial run, end-time, time actually reached, CPU time, etc.). If a model run is incorrectly terminated (e.g. run time error or excess of the permitted CPU time), information over the time reached and the necessary CPU time is missing (to understand: the file HEADER is written twice by the model; once briefly after beginning of the simulation (naturally here the information over the time reached is missing etc.) and then briefly before the normal end of the simulation. The second, now complete output overwrites the first output.).  \\\\
-At the end of the file, information about the values of user parameters (see [wiki:chapter_37 chapter 3.7] and [wiki:chapter_43 chapter 4.3]) can be output by the user with the help of the subroutine {{{user_header}}} (located in the file {{{user_interface.f90}}}). If no user parameters were found, the string '' '!*** no user-defined variables found' '' appears at the end of the file. If user parameters were indicated, the string '' 'user-defined variables and actions' '' is printed, followed by informations about the user-defined subdomains for which profiles and time series are output. All further information to appear here, must be provided by the user (by appropriate WRITE statements in {{{user_header}}}).
+At the end of the file, information about the values of user parameters (see [../packages Optional software packages] and [../userint/userpar user-defined parameters]) can be output by the user with the help of the subroutine {{{user_header}}} (located in the file {{{user_interface.f90}}}). If no user parameters were found, the string '' '!*** no user-defined variables found' '' appears at the end of the file. If user parameters were indicated, the string '' 'user-defined variables and actions' '' is printed, followed by informations about the user-defined subdomains for which profiles and time series are output. All further information to appear here, must be provided by the user (by appropriate WRITE statements in {{{user_header}}}).
 }}}
 |----------------
@@ -647 +647 @@
 With parallel runs each processing element writes the data of its subdomain to a separate file with the name PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable for AVS, but after the end of the model run they can be combined to one file readable for AVS with the help of the program {{{combine_plot_fields.x}}} (automatically activated by '''mrun'''). This tool expects the files of the individual processing elements under the names described above and outputs the combined file into a new file PLOT3D_DATA.
 The tool writes informative messages about the accomplished actions into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} also possibly existing files with two-dimensional plot data (see e.g. [#PLOT2D_XY PLOT2D_XY]) are combined. \\\\   
-With parallel runs the output of data of large volume is also possible in compressed form. For this purpose the initialization parameter  [../d3par#do3d_compress do3d_compress] = ''.T.'' must be set and the desired output accuracy has to be indicated with the help of [../d3par#do3d_comp_prec do3d_comp_prec]. In favorable cases the file size can be reduced by a factor of up to 5. For the visualization of compressed data a special AVS module ({{{read_compressed_field}}}) and a further entry in the '''mrun'''-configuration file are needed. More details can be found in [wiki:chapter_456 chapter 4.5.6].
+With parallel runs the output of data of large volume is also possible in compressed form. For this purpose the initialization parameter  [../d3par#do3d_compress do3d_compress] = ''.T.'' must be set and the desired output accuracy has to be indicated with the help of [../d3par#do3d_comp_prec do3d_comp_prec]. In favorable cases the file size can be reduced by a factor of up to 5. For the visualization of compressed data a special AVS module ({{{read_compressed_field}}}) and a further entry in the '''mrun'''-configuration file are needed. More details can be found in the postprocessing description of [../avs AVS].
 }}}
 |----------------