Open zaikunzhang opened 3 months ago
@zaikunzhang
The issue is upstream, they didn't interfaced correctly PRIMA.jl
.
It seems that they already fixed the problem in SciML/Optimization.jl
:
https://github.com/SciML/Optimization.jl/pull/721
No PRIMA.jl
is certainly not broken (there is however the Windows issue with CUTEst) and does not use AD at all, just the values returned by the objective function. The reported issue is clearly a misuse of the method, I think that's what has been already answered.
Hello, the issue https://github.com/SciML/Optimization.jl/issues/719 was definitely on the side of Optimization.jl, not PRIMA.jl itself. (And it also only occurred when using PRIMA.jl via Optimization.jl.) That's why I opened the issue there.
Similarly, the AD is used for detection of lin/nonlin constraints by Optimization.jl, not COBYLA itself.
I just worded myself poorely. Sorry about that. :)
PS: Thanks for the great implementation of great algorithms! :)) PRIMA has quickly become my favorite robust derivative-free optimization library.
Hi @soldasim ,
Great! Thank you for letting us know!
Best regards, Zaikun
Hi @amontoison and @emmt ,
Could you have a look at the following correlated issues?
https://github.com/SciML/Optimization.jl/issues/719
https://github.com/soldasim/BOSS.jl/issues/28
I do believe this is a problem with the Julia interface. Shouldn't we just ignore anything related to automatic deafferentation, since PRIMA does not use it at all?
Quoting the first issue:
This isn't the case, right?
Quoting the second issue:
This is important for us. People believe that PRIMA.jl is broken ...
Thanks!
Zaikun