TODO: try to avoid a dependency on numpy in the test suite.

[dunshire.git] / TODO

diff --git a/TODO b/TODO
index 1a67a6f867d5fa5d3bfd14b3a7fec0500392a318..d0c0bf980f5bc1cc3ffba2dc1f0a1beb30d72147 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,22 +1,13 @@
-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.
+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.
 
-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. 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. Remove the one use of numpy.matrix in a doctest, since that's
+   an annoying dependency to have just to run the test suite.