-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SLSQP in NLopt.jl 1.0.2 throws error: bug: more than iter SQP iterations
#215
Comments
That's weird, it's supposed to never reach that check, since we check the evaluation count elsewhere. |
I linked the wrong line. now corrected to L2585 I don't fully grasp the flow of the script (yet) but I can confirm that he throws: |
Do you have a reproducible example? |
I get the same error. Here is a MWE:
NLopt |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I understand 1.0.1 => 1.0.2 brought changes to the error handling.
this is inconvenient in the case of SLSQP because it (now) throws an error when maxeval is reached and the optimisation failed. for my purposes it would be useful to have access to the return values even if the optimisation failed/errored. in other words, not throw an error and hand over return values
The text was updated successfully, but these errors were encountered: