Closed dpo closed 6 years ago
There it is. Sorry for the confusion. Yes, logging is supposed to be set up as in the examples. It's turned off by default but it's more flexible than a verbose
argument that has to be propagated.
Same old gcc error. I think this can safely be labeled as good to go.
Manually rebased and merged. Thanks.
I'm not sure how the logging is supposed to be used. Is it to be created when calling the optimizer, outside Optimize.jl - like the examples? Also,
lbfgslogger
is insidelbfgs.jl
, buttrunklogger
is not insidetrunk.jl
.