| 1154 | | 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. 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.\\\\ |
| 1155 | | 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}}}.\\\\ |
| 1156 | | '''Note:'''\\ |
| 1157 | | 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). |
| | 1154 | 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.\\\\ |
| | 1155 | 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}}}. |
