Skip to content
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

Closed
dcoudert opened this issue Feb 19, 2018 · 15 comments
Closed

add parameter solver to method chromatic_number #24782

dcoudert opened this issue Feb 19, 2018 · 15 comments

Comments

@dcoudert
Copy link
Contributor

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

@dcoudert dcoudert added this to the sage-8.2 milestone Feb 19, 2018
@dcoudert
Copy link
Contributor Author

Branch: public/24782_chromatic_number

@dcoudert
Copy link
Contributor Author

comment:1

No need to add specific extra tests since the solver parameter is tested in method vertex_coloring.


New commits:

820526dtrac #24782: add parameter solver to chromatic_number

@dcoudert
Copy link
Contributor Author

Commit: 820526d

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Mar 13, 2018

Changed commit from 820526d to 626660e

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Mar 13, 2018

Branch pushed to git repo; I updated commit sha1. New commits:

626660etrac #24782: Merged with 8.2.beta8

@tscrim
Copy link
Collaborator

tscrim commented Mar 14, 2018

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.

@tscrim
Copy link
Collaborator

tscrim commented Mar 14, 2018

Reviewer: Travis Scrimshaw

@jm58660
Copy link
Mannequin

jm58660 mannequin commented Mar 14, 2018

comment:4

A sidenote: Should we test for a combination of solver != None and algorithm != 'MILP'? At least it is not important, so don't bother with it on this ticket.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Mar 14, 2018

Branch pushed to git repo; I updated commit sha1. New commits:

dcab836trac #24782: improve links in documentation

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Mar 14, 2018

Changed commit from 626660e to dcab836

@dcoudert
Copy link
Contributor Author

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.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 13, 2018

Changed commit from dcab836 to 9266636

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 13, 2018

Branch pushed to git repo; I updated commit sha1. New commits:

9266636trac #24782: Merged with 8.3.beta0

@dcoudert dcoudert modified the milestones: sage-8.2, sage-8.3 May 13, 2018
@tscrim
Copy link
Collaborator

tscrim commented May 13, 2018

comment:9

Sorry, forgot about this. LGTM.

@vbraun
Copy link
Member

vbraun commented May 15, 2018

Changed branch from public/24782_chromatic_number to 9266636

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants