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 parameter solver to method chromatic_number #24782
Comments
Branch: public/24782_chromatic_number |
comment:1
No need to add specific extra tests since the New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:3
Nitpick, but you can just use -:meth:`solve <sage.numerical.mip.MixedIntegerLinearProgram.solve>`
+:meth:`~sage.numerical.mip.MixedIntegerLinearProgram.solve`
-:class:`MixedIntegerLinearProgram <sage.numerical.mip.MixedIntegerLinearProgram>`
+:class:`~sage.numerical.mip.MixedIntegerLinearProgram` Otherwise LGTM. You can set a positive review once fixed or if you want to just ignore. |
Reviewer: Travis Scrimshaw |
comment:4
A sidenote: Should we test for a combination of |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
I changed the links. However, I don't want to test the combination algorithm / solver. It's not done elsewhere (in general) and we can ignore the solver if we use another algorithm. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Sorry, forgot about this. LGTM. |
Changed branch from public/24782_chromatic_number to |
When
algorithm='MILP'
, we must be able to select the LP solver. This is not the case yet.CC: @jm58660
Component: graph theory
Author: David Coudert
Branch/Commit:
9266636
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/24782
The text was updated successfully, but these errors were encountered: