handle_init initializes an empty problem, adds
decision variables,
, and returns a handle to the data structure. Note that further variables may be added to the problem later by
e04taf (no CPP interface) and it is also possible to temporarily disable and enable individual variables in the model by
e04tcf (no CPP interface) and
e04tbf (no CPP interface), respectively. This handle may then be passed to some of the functions of the suite to formulate the problem (define or edit the variables, the objective function and constraints). Once the problem is fully defined, the handle may be passed to a suitable solver from the suite (
e04fff (no CPP interface),
handle_solve_dfls_rcomm,
e04ggf (no CPP interface),
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)). Afterwards, the problem may be further modified or passed to another solver of the suite. The handle
must not be changed between calls to the functions of the suite. 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.