Changes between Version 354 and Version 355 of doc/app/runtime_parameters


Ignore:
Timestamp:
Feb 15, 2021 8:29:19 AM (4 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/runtime_parameters

    v354 v355  
    13061306|----------------
    13071307{{{#!td style="vertical-align:top"
    1308 [=#termination_time_needed '''termination_time_needed''']
    1309 }}}
    1310 {{{#!td style="vertical-align:top"
    1311 R
    1312 }}}
    1313 {{{#!td style="vertical-align:top"
    1314 35.0
    1315 }}}
    1316 {{{#!td
    1317 CPU time needed for terminal actions at the end of a run in batch mode (in s).\\\\
    1318 If the environment variable '''write_binary''' is set ''.T.'' (see [../runs Initialization and restart runs]), PALM checks the remaining CPU time of the job after each time step. 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. Furthermore, the parameter has also to account for the CPU time consumed by the job '''before''' the PALM executable has started (e.g. required for providing input data, or for compiling the user-interface code, etc.). 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.\\\\
    1319 An abort happens in any way, if the activation string '''restart''' is not given with the {{{palmrun}}}-option {{{-a}}} and if the job has additionally been assigned an insufficient CPU time by '''palmrun''' option {{{-t}}}.
    1320 }}}
    1321 |----------------
    1322 {{{#!td style="vertical-align:top"
    13231308[=#nz_do3d '''nz_do3d''']
    13241309}}}
     
    15041489|----------------
    15051490{{{#!td style="vertical-align:top"
     1491[=#restart_data_format '''restart_data_format''']
     1492}}}
     1493{{{#!td style="vertical-align:top"
     1494C*20
     1495}}}
     1496{{{#!td style="vertical-align:top"
     1497'fortran_binary'
     1498}}}
     1499{{{#!td
     1500Binary format of the input and output restart files.\\\\
     1501Allowed values are '' 'fortran_binary' '', '' 'mpi' '', and '' 'mpi_shared_memory' ''. In case of '' 'fortran_binary' '' each core reads/writes its own file. In case of '' 'mpi' '', the I/O is done using a single file. This method can also be used in serial mode (when PALM has been compiled without {{{-D__parallel}}} option). In such a case, restart I/O is carried out using POSIX calls.\\\\
     1502On many-core processors the I/O speed can be increased by setting '''restart_data_format''' = '' 'mpi_shared_memory' ''. With this setting, I/O is performed only by a limited number of cores on each of the nodes. With mpi every core writes and reads its relevant data. With mpi_shared_memory, only every 4th (or any other multiple integer of the cores per node) reads and writes data and distributes it to the other cores. This is possible since all processes on a node can share their memory. With this, the IO rates might increase.
     1503
     1504This parameter can also be used in the initialization parameter NAMELIST.
     1505}}}
     1506|----------------
     1507{{{#!td style="vertical-align:top"
     1508[=#restart_data_format_input '''restart_data_format_input''']
     1509}}}
     1510{{{#!td style="vertical-align:top"
     1511C*20
     1512}}}
     1513{{{#!td style="vertical-align:top"
     1514value of [#restart_data_format restart_data_format]
     1515}}}
     1516{{{#!td
     1517Binary format of the input restart file.\\\\
     1518See [#restart_data_format restart_data_format] for allowed values.
     1519
     1520This parameter can also be used in the initialization parameter NAMELIST.
     1521}}}
     1522|----------------
     1523{{{#!td style="vertical-align:top"
     1524[=#restart_data_format_output '''restart_data_format_output''']
     1525}}}
     1526{{{#!td style="vertical-align:top"
     1527C*20
     1528}}}
     1529{{{#!td style="vertical-align:top"
     1530value of [#restart_data_format restart_data_format]
     1531}}}
     1532{{{#!td
     1533Binary format of the output restart file.\\\\
     1534See [#restart_data_format restart_data_format] for allowed values.
     1535
     1536This parameter can also be used in the initialization parameter NAMELIST.
     1537}}}
     1538|----------------
     1539{{{#!td style="vertical-align:top"
    15061540[=#restart_time '''restart_time''']
    15071541}}}
     
    15201554For [../examples/coupled coupled runs] this parameter must be equal in both parameter files [[../iofiles#PARIN|PARIN]] and [[../iofiles#PARIN_O|PARIN_O]].
    15211555}}}
     1556|----------------
     1557{{{#!td style="vertical-align:top"
     1558[=#termination_time_needed '''termination_time_needed''']
     1559}}}
     1560{{{#!td style="vertical-align:top"
     1561R
     1562}}}
     1563{{{#!td style="vertical-align:top"
     156435.0
     1565}}}
     1566{{{#!td
     1567CPU time needed for terminal actions at the end of a run in batch mode (in s).\\\\
     1568If the environment variable '''write_binary''' is set ''.T.'' (see [../runs Initialization and restart runs]), PALM checks the remaining CPU time of the job after each time step. 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. Furthermore, the parameter has also to account for the CPU time consumed by the job '''before''' the PALM executable has started (e.g. required for providing input data, or for compiling the user-interface code, etc.). 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.\\\\
     1569An abort happens in any way, if the activation string '''restart''' is not given with the {{{palmrun}}}-option {{{-a}}} and if the job has additionally been assigned an insufficient CPU time by '''palmrun''' option {{{-t}}}.
     1570}}}
    15221571\\\\
    15231572[=#pgrid '''Processor grid / MPI settings:]\\