Opened 15 months ago
Closed 6 months ago
#14581 closed defect (fixed)
GLPK incorrectly handles zero bounds
Reported by: | novoselt | Owned by: | ncohen |
---|---|---|---|
Priority: | major | Milestone: | sage-6.1 |
Component: | linear programming | Keywords: | |
Cc: | Merged in: | ||
Authors: | Nathann Cohen | Reviewers: | Volker Braun |
Report Upstream: | N/A | Work issues: | |
Branch: | u/ncohen/14581 (Commits) | Commit: | 6789698aa1905f5d531df707e455e62a651913f4 |
Dependencies: | Stopgaps: |
Description
sage: P = MixedIntegerLinearProgram() sage: x = P["x"] sage: P.set_max(x, 0) sage: print P.get_max(x) None
The problem is that GLPK backend has value = False default parameter with a test value == False later on and zero is equal to false. None has to be used instead!
Change History (7)
comment:1 Changed 15 months ago by novoselt
comment:2 Changed 12 months ago by jdemeyer
- Milestone changed from sage-5.11 to sage-5.12
comment:3 Changed 8 months ago by ncohen
- Branch set to u/ncohen/14581
- Status changed from new to needs_review
Here it is ! :-)
I'll never write == False again :-P
Nathann
comment:4 Changed 8 months ago by git
- Commit set to 6789698aa1905f5d531df707e455e62a651913f4
comment:5 Changed 6 months ago by vbraun
- Reviewers set to Volker Braun
- Status changed from needs_review to positive_review
comment:6 Changed 6 months ago by ncohen
THaaaaaaaaaaaanks !!
Nathann
comment:7 Changed 6 months ago by vbraun
- Resolution set to fixed
- Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
Why are there "numerical" and "linear programming" components?.. "numerical" always confused me as a choice for the directory name...