Verify optimal values reported by ipopt
Opened this issue · 1 comments
dweindl commented
[2019-12-19 13:50:47] [INF] [ 0/i02r07c02s12.sng.lrz.de] [o7i4] iter: 4 cost: 163896 time_iter: wall: 367.656s cpu: 4444.31s time_optim: wall: 2062.4s cpu: 22920.6s
[2019-12-19 13:50:47] [INF] [ 0/i02r07c02s12.sng.lrz.de] [o7i5] cachedCost != optimalCost
Add output. Why is a different value reported? Not considering progress during linesearch again?
dweindl commented
Partially fixed in 8018064.
Remaining cases seem to occur in combination with hierarchical optimization. If Ipopt makes no progress during line search, the optimum is an older function value, for which the inner parameter are not stored anymore. Either need to keep a longer history, or recompute those values.