handle_init initializes an empty problem with
decision variables,
, and returns a handle to the data structure. This handle may then be passed to some of the functions
handle_set_group,
handle_set_linobj,
handle_set_quadobj,
handle_set_nlnobj,
handle_set_simplebounds,
handle_set_linconstr,
handle_set_nlnconstr,
handle_set_nlnhess,
handle_set_nlnls,
e04rnf (no CPP interface) and
e04rpf (no CPP interface) to formulate the problem (define the objective function and constraints) and to a compatible solver,
e04fff (no CPP interface),
handle_solve_dfls_rcomm,
e04jdf (no CPP interface),
e04jef (no CPP interface),
handle_solve_bounds_foas,
handle_solve_lp_ipm,
handle_solve_socp_ipm,
handle_solve_ipopt and
e04svf (no CPP interface), to solve it. The handle
must not be changed between calls. When the handle is no longer needed,
handle_free must be called to destroy it and deallocate all the allocated memory and data within. See
Section 3.1 in the
E04 Chapter Introduction for more details about the NAG optimization modelling suite.
None.
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).
Not applicable.
Please see the description for the underlying computational routine in this section of the
FL Interface documentation.
None.
Examples for the NAG CPP Interface are not currently available.