Changes between Version 123 and Version 124 of doc/app/runtime_parameters

Timestamp:

Sep 15, 2010 11:54:18 AM (15 years ago)

Author:

weinreis

Comment:

--

doc/app/runtime_parameters

@@ -101 +101 @@
 3d volume data output is always handled seperately by each processor so that {{{combine_plot_fields.x}}} has to be called anyway after PALM has been finished.\\\\
 '''Old formats:'''\\\\
-Beside the NetCDF format, 2d cross section data and 3d volume data can also be output, for historical reasons, in a different (binary) format using parameter [#data_output_format data_output_format].\\\\
+Beside the netCDF format, 2d cross section data and 3d volume data can also be output, for historical reasons, in a different (binary) format using parameter [#data_output_format data_output_format].\\\\
 By assigning '''data_output_format''' = '' 'avs' '', the 3d volume data is output to the local file [[../iofiles#PLOT3D_DATA|PLOT3D_DATA]]. Output is in FORTRAN binary format readable by the plot software '''AVS'''.  The order of data on the file follows the order used in the assignment for '''data_output''' (e.g. '''data_output''' = '' 'p', 'v',...'' means that the file starts with the pressure data, followed by the v-component of the velocity, etc.). Both instantaneous and time averaged data are written on this file! Additional to this file, PALM creates a second binary file (local name [[../iofiles#PLOT3D_COOR|PLOT3D_COOR]]) with coordinate information needed by '''AVS'''. As third and fourth file two ASCII files are created (AVS-FLD-format, local name [[../iofiles#PLOT3D_FLD|PLOT3D_FLD]] and [[../iofiles#PLOT3D_FLD_COOR|PLOT3D_FLD_COOR]]), which describe the contents of the data file and/or coordinate file and are used by '''AVS'''. However, '''AVS''' expects the content description in one file. This needs the local file PLOT3D_FLD_COOR to be appended to the file PLOT3D_FLD (by suitable OUTPUT command in the '''mrun''' configuration file: {{{“cat PLOT3D_FLD_COOR >> PLOT3D_FLD”}}}) after PALM has finished. To reduce the amount of data, output to this file can be done in compressed form (see [#do3d_compress do3d_compress]). Further details about plotting 3d volume data with '''AVS''' can be found in chapter [[4.5.5]].\\\\
 '''Important:'''\\
@@ -123 +123 @@
 For historical reasons, other data formats are still available. Beside 'netcdf', data_output_format may be assigned the following values:
 ||'' 'avs' '' ||output of 3d volume data in FORTRAN binary format to be read by the graphic software '''AVS''' (see chapter [[4.5.5]])||
-Multiple values can be assigned to '''data_output_format''', i.e. if the user wants to have both the "old" data format as well as cross section data in NetCDF format, then '''data_output_format''' = '' 'avs', 'netcdf' '' has to be assigned.\\\\
+Multiple values can be assigned to '''data_output_format''', i.e. if the user wants to have both the "old" data format as well as cross section data in netCDF format, then '''data_output_format''' = '' 'avs', 'netcdf' '' has to be assigned.\\\\
 '''Warning:''' There is no guarantee that the "old" formats will be available in future PALM versions (beyond 3.0)!
 }}}
@@ -605 +605 @@
 {{{#!td
 Temporal interval for which the precipitation amount (in mm) shall be calculated and output (in s).\\\\
-This parameter requires [#precipitation precipitation] = ''.TRUE.''. The interval must be smaller or equal than the output interval for 2d horizontal cross sections given by [#dt_do2d_xy dt_do2d_xy]). The output of the precipitation amount also requires setting of [#data_output data_output] = '' 'pra*'.''
+This parameter requires [#precipitation precipitation] = ''.T.''. The interval must be smaller or equal than the output interval for 2d horizontal cross sections given by [#dt_do2d_xy dt_do2d_xy]). The output of the precipitation amount also requires setting of [#data_output data_output] = '' 'pra*'.''
 }}}
 |----------------
@@ -793 +793 @@
 CPU time needed for terminal actions at the end of a run in batch mode (in s).\\\\
 If the environment variable '''write_binary''' is set ''.T.'' (see [[chapter 3.3]]), PALM checks the remaining CPU time of the job after each timestep. Time integration must not consume the CPU time completely, since several actions still have to be carried out after time integration has finished (e.g. writing of binary data for the restart run, carrying out output commands, copying of local files to their permanent destinations, etc.) which also takes some time. The maximum possible time needed for these activities plus a reserve is to be given with the parameter '''termination_time_needed'''. Among other things, it depends on the number of grid points used. If its value is selected too small, then the respective job will be prematurely aborted by the queuing system, which may result in a data loss and will possibly interrupt the job chain.\\\\
-An abort happens in any way, if the environment variable '''write_binary''' is not set to true and if moreover the job has been assigned an insufficient CPU time by '''mrun''' option {{{-t}}}.\\\\
+An abort happens in any way, if the environment variable '''write_binary''' is not set to ''true'' and if moreover the job has been assigned an insufficient CPU time by '''mrun''' option {{{-t}}}.\\\\
 '''Note:'''\\
 On the IBM computers of the HLRN the time used by the job '''before''' the start of PALM have also to be accounted for (e.g. for compilation and copying of input files).
@@ -995 +995 @@
 {{{#!td
 '''Currently this parameter cannot be used.'''\\\\
-Height level up to which 2d cross sections are to be plotted with iso2d (in m).\\\\
+Height level up to which 2d cross sections are to be plotted with '''iso2d''' (in m).\\\\
 This parameter only applies for [#data_output_format data_output_format] = '' 'iso2d'.''\\\\
 It affects plots of  2d vertical cross sections ([#data_output data_output]) when plotted with '''iso2d'''. By default, vertical sections are plotted up to the top boundary. In contrast, with '''z_max_do2d''' the visualization within the plot can be limited to a certain height level (0 <= z <= '''z_max_do2d'''). Nevertheless, '''all''' grid points of the complete cross section are still output to the local files PLOT2D_XZ or PLOT2D_YZ. The level up to which the section is visualized can later be changed by manually editing the file PLOT2D_XZ_GLOBAL or PLOT2D_YZ_GLOBAL (the respective '''iso2d'''-parameter is '''yright''').