Download Model-Independent Parameter Estimation Watermark

Parallel PEST
10-10
ensure that these files are written correctly to the PSLAVE working directory no matter what
is its full pathname. Note however that the directory K:\ (without the dot) is not the same
directory as K:.\ (with the dot) if directories under the PSLAVE working directory are
accessible from the machine on which PEST is run. If there are any doubts, provide the full
PSLAVE path.
Note also from Example 10.2 that a slave on the local machine can work from the same
directory as PEST. This may be desirable if all model input files are in this same directory
(which is often the case) and this is also the current PEST working directory. A designation of
.\ is sufficient to identify this directory.
The next line of the run management file must contain as many entries as there are slaves.
Each entry is the expected run time of the model on the respective slave, the ordering of
slaves on this line being the same as that in which slave data was supplied earlier in the run
management file. Run times should be supplied in seconds; if you are unsure of the exact run
times, simply provide the correct run time ratios. There is no need for stopwatch precision
here as PEST continually updates model run time estimates in the course of the parameter
estimation process. However it is better to overestimate, rather than underestimate these run
times so that PEST will not re-instigate the initial model run (which is not part of the
Jacobian calculation) on an alternative machine if the initial model run takes much longer
than you have indicated, and PEST comes to the conclusion that a mishap may have occurred
on the machine to which that run was initially assigned.
If the value supplied for IFLETYP is 0, then the run management file is complete. However if
it is supplied as 1, the names of all model input files and all model output files on all slave
machines must next be supplied individually. Either full pathnames can be supplied or
abbreviated pathnames, the abbreviations being sufficient for PEST to write and read the
respective files from the directory in which it is run. Data for the various slaves must be
supplied in the same order as that in which the slaves were introduced earlier in the file. For
each slave the names of NTPFLE model input files must be followed by the names of
NINSFLE model output files, where NTPFLE is the number of template files and NINSFLE
is the number of instruction files pertaining to the present PEST case. (Note that the PEST
template and instruction file corresponding to each of these model input and output files is
identified in the PEST control file read by Parallel PEST.)
Example 10.3 shows a Parallel PEST run management file equivalent to that of Example 10.2
but with the value of NFLETYP set to 0. Use of an abbreviated run management file such as
that shown in Example 10.3 is only possible where all model input and output files on each
slave reside in the one subdirectory, and this subdirectory is also the PSLAVE working
directory on that machine.
prf
3 0 1.5
'my machine' .\
'steve''s machine' k:.\
'jerome''s machine' l:\model
600 600 720
Example 10.3 A Parallel PEST run management file equivalent to that of Example
10.2, but with NFLETYP set to zero.