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

Explicit warning when AD backend not specified correctly for automatic box-constraint handling with Optim #741

Merged
merged 3 commits into from
May 17, 2024

Conversation

Vaibhavdixit02
Copy link
Member

Checklist

  • Appropriate tests were added
  • Any code changes were done in a way that does not break public API
  • All documentation related to code changes were updated
  • The new code follows the
    contributor guidelines, in particular the SciML Style Guide and
    COLPRAC.
  • Any new documentation only uses public API

Additional context

Fixes #713 #558
Add any other context about the problem here.

@ChrisRackauckas
Copy link
Member

Instead of a warning should it error?

@Vaibhavdixit02
Copy link
Member Author

I guess that might lead to fewer issues, so makes sense. It would be a breaking change though

@Vaibhavdixit02 Vaibhavdixit02 merged commit 87e7542 into master May 17, 2024
34 of 42 checks passed
@Vaibhavdixit02 Vaibhavdixit02 deleted the Vaibhavdixit02-patch-4 branch May 17, 2024 02:38
@sjdaines
Copy link
Contributor

This errors with ERROR: UndefVarError: NoAD not defined in Optimization.jl v3.25.0

See issue #747

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.

MethodError: objects of type Nothing are not callable when lb and ub are used with NelderMead
3 participants