Changes between Version 11 and Version 12 of doc/app/runs

Timestamp:

Sep 19, 2018 2:34:15 PM (6 years ago)

Author:

raasch

Comment:

--

doc/app/runs

@@ -1 +1 @@
 
-= Initialization and restart runs =
+= Restart runs / Handling of large (restart) files =
+
+Batch systems generally limit the CPU time that is allowed to be requested by a job, e.g. to a maximum of 12 hours or 24 hours. If a simulation needs more time to run, it has to be split into several parts/jobs. The first job is called the ''initial'' job, the others ''restart'' jobs. Together they form a so-called ''job chain''. Restart jobs require as input the values of all flow variables after the final time step of the previous job. They need to be output by the previous job in a so-called ''restart-file''.
+
+{{{palmrun}}} allows you to automatically generate job chains and to handle the restart files. Of course, automatic generation does not work if you run PALM in interactive mode. The following chapter describes
 
 A job started by '''[../../app/jobcontrol mrun]''' will - according to its requested computing time, its memory size requirement and the number of necessary processing elements (on parallel computers) - be queued by the queuing-system of the local or remote computer into a suitable job class which fulfills these requirements. Each job class permits only jobs with certain maximum requirements (e.g. the allowed CPU time or the maximum number of cores that can be used by the job). The job classes are important for the scheduling process of the computer. Jobs with small requirements usually come to execution very fast, jobs with higher requirements must wait longer (sometimes several days).\\\\
@@ -41 +45 @@
 Therefore restart jobs can not only be started automatically through '''mrun''', but also manually by the user. This is necessary e.g. whenever after the end of a job chain it is decided that the simulation must be continued further, because the phenomenon which should be examined did not reach the desired state yet. In such cases the '''mrun''' options completely correspond to those of the initial call; simply the {{{"#"}}} characters in the arguments of options {{{-r}}}, {{{-i}}} and {{{-o}}} must be replaced by {{{"f"}}}.\\\\
 
-= Handling of large binary restart- or output-files =
+= Handling of large (restart) files =
 
 In case of very large files, the copy of data from and to '''mrun's''' temporary working directory may need a long time. The CPU cores requested for the job run idle during that time and may consume significant amount of the job time without doing anything. The time required for copying can be spared by using a file link instead of copying the data.
@@ -69 +73 @@
 }}}
 Such fast file systems are generally not allowed to store files for a longer time, so the user has to take care for archiving himself.
-
-'''Attention:'''\\
-The {{{ln}}} file attribute and the above described method for storing large binary files has been introduced with revision number r2262. {{{mrun}}} does not create empty files/directories for restart files in the folder given with the file connection statement any more, as it was done with feature "fl" before.