-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
ERROR: UndefVarError: NoAD
not defined
#747
Comments
@gdalle is this supposed to be living in ADTypes? |
For what it's worth I don't think our recent changes caused this bug, but we could definitely add something like |
MWE showing that this can be triggered by using OptimizationOptim.JL Optim.BFGS(), when using upper/lower bounds: (NB: Looks like this is a regression introduced in Optimization.jl v3.25.0)
with stack trace:
|
The breaking change is this commit: 3d5d102 PR #741 @Vaibhavdixit02 |
@sjdaines you are correct, I don't know how I missed this. Thanks a lot! |
Describe the bug 🐞
Since yesterday the error "LoadError: UndefVarError:
NoAD
not defined" appears after updating packages.Expected behavior
Previously, the code did not give this error, it is unclear why it no longer works or what a proper way to code.
Minimal Reproducible Example 👇
The code is extensive, so I can only provide a code fragment here for now
Error & Stacktrace⚠️
Environment (please complete the following information):
using Pkg; Pkg.status()
using Pkg; Pkg.status(; mode = PKGMODE_MANIFEST)
versioninfo()
Additional context
The text was updated successfully, but these errors were encountered: