Hi,
If you are modifying the optimization problem often (i.e. in an MPC problem), then using the opti constructor is likely not the most efficient, especially for nonlinear problems. You are better off using the solver interface directly, such as described here:
http://www.i2c2.aut.ac.nz/Wiki/OPTI/index.php/Advanced/LowLevel
You can inspect the problem OPTI is passing to NLOPT via Opt.nlprob (“nlprob” property of the OPTI object called “Opt”). Then you can pass parameters by redefining a function handle to the objective/constraints before each call:
http://au.mathworks.com/help/optim/ug/passing-extra-parameters.html?refresh=true
Regards,
Jonathan
--
You received this message because you are subscribed to the Google Groups "OPTI Toolbox Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opti-toolbox-fo...@googlegroups.com.
To post to this group, send email to opti-tool...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "OPTI Toolbox Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/opti-toolbox-forum/_mtrSclUE7E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to opti-toolbox-fo...@googlegroups.com.
Hi,
No, the fields are deliberately read only. My intention was for you to call NLOPT directly, using the function handles similar to the ones OPTI makes. Use the nlprob structure just as a reference, then look at the opti_nlopt function.
Jonathan