Differences between revisions 3 and 4
Revision 3 as of 2009-03-10 20:25:38
Size: 1433
Editor: was
Comment:
Revision 4 as of 2009-03-10 22:18:20
Size: 1513
Editor: was
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
Make it possible to use Sage *from* Macaulay2. Make it possible to use Sage *from* Macaulay2.  See http://trac.sagemath.org/sage_trac/ticket/5475 for something maybe useful.

Sage Days 14 projects

This is a list of projects suitable for Sage Days 14. Feel free to add your favourite ideas/wishes, and to put your name down for something you're interested in (you'll need to get an account on the wiki to do this). The projects can be about Sage, or Macaulay2, or both.

Create an interface from Macaulay2 to Sage

Make it possible to use Sage *from* Macaulay2. See http://trac.sagemath.org/sage_trac/ticket/5475 for something maybe useful.

Improve robustness of the Sage/Macaulay2

See http://trac.sagemath.org/sage_trac/ticket/5467

Improve Sage visualisation capabilities

People: Alex Ghitza,

There is good 2d plotting infrastructure, and nicely developing 3d plotting. We should attach this functionality to algebraic curves, surfaces, etc.

Documentation for algebraic geometry code in Sage

People: Alex Ghitza,

Go through schemes/* and add docstrings and doctests everywhere they're missing. This is a good project for becoming familiar with the Sage code; it is also sorely needed.

Hierarchy of algebraic-geometric objects in Sage

People: Alex Ghitza,

This is about infrastructure and long-term plans. We need to look at the existing hierarchy, figure out which high-level objects are missing and think about the best ways to organise them. (Example: do we want a "coherent sheaf" object in Sage? how would we implement it?) I'll try to touch upon some of these issues in my talk.

days14/projects (last edited 2009-03-12 20:28:31 by MikeHansen)