handle_set_nlnhess is a part of the NAG optimization modelling suite and defines or redefines either the structure of the Hessians of the nonlinear objective and constraints or the structure of the Hessian of the Lagrangian.
After the handle has been initialized (e.g., handle_init has been called),
and a nonlinear objective function and/or
the th ()
nonlinear constraint function has been registered with handle_set_nlnconstr and handle_set_nlnobj,
then
handle_set_nlnhess may be used to define the sparsity structure (pattern) of the Hessians
of those functions or of their Lagrangian function. Define:
, and
for
handle_set_nlnhess can be used to define the following sparsity structures:
the Hessian of the Lagrangian function ,
the Hessian of the objective function , or
the Hessian of the th constraint function
with
.
In general, each of the symmetric Hessian matrices will have its own sparsity structure. These structures can be given in separate handle_set_nlnhess calls, or merged together in the Lagrangian and given in one call. The nonzero values of the Hessians at particular points will be communicated to the NLP solver by user-supplied functions (e.g., hess for handle_solve_ipopt). The values will need to be provided in the order matching the sparsity pattern.
Note that the Hessians are automatically deleted whenever the underlying functions change. For example, if handle_set_nlnconstr is called to redefine the nonlinear constraints, all individual constraints Hessians or Hessian of the Lagrangian would be deleted. If a nonlinear objective function was changed to linear, the Hessian of the objective function or of the Lagrangian would be deleted. handle_set_nlnhess can work either with individual Hessians or with the Hessian of the Lagrangian but not both. Therefore, if the Hessian of the Lagrangian was defined and handle_set_nlnhess was called to define an individual Hessian of the constraint, the Hessian of the Lagrangian would be removed, and vice versa. Hessians can be redefined by multiple calls of handle_set_nlnhess.
See Section 3.1 in the E04 Chapter Introduction for more details about the NAG optimization modelling suite.
Communication structure.
An object of either the derived class CommE04RA or its base class NoneCopyableComm can be supplied.
It is recommended that the derived class is used. If the base class is supplied it must
first be initialized via a call to opt::handle_init (e04ra).
On entry: specifies the functions for which a Hessian sparsity structure is provided in nnzh, irowh and icolh.
The sparsity structure of the Hessian of the Lagrangian is provided.
The sparsity structure of the Hessian of the objective function is provided.
The sparsity structure of the Hessian of the idfth constraint function is provided.
The value of idf will also determine how an NLP solver will call the user-supplied functions that evaluate these nonzeros at particular points of the decision variable space, i.e., whether the solver will expect the nonzero values of the objective and constraint Hessians in separate calls or merged in the Lagrangian Hessian, in one call. See, for example, hess of handle_solve_ipopt.
Constraint:
.
Note: , the number of nonlinear constraints registered with the handle.
On entry: arrays irowh and icolh store the nonzeros of the upper triangle of the matrix in coordinate storage (CS) format (see Section 2.1.1 in the F11 Chapter Introduction). irowh specifies one-based row indices, icolh specifies one-based column indices and specifies the values of the nonzero elements in such a way that where and
, for . No particular order is expected, but elements should not repeat.
On entry: arrays irowh and icolh store the nonzeros of the upper triangle of the matrix in coordinate storage (CS) format (see Section 2.1.1 in the F11 Chapter Introduction). irowh specifies one-based row indices, icolh specifies one-based column indices and specifies the values of the nonzero elements in such a way that where and
, for . No particular order is expected, but elements should not repeat.
Constraint:
, for .
5: – OptionalE04RLInput/Output
Optional parameter container, derived from Optional.
5.1Additional Quantities
1:
The number of nonzero elements in the upper triangle of the matrix
6Exceptions and Warnings
Errors or warnings detected by the function:
All errors and warnings have an associated numeric error code field, errorid, stored either as a member of the thrown exception object (see errorid), or as a member of
opt.ifail, depending on how errors
and warnings are being handled (see Error Handling for more details).
comm::handle does not belong to the NAG optimization modelling suite, has not been initialized properly or is corrupted.
comm::handle has not been initialized properly or is corrupted.
The problem cannot be modified right now, the solver is running.
Neither nonlinear objective nor nonlinear constraints are present. The structure of the Hessian cannot be defined.
No nonlinear objective has been defined, its Hessian cannot be set.
On entry, . Constraint: .
On entry, . Constraint: .
On entry, , and . Constraint: .
On entry, , and . Constraint: .
On entry, , and . Constraint: (elements within the upper triangle).
On entry, more than one element of structural matrix has row index and column index . Constraint: each element of structural matrix must have a unique row and column index.
On entry, argument must be a vector of size array. Supplied argument has dimensions.
On entry, argument must be a vector of size array. Supplied argument was a vector of size .
On entry, argument must be a vector of size array. The size for the supplied array could not be ascertained.
On entry, the raw data component of is null.
On entry, unable to ascertain a value for .
On entry, the communication class has not been initialized correctly.
An unexpected error has been triggered by this routine.
Your licence key may have expired or may not have been installed correctly.
Dynamic memory allocation failed.
7Accuracy
Not applicable.
8Parallelism and Performance
Please see the description for the underlying computational routine in this section of the
FL Interface documentation.
9Further Comments
10Example
Examples of the use of this method may be found in the examples for: handle_solve_ipopt.