Conic process error message withholds important debug information.

[Michi Floßmann]

Hi!

I'm not sure if this is the correct to put this issue or if it's better suited for a github issue.

I have been using casadi in conjunction with qpOASES for my project for a few months now and recently updated to v3.5.1-2.
In previous versions of Casadi, whenever qpOASES failed to solve my problem, it raised an error with an accurate description of what went wrong, e.g. infeasibility error, unbounded problem, etc.

Now, whenever a problem with qpOASES comes up, the exception seems to be caught and instead this message is shown:

 conic process failed. Set 'error_on_fail' option to false to ignore this error

I find this behaviour extremely less useful than the previous one. Now, I can choose to crash or ignore it, without the option to find out WHY the process failed. To me, this is a good example of improving something for the worse.

Are there any plans to introduce options to diagnose these kinds of errors?

[Joris Gillis]

Dear Michi,

Thanks for reporting.
Can you specify the context you are seeing this new behaviour in?
In Python linux terminal, the old debug messages still appear like they used to..

Best,
Joris

[Joakim Børlum]

Hi Joris,

I am seeing the same behavior.

Python 3.7, casadi 3.5.1 (installed using pip).

My problem solves just fine using IPOPT, but now I wanted to see if I could get it working aswell, using qrqp (for code-generation purposes).

However, I just run into:





conic process failed. Set 'error_on_fail' option to false to ignore this error

BR,

Joakim