Add a new DEBUG_FLOAT_FORMAT and use it when raising game exceptions.

[dunshire.git] / dunshire / options.py

diff --git a/dunshire/options.py b/dunshire/options.py
index 2a57e270e6763ba087d361bb0d81e7f57bd0d5d4..719d7f2228a19e72aa52569fec4f88a9117668a7 100644 (file)
--- a/dunshire/options.py
+++ b/dunshire/options.py
@@ -5,14 +5,24 @@ change them. But this makes the user interface real simple.
 """
 
 
-ABS_TOL = 1e-7
+ABS_TOL = 1e-6
 """
 The absolute tolerance used in all "are these numbers equal" and "is
 this number less than (or equal to) that other number" tests. The CVXOPT
-default is ``1e-7``, so we use that. Where we need to be more lenient,
-we'll have to adjust it.
+default is ``1e-7``, but loosening that a little reduces the number of
+"unknown" solutions that we get during random testing. Whether or not it
+improves the solubility of real problems is a question for the
+philosophers.
 """
 
+DEBUG_FLOAT_FORMAT = '%.20f'
+"""
+The float output format to use when something goes wrong. If we need to
+produce a random test case, for example, then we need all of the digits
+of the things involved. If we try to recreate the problem using only,
+say, the first seven digits of each number, then the resulting game
+might not reproduce the failure.
+"""
 
 FLOAT_FORMAT = '%.7f'
 """