Should we add debugging functionality?

[timmercy]

Maybe we should add an option to show which constraints are violated in the case of an infeasible problem?

[rubenvanparys]

ok maybe, but

• how are you implement this? Evaluate every constraint and compare it with lbg, ubg. This is possible as the optilayer foresees the (numeric) evaluation of constraints.
• I don't know if this information is valuable. I am not sure whether only the critical constraints will be infeasible if ipopt returns 'infeasible problem'. In my opinion ipopt returns just rubbish in this case...

[jgillis]

In my experience such information is valuable. Especially when you see ipopt during its iterations to struggle to meet some constraints. It can be a helpful way to spot mistakes in your formulation.

[timmercy]

Joris showed me once how to do this. If I recall correctly: Before solving: from casadi.tools import reportBounds solver.setOption('warn_initial_bounds', True) solver.setOption('constr_viol_tol', 1e-4) After soving: solver.reportConstraints() reportBounds(nlp.getOutput("g"),solver.getInput("lbg"),solver.getInput("ubg"), showNonViolating=False)

You get a list in which you can see which constraints are fulfilled and which are violated. The only downside is that you don't get the name of the constraint, so you have to couple your list to your optimization formulation.

Is this implementation still possible in CasADi 3.0 or are there any other/better ways to do this?

[jgillis]

well okay that method is lame; i'm sure you can do it better..

[jgillis]

(if you used casadi structures, you can easily request readable labels for all entries of g)

[timmercy]

Okay, I used this method indeed before CasADi structures were used

[rubenvanparys]

We do use casadi structs for constraints

Okay, I used this method indeed before CasADi structures were used

You are receiving this because you commented. Reply to this email directly or view it on GitHubhttps://github.com/meco-group/omg-tools/issues/28#issuecomment-213275143