Processing Math: Done
No jsMath TeX fonts found -- using unicode fonts instead.
This may be slow and might not print well.
Use the jsMath control panel to get additional information.
jsMath Control PanelHide this Message

jsMath
Differences between revisions 1 and 10 (spanning 9 versions)
⇤ ← Revision 1 as of 2007-02-12 20:55:22 →
Size: 188
Editor: anonymous
Comment:
← Revision 10 as of 2007-02-13 21:50:09 → ⇥
Size: 1013
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * Sparse numerical linear algebra  1. Josh Kantor: Sparse numerical linear algebra
Line 7: Line 7:
 * Pippenger's Algorithm for multivariate polynomial evaluation  * Tom Boothby: [http://cr.yp.to/papers/pippenger.pdf Pippenger's Algorithm] for multivariate polynomial evaluation
Line 9: Line 9:
 *  * William Stein: Optimized exact sparse and dense linear algebra (especially for computing modular forms)

 * David Harvey (+ possibly Martin Albrecht): multithreaded polynomial arithmetic in FLINT

 * David Roe: p-adics (extension fields)

 * Tom Boothby: 3d object arithmetic / integration with tachyon

== NOTE ==

It would be very good to do the following for each sprint project:
    1. create a specific detailed realistic list of goals.
    * list every possible problem they can think of that might cause problems for (a)
    * how many people are needed to do a)
    * background reading material that sprinters should look at (this could be papers or source code).
    * list anything else that could go wrong, and ways to deal with it.

Sage Days 3 Coding Sprints

List your ideas for coding sprints here.

  1. Josh Kantor: Sparse numerical linear algebra

  2. Tom Boothby: [http://cr.yp.to/papers/pippenger.pdf Pippenger's Algorithm] for multivariate polynomial evaluation

  3. William Stein: Optimized exact sparse and dense linear algebra (especially for computing modular forms)
  4. David Harvey (+ possibly Martin Albrecht): multithreaded polynomial arithmetic in FLINT
  5. David Roe: p-adics (extension fields)
  6. Tom Boothby: 3d object arithmetic / integration with tachyon

NOTE

It would be very good to do the following for each sprint project:

  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 anonymous)