-
Notifications
You must be signed in to change notification settings - Fork 181
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
Add documentation page listing and naming available solvers? #1915
Comments
There is already some information on Solution-algorithms
This isn't necessary, as these are three wholly distinct solution techniques for LP. Variants within these techniques are
No, "Dual simplex" is a variant of the simplex algorithm, but "PDLP" is a first order method. I've realised that Solution-algorithms doesn't say anything about what PDLP is, so I'll add that, stressing that PDLP is currently only available for CPUs, and may be totally uncompetitive.
Yes, and much progress has been made on the most challenging part of the development. We could make a prototype serial version available soon - that may be significantly faster than the current IPM solver on some problem classes. However, a full parallel implementation is unlikely to be available within the next 12 months. |
Closed by #1916 |
Thanks a lot for the feedback and PR #1916. I've made a minor Markdown syntax correction in #1939. Overall PR #1916 is fine to me, except that now that there are links from the solvers explanation page to the options solver and simplex_strategy, I would also add the matching back-links from these options to the solvers explanation page. Also perhaps add "see also simplex_strategy" in the "solver" option |
Hello,
I wonder whether it may be useful to add a documentation page listing the available solvers in HiGHS. In particular, this may clarify some aspects:
simplex
,ipm
andpdlp
) used in thesolver
setting option https://ergo-code.github.io/HiGHS/dev/options/definitions/#solverpdlp
? (seems yes from previous discussion)The text was updated successfully, but these errors were encountered: