Add callback timing information about rosetta-opf HOT 5 CLOSED

See #11

You can get Ipopt to print it if you turn up the output level.

from rosetta-opf.

I agree that we should report the time spent in the callbacks (apparently the latest Ipopt version does not report that information anymore). On my side, I am using the following fields in JuMP:
https://github.com/jump-dev/JuMP.jl/blob/master/src/nlp.jl#L359-L364

knowing that JuMP:

• (1) first run a forward and a reverse passes to evaluate the objective, the constraints, the gradient and the Jacobian
• (2) then evaluate the Hessian of the Lagrangian apart with a forward-over-reverse pass.

Hence, if we exclude the time spent in the extraction, we know only the time spent in (1) (objective+gradient+constraint+Jacobian) and in (2) (Hessian). At least as far as I understand JuMP's AD.

from rosetta-opf.

You can get Ipopt to print it if you turn up the output level.

Actually, it's:

set_optimizer_attribute(model, "print_timing_statistics", "yes")

from rosetta-opf.

Is there anything actionable to do on this topic? As far as I can tell, we already collect as much of this as we can.

from rosetta-opf.

from rosetta-opf.