Skip to content
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

Check more retcodes from NLopt #879

Merged
merged 3 commits into from
Feb 5, 2025
Merged

Conversation

sumiya11
Copy link
Contributor

@sumiya11 sumiya11 commented Feb 5, 2025

This change covers all successful termination return codes listed in NLopt documentation (https://nlopt.readthedocs.io/en/latest/NLopt_Reference/#successful-termination-positive-return-values).

A test in OptimizationNLopt will follow.

Closes #862.

@sumiya11
Copy link
Contributor Author

sumiya11 commented Feb 5, 2025

Added tests for new return codes.

I am not 100% positive about the test for MAXTIME_REACHED, but it seems to work as expected.

@sumiya11
Copy link
Contributor Author

sumiya11 commented Feb 5, 2025

I wonder why that test in NLopt started failing.

@sumiya11
Copy link
Contributor Author

sumiya11 commented Feb 5, 2025

This test failed sporadically also in previous commits; so I relaxed the condition.

@ChrisRackauckas ChrisRackauckas merged commit 0af051b into SciML:master Feb 5, 2025
22 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect return value classification of FTOL_REACHED from NLopt
2 participants