Use the DEBUG_FLOAT_FORMAT when printing exception details.

[dunshire.git] / TODO

diff --git a/TODO b/TODO
index 1a67a6f867d5fa5d3bfd14b3a7fec0500392a318..2fe7ea4eab6b3fc44b571c8dcdb1272c6a4e153e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,22 +1,12 @@
-1. Add unit testing for crazier things like random invertible matrices.
+1. Make it work on a cartesian product of cones in the correct order.
 
-2. Copy the intro from my thesis into README.rst, and add a section
-   explaining the CVXOPT formulation.
-
-3. Try to eliminate the code in matrices.py.
-
-4. Make it work on a cartesian product of cones in the correct order.
-
-5. Make it work on a cartesian product of cones in the wrong order
+2. Make it work on a cartesian product of cones in the wrong order
    (apply a perm utation before/after).
 
-6. Rename all of my variables so that they don't conflict with CVXOPT.
-   Maybe x -> xi and y -> gamma in my paper, if that works out.
-
-7. Make sure we have the dimensions of the PSD cone correct.
+3. Make sure we have the dimensions of the PSD cone correct.
 
-8. Come up with a fast heuristic (like making nu huge and taking e1 as
+4. Come up with a fast heuristic (like making nu huge and taking e1 as
    our point) that finds a primal feasible point.
 
-9. We only need to include the API docs for dunshire.games in the
-   "user manual;" everything else can go in an appendix.
+5. Add a test to ensure that if we solve the same game twice, we get the
+   same answer back.