Closed moorepants closed 1 month ago
It may be worth to try again once https://github.com/conda-forge/ipopt-feedstock/pull/58 is merged. The bug https://github.com/conda-forge/ipopt-feedstock/issues/57 could create quite subtle wrong behaviors.
In the output of your examples I see that there is a difference in the linear solver used (pardiso vs mumps). Could this be the source of the problem?
Reading a bit more, I see that the error was:
Exception message: success && IsFiniteNumber(ret) evaluated false: Error evaluating the objective function
Given that, I think that probably this was due to https://github.com/conda-forge/ipopt-feedstock/issues/57, that was indeed related to IsFiniteNumber
not working correctly.
In the output of your examples I see that there is a difference in the linear solver used (pardiso vs mumps). Could this be the source of the problem?
Interesting. I'm not sure why pardiso would be loaded. I didn't think we were installing that.
Opened https://github.com/mechmotum/cyipopt/pull/267 to check this and see if it can be closed.
I see no issues with the current conda forge binaries in #267, so closing.
Text taken from https://github.com/matthias-k/cyipopt/pull/78:
This is the exception_handling.py output with Py 2.7, IPOPT 3.13.2 (official binary) on Windows:
And Python 3.8, IPOPT 3.13.3 (via conda forge), on Windows:
Maybe there is a difference in IPOPT 3.13.2 and 3.13.3 that prevents this exception to be properly caught?
So 3.13.2 give the same results on Py 27 and Py 38 on Windows. Maybe this due to a change introduced in 3.13.3.
The file IpOrigIpoptNLP.cpp was edited between 3.13.2 and 3.13.3. See:
https://github.com/coin-or/Ipopt/compare/releases/3.13.2...master#diff-9a3e51142bc8474657621b48b0490655b611422d8df80ffb35db280763789a0a
But the only changes are extra forwardslashes. Not sure what that does...
I tried the official Ipopt 3.13.3 binaries with Python 3.* on Windows and that works as expected. The oddity is only from the conda forge builds. So something is likely different in the conda forge builds. I think we could merge this as is and open an issue for this exception handling issue.