Changes between Version 38 and Version 39 of doc/app/runtime_parameters


Ignore:
Timestamp:
Sep 13, 2010 3:11:59 PM (15 years ago)
Author:
weinreis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/runtime_parameters

    v38 v39  
    9999By default, with parallel runs, processors output only data of their respective subdomains into seperate local files (file names are constructed by appending the four digit processor ID, e.g. <filename>_0000, <filename>_0001, etc.). After PALM has finished, the contents of these individual files are sampled into one final file using the program {{{combine_plot_fields.x}}} (to be started e.g. by a suitable OUTPUT command in the '''mrun''' configuration file).\\\\
    100100Alternatively, PALM is able to collect all grid points of a cross section on PE0 before output is done. In this case only one  output file ([[DATA_2D_XY_NETCDF]], etc.) is created and {{{combine_plot_fields.x}}} does not have to be called. In case of very large numbers of horizontal gridpoints, sufficient memory is required on PE0.  This method can be used by assigning [[data_output_2d_on_each_pe]] = ''.F.''.\\\\
    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.
     1013d 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.\\\\
     102'''Old formats:'''\\\\
     103Beside 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]].\\\\
     104By assigning '''data_output_format''' = '' 'avs' '', the 3d volume data is output to the local file 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 PLOT3D_COOR) with coordinate information needed by AVS. As third and fourth file two ASCII files are created (AVS-FLD-format, local name PLOT3D_FLD and 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). Further details about plotting 3d volume data with AVS can be found in chapter 4.5.5.
    102105}}}
    103106|----------------
     
    337340dummy
    338341}}}
    339 |----------------
    340 {{{#!td style="vertical-align:top"
    341 [=#dummy '''dummy''']
    342 }}}
    343 {{{#!td style="vertical-align:top"
    344 dummy
    345 }}}
    346 {{{#!td style="vertical-align:top"
    347 dummy
    348 }}}
    349 {{{#!td
    350 dummy
    351 }}}
    352 |----------------
    353 {{{#!td style="vertical-align:top"
    354 [=#dummy '''dummy''']
    355 }}}
    356 {{{#!td style="vertical-align:top"
    357 dummy
    358 }}}
    359 {{{#!td style="vertical-align:top"
    360 dummy
    361 }}}
    362 {{{#!td
    363 dummy
    364 }}}
    365 |----------------
    366 {{{#!td style="vertical-align:top"
    367 [=#dummy '''dummy''']
    368 }}}
    369 {{{#!td style="vertical-align:top"
    370 dummy
    371 }}}
    372 {{{#!td style="vertical-align:top"
    373 dummy
    374 }}}
    375 {{{#!td
    376 dummy
    377 }}}
    378 |----------------
    379 {{{#!td style="vertical-align:top"
    380 [=#dummy '''dummy''']
    381 }}}
    382 {{{#!td style="vertical-align:top"
    383 dummy
    384 }}}
    385 {{{#!td style="vertical-align:top"
    386 dummy
    387 }}}
    388 {{{#!td
    389 dummy
    390 }}}|----------------
    391 {{{#!td style="vertical-align:top"
    392 [=#dummy '''dummy''']
    393 }}}
    394 {{{#!td style="vertical-align:top"
    395 dummy
    396 }}}
    397 {{{#!td style="vertical-align:top"
    398 dummy
    399 }}}
    400 {{{#!td
    401 dummy
    402 }}}
    403 |----------------
    404 {{{#!td style="vertical-align:top"
    405 [=#dummy '''dummy''']
    406 }}}
    407 {{{#!td style="vertical-align:top"
    408 dummy
    409 }}}
    410 {{{#!td style="vertical-align:top"
    411 dummy
    412 }}}
    413 {{{#!td
    414 dummy
    415 }}}