Download Visual PEST-ASP
Transcript
Running PEST 5-10 fraction of the objective function value at the commencement of the optimisation iteration. During the first iteration of Example 5.1, PEST tests two Marquardt lambdas; because the second lambda results in an objective function fall of less than 0.03 (ie. PHIREDLAM) relative to the first one tested, PEST does not test any further lambdas. Instead it progresses to the next optimisation iteration after listing both the updated parameter values as well as those from which the updated parameter set was calculated, viz. those at the commencement of the optimisation iteration. Note that the only occasion on which the “previous parameter values” recorded at the end of an optimisation iteration do not correspond with those determined during the previous optimisation iteration is when the switch to three-point derivatives calculation has just been made and the previous iteration failed to lower the objective function; on such an occasion, PEST adopts as its starting parameters for the new optimisation iteration the parameter set resulting in the lowest objective function value achieved so far. At the end of each optimisation iteration PEST records either two or three (depending on the input settings) very important pieces of information; in the case of Example 5.1 it is two. These are the maximum factor parameter change and the maximum relative parameter change. As was discussed in previous chapters, each adjustable parameter must be designated as either factor-limited or relative-limited; in Example 5.1 all adjustable parameters are factor-limited with a factor limit of 3.0. A suitable setting for the factor and relative change limits (ie. FACPARMAX and RELPARMAX) may be crucial in achieving optimisation stability. Note that, along with the value of the maximum factor or parameter change encountered during the optimisation iteration, PEST also records the name of the parameter that underwent this change. This information may be crucial in deciding which, if any, parameters should be temporarily held at their current values should trouble be encountered in the optimisation process. For details of the options for user-intervention, see Section 5.6 of this manual. The recording of the maximum factor and relative parameter changes at the end of each iteration allows you to judge whether you have set these vital variables (ie. FACPARMAX and RELPARMAX) wisely. In the present case only the maximum factor change is needed because no parameters are relative-limited; the maximum relative parameter change is recorded, however, because one of the termination criteria involves the use of relative parameter changes. Note that had some of the parameters in Example 5.1 been relativelimited, this part of the run record would have been slightly different in that the maximum factor parameter change would have been provided only for factor-limited parameters and the maximum relative parameter change would have been provided for relative-limited parameters. However a further line documenting the maximum relative parameter change for all parameters would have been added because of its pertinence to the aforementioned termination criterion. The PEST run record of Example 5.1 shows that in iteration 2, one of the parameters, viz. “h2”, incurs the maximum allowed factor change, thus limiting the magnitude of the parameter upgrade vector. In optimisation iterations 3 and 4, parameter “h1” limits the magnitude of the parameter upgrade vector through incurring the maximum allowed parameter factor change. It is possible that convergence for this case would have been achieved much faster if FACPARMAX on the PEST control file were set higher than 3.0.