Changes between Version 2 and Version 3 of doc/app/runs

Timestamp:

Sep 16, 2010 9:22:04 AM (14 years ago)

Author:

kanani

Comment:

--

doc/app/runs

@@ -25 +25 @@
       PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df
 }}}
-with the restart runs. Given that this statement only gets active if the option {{{-r}}} is given the value {{{d3f}}} and that the '''mrun''' call for this restart run is produced automatically (thus not by the user), '''mrun''' obviously has to replace ''{{{d3#}}}'' of the initial run with ''{{{d3f}}}'' within the call of this restart run. Actually, with restart runs all ''{{{#}}}'' characters within the strings given for the options {{{-r}}} , {{{-i}}} and {{{-o}}} are replaced by ''{{{f}}}''.\\\\
+with the restart runs. Given that this statement only gets active if the option {{{-r}}} is given the value {{{d3f}}} and that the '''mrun''' call for this restart run is produced automatically (thus not by the user), '''mrun''' obviously has to replace {{{"d3#"}}} of the initial run with {{{"d3f"}}} within the call of this restart run. Actually, with restart runs all {{{"#"}}} characters within the strings given for the options {{{-r}}} , {{{-i}}} and {{{-o}}} are replaced by {{{"f"}}}.\\\\
 For example, for the initial run the permanent file
 {{{
@@ -34 +34 @@
       ~/palm/current_version/JOBS/abcde/INPUT/abcde_p3df
 }}}
-is used. Only with restart runs the local file [../iofiles#BININ BININ] is made available as input file, because the appropriate file connection statement also contains the character string ''{{{d3f}}}'' in the third column. This is logical and necessary since in BININ the binary data, produced by the model of the preceding job of the chain, are expected and the initial run does not need these data. The permanent names of this input file (local name BININ) and the corresponding output file (local name [../iofiles#BINOUT BINOUT]) are identical and read
+is used. Only with restart runs the local file [../iofiles#BININ BININ] is made available as input file, because the appropriate file connection statement also contains the character string {{{"d3f"}}} in the third column. This is logical and necessary since in BININ the binary data, produced by the model of the preceding job of the chain, are expected and the initial run does not need these data. The permanent names of this input file (local name BININ) and the corresponding output file (local name [../iofiles#BINOUT BINOUT]) are identical and read
 {{{
       ~/palm/current_version/JOBS/abcde/OUTPUT/abcde_d3d
 }}}
 However, after the file produced by the previous job was read in by the model and after the local file BINOUT was produced at the end of the job, the restart job does not overwrite this permanent file ({{{.../abcde_d3d}}}) with the new data. Instead of that, it is examined whether already a permanent file with the name {{{.../abcde_d3d}}} exists when copying the output file (BINOUT) of '''mrun'''. If this is the case, BINOUT is copied to the file {{{.../abcde_d3d.1}}}. Even if this file is already present, {{{.../abcde_d3d.2}}} is tried etc. For an input file the highest existing cycle of the respective permanent file is copied. In the example above this means: the initial run creates the permanent file {{{.../abcde_d3d}}}, the first restart run uses this file and creates {{{.../abcde_d3d.1}}}, the second restart run creates {{{.../abcde_d3d.2}}} etc. After completion of the job chain the user can still access all files created by the jobs. This makes it possible for the user for example to restart the model run of a certain job of the job chain again.\\\\
-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}}}''. 
+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"}}}.