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 c6e5c4cb079edfc7149ee8179137fb7f61975e84..719d7f2228a19e72aa52569fec4f88a9117668a7 100644 (file)
--- a/dunshire/options.py
+++ b/dunshire/options.py
@@ -9,9 +9,20 @@ 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
 """
 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``, and we need a little bit of padding on top of that.
+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'
 """
 
 FLOAT_FORMAT = '%.7f'
 """