"The algorithm NOMADOpt does not support callbacks"
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 839
- Forks
- 100
- Avg merge
- 20h 43m
- Merged PRs (30d)
- 38
Description
I try to run an optimization (using a callback to save the evaluations) with the NOMAD package. However, it does not seem to support callbacks:
solve(optprob, NOMADOpt(); maxtime=10, callback=cb)
produces error:
ERROR: The algorithm NOMADOpt does not support callbacks, remove the `callback` keyword argument from the `solve` call.
Stacktrace:
[1] #_check_opt_alg#553
@ ~/.julia/packages/SciMLBase/zXEYU/src/solve.jl:98 [inlined]
[2] solve(::SciMLBase.OptimizationProblem{true, OptimizationFunction{true,Optimization.AutoForwardDiff{nothing},…}, Vector{Float64}, SciMLBase.NullParameters, Vector{Float64}, Vector{Float64}, Nothing, Nothing, Nothing, Nothing, Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}}}, ::NOMADOpt; kwargs::Base.Pairs{Symbol, Any, Tuple{Symbol, Symbol}, NamedTuple{(:maxtime, :callback), Tuple{Int64, typeof(cb)}}})
@ SciMLBase ~/.julia/packages/SciMLBase/zXEYU/src/solve.jl:84
[3] top-level scope
@ ~/Activate-CRN-Learning/playground.jl:89
Not sure if this is something that could be implemented? Alternatively, maybe the "Overview of the Optimizers" table could note which optimizers supports callbacks and which do not?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SciMLBase solve.jl _check_opt_alg path shown in the stack trace and inspect how NOMADOpt is represented in the Optimization.jl interface. Determine whether callback support can be implemented or whether the Overview of the Optimizers table should document this limitation. Done means callback behavior is supported or the optimizer's callback capability is clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100