DONLP2 computes the names of the two files for output using the first 8 characters from NAME . If NAME is shorter
than 8 characters XXX.. is appended to NAME . These files are used for the following: The NAME(1:8).PRO file contains
the results of the optimization run . Of course these results are also contained in the named common blocks described
below. In case of a failure a short protocol of the complete run is appended, which may be evaluated by a knowledgeable
person in order to locate the problem.
!!!! FORTRAN files PROU and MEU are used for output and must not be used otherwise by the user
Output can be of
various stages of volume: Normally the final results are written to the PRO- and the "special events" to the MES-file.
That means TE0=TE1=TE2=TE3=.FALSE., as given in the head of DONLP2. Then the XXXXXXXX.PRO -file holds the following:
if TE0 is set true, then a one-line-information is written to std-out for every step of iteration, giving sufficient information on the progress of solution. This is the following:
If TE1 is set true, the short protocol accumulated in the array ACCINF is printed at termination. TE1 is set to true automatically in case of unsuccessful termination. The ACCINF-array is a 32-column array, each line of which holds information on an iteration in condensed form, see below .
If TE2 is set true, intermediate results X,D, active constraint values and so on are written to the PRO-file. These are:
If TE3 is true, the values of the gradients and the approximated Hessians are printed too, provided n £ 50 and NRES=NH+NG £ 100. The *.MES-file is of value if the optimizer ends irregularly. It contains a message for every action which is "abnormal" in the sense of good progress for a regular and well conditioned problem. In most cases special advice is necessary to evaluate it. However, if the user observes many restarts reported in the *.MES file or similarly many calls to the full sqp-method, she(he) should check the problem against bad scaling and redundant constraints!