-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: SIMPLEX_STRATEGY_PRIMAL strategy fails #348
Comments
The primal simplex solver is WIP. Qi wrote it last summer, and I know that there are bugs in it. Please don't invite folk to use it via your wrapper. Once again, we don't have a mechanism for preventing users from setting option values that we need to use for development. I note the example - which is from issue #280 - and will use it in debugging the primal simplex solver |
Actually, I've just tried to solve the LP given by the MPS file and, whether or not presolve is used, HiGHS returns the correct solution. This is regardless of the simplex options that's chosen - quite simply because no simplex solver needs to be used as the initial point is optimal. Could you generate one of the random problems and send post it as an MPS file. I don't understand your use of the random function well enough to generate them myself. Thanks |
I will make a note to avoid using this option in production. This shouldn't be the same example as in #280, I've made a mistake in uploading the incorrect file. This should be the correct MPS file: |
I'm now reproducing the bug with this MPS file, thanks. |
This is no longer failing on current master, will close |
The following problem is solved correctly by all other simplex strategies except
SIMPLEX_STRATEGY_PRIMAL
:or the following MPS file:
simplex_primal_test.txt
The following options were used:
The HiGHS call was run as follows:
The following simplex strategies were able to achieve optimal solution:
I will also note that the
simplex_strategy
SIMPLEX_STRATEGY_NUM
raises the following warning:The text was updated successfully, but these errors were encountered: