You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently exploring the SQPMETHOD solver in MATLAB, I noticed that while options for KNITRO and IPOPT are passed to the respective solver by a struct containing a field with a name equal to the solver (which itself is expected to be a struct with fields equal to the option names), SQPMETHOD seems to expect the individual options at the "root level" of the option struct itself: If I add a field like opts.sqpmethod = struct(); and call the nlp object – like I've done it for all other solvers so far (with their respective name in place) – I get an error that the option sqpmethod is unknown.
Am I doing something wrong, or is this intended? As it stands, it makes switching solvers a little cumbersome if they are highly parametrized.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi
Recently exploring the SQPMETHOD solver in MATLAB, I noticed that while options for KNITRO and IPOPT are passed to the respective solver by a struct containing a field with a name equal to the solver (which itself is expected to be a struct with fields equal to the option names), SQPMETHOD seems to expect the individual options at the "root level" of the option struct itself: If I add a field like
opts.sqpmethod = struct();
and call the nlp object – like I've done it for all other solvers so far (with their respective name in place) – I get an error that the optionsqpmethod
is unknown.Am I doing something wrong, or is this intended? As it stands, it makes switching solvers a little cumbersome if they are highly parametrized.
Thank you and best regards, Gregor.
Beta Was this translation helpful? Give feedback.
All reactions