X-Git-Url: https://gitweb.michael.orlitzky.com/?a=blobdiff_plain;f=TODO;h=783d4a9d4136683d9da2b39d7d11c2100314bcdc;hb=27226106ec54fd64292c8fc963cdd7aea22d2b8a;hp=2ab222a2b67343296257558f3ed45a7d58841093;hpb=a843cd2917655c9a0a151d03d2a76e02d0f18a85;p=dunshire.git

diff --git a/TODO b/TODO
index 2ab222a..783d4a9 100644
--- a/TODO
+++ b/TODO
@@ -1,25 +1,24 @@
-1. Add doctests for simple examples like the ones in Dr. Gowda's paper
-   and the identity operator.
+1. Add unit testing for crazier things like random invertible matrices.
 
-2. Add unit testing for crazier things like random invertible matrices.
+2. Copy the intro from my thesis into README.rst, and add a section
+   explaining the CVXOPT formulation.
 
-3. Test that the primal/dual optimal values always agree (this implies
-   that we always get a solution).
+3. Try to eliminate the code in matrices.py.
 
-4. Run the tests with make test.
+4. Make it work on a cartesian product of cones in the correct order.
 
-5. Use pylint or whatever to perform static analysis.
-
-6. Add real docstrings everywhere.
+5. Make it work on a cartesian product of cones in the wrong order
+   (apply a perm utation before/after).
 
-7. Try to eliminate the code in matrices.py.
+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.
 
-8. Make it work on a cartesian product of cones in the correct order.
+7. Make sure we have the dimensions of the PSD cone correct.
 
-9. Make it work on a cartesian product of cones in the wrong order
-   (apply a perm utation before/after).
+8. Use a positive tolerance when comparing floating point numbers.
 
-10. Add (strict) cone containment tests to sanity check e1,e2.
+9. Come up with a fast heuristic (like making nu huge and taking e1 as
+   our point) that finds a primal feasible point.
 
-11. 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.
+10. We only need to include the API docs for dunshire.games in the
+    "user manual;" everything else can go in an appendix.