#20323: Common TestSuite for MIP backends
-------------------------------------+-------------------------------------
Reporter: mkoeppe | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-7.2
Component: numerical | Resolution:
Keywords: lp | Merged in:
Authors: Matthias Koeppe | Reviewers: Thierry Monteil
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/mkoeppe/common_testsuite_for_mip_backends|
f40980646e129eeb501a51fd06e99eb98d83a4f3
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by mkoeppe):
Replying to [comment:32 dimpase]:
> I recall asking how one deals with different backends producing
different, albeit equivalent, outputs. E.g. some of them would even
introduce extra variables for some constraints (see e.g.
[http://trac.sagemath.org/ticket/13148#comment:2 here]). Some backends
assign names to constraints automatically.
Thanks for the pointer to that ticket. Yes, the tests need to be written
in a way that they accommodate the solvers.
--
Ticket URL: <http://trac.sagemath.org/ticket/20323#comment:37>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
