dunshire/games.py: don't require numpy to run the doctests.

[dunshire.git] / TODO

diff --git a/TODO b/TODO
index 27da26fc1c5535d5d99b046eaa2c4a48b19fc493..94690840107c6dd0dd8613fb450b9f4b3121f7aa 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,29 +1,10 @@
-1. Add unit testing for crazier things like random invertible matrices.
+1. Implement the SPD cone.
 
-2. Copy the intro from my thesis into README.rst, and add a section
-   explaining the CVXOPT formulation.
+2. Make it work on a cartesian product of cones in the correct order.
 
-3. Try to eliminate the code in matrices.py.
+3. Make it work on a cartesian product of cones in the wrong order
+   (apply a permutation before/after).
 
-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
-   (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.
-
-8. Use a positive tolerance when comparing floating point numbers.
-
-9. Come up with a fast heuristic (like making nu huge and taking e1 as
-   our point) that finds a primal feasible point.
-
-10. We only need to include the API docs for dunshire.games in the
-    "user manual;" everything else can go in an appendix.
-
-11. The ice cream cone tests sometimes fail. It can happen that we get
-    an "unknown" back from CVXOPT, or simply that we don't get the
-    expected answer in self.assertTrue(abs(first - second) <
-    options.ABS_TOL).
+4. Add random_game() and use it to replace all of the tests where
+   the cone is irrelevant. This should be done only after we are
+   feature complete and sure that everything works.