Differences between revisions 23 and 24
Revision 23 as of 2007-02-17 11:09:45
Size: 1778
Editor: 12
Revision 24 as of 2007-02-17 18:57:21
Size: 1808
Editor: c-24-18-159-112
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 * [:days3/sprints/3d: Tom Boothby: 3d object arithmetic / integration with tachyon]  * [:days3/sprints/3d: Tom Boothby/Robert Bradshaw/Robert Miller: 3d object arithmetic / integration with tachyon]

Sage Days 3 Coding Sprints

List your ideas for coding sprints here.

  1. [:days3/sprints/sparsenumerical: Josh Kantor: Sparse numerical linear algebra]
  2. [:days3/sprints/pippenger: Tom Boothby: Pippenger's Algorithm for fast multivariate polynomial evaluation]
  3. [:days3/sprints/exactlinalg: William Stein: Optimized exact sparse and dense linear algebra (especially for computing modular forms)]
  4. [:days3/sprints/flint: David Harvey (+ possibly Martin Albrecht): multithreaded polynomial arithmetic in FLINT]
  5. [:days3/sprints/roe: David Roe: p-adics (extension fields) (David Harvey would like to help with this)]
  6. [:days3/sprints/3d: Tom Boothby/Robert Bradshaw/Robert Miller: 3d object arithmetic / integration with tachyon]
  7. [:days3/sprints/objconst: David Harvey: would like to experiment further with speeding up object construction]
  8. [:days3/sprints/dsage: Yi Qiang: improve user interface for dsage, get rid of dsage_console.py, implement SQLite backend, remove server side pickling/unpickling. ]
  9. [:days3/sprints/Supersingular: Iftikhar Burhanuddin: Investigte memory leaks associated to SupersingularModule code.]

  10. [:days3/sprints/examples: William Stein: Revamp the SAGE_ROOT/examples directory so it is better documented and automatically tested.]


It would be very good to do the following for each sprint project (on a separate page linked to from above).

  1. create a specific detailed realistic list of goals.
  2. list every possible problem they can think of that might cause problems for (a)
  3. how many people are needed to do a)
  4. background reading material that sprinters should look at (this could be papers or source code).
  5. list anything else that could go wrong, and ways to deal with it.

days3/sprints (last edited 2008-11-14 13:42:05 by localhost)