Yo,

> Nope. It was just a report that the long doctest fails.

Well in this case the fix is straightforward: add a "# tol" wherever it breaks

> But questions:
> - is the coin-or answer reasonable?
> - should we increase the tolerance in that particular place?

Coin's answers always contain a lot of noise. I don't see anything
wrong with a "# tol" if the only problem is with the 10th decimal or
something.

> Might be useful.

I was convinced that I had written this somewhere in the doc and did
not find anything, but I actually wrote it "a bit better" in a
function:

http://www.sagemath.org/doc/reference/numerical/sage/numerical/backends/generic_backend.html#sage.numerical.backends.generic_backend.default_mip_solver

Nathann

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to