There’s an option called extended_trace that will store the entire state 
history of the optimization routine and often a bit more (like gradients, 
hessians).

 — John

On Mar 1, 2014, at 12:14 PM, Tom Nickson <[email protected]> wrote:

> If I call optim with store_trace = true or show_trace = true, I get the value 
> of the function at each point along the run. Is it possible to get it to spit 
> out where the function was evaluated as well? I can easily adulterate my 
> function to log its location, or even modify optim.jl but is there a built in 
> method?
> 
> Tom

Reply via email to