Differences between revisions 1 and 11 (spanning 10 versions)
⇤ ← Revision 1 as of 2007-05-07 00:32:30 →
Size: 1305
Editor: anonymous
Comment:
← Revision 11 as of 2007-12-18 23:02:57 → ⇥
Size: 2197
Editor: MichaelAbshoff
Comment: add 2.9 release, FreeBSD port
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Hello, I study math at the University of Dortmund. Most of the time I spend with SAGE is dedicated to making it work better on Windows using cygwin. Hello, I study math at the University of Dortmund. Most of the time I spend with SAGE is dedicated around packages and their portability. I added valgrind support to Sage 2.8.3 and have been using various valgrind tools to investigate Sage's memory consumption.

I also recently become a release manager for Sage and I chaired a number of releases: 2.8.11, 2.8.13-2.8.15 and 2.9. Since it looks like few people want to do this job it is very likely that I will do a lot more of those.
Line 6: Line 8:
Line 7: Line 10:
 * Probably chairing the current Sage release
 * Solaris port of SAGE.
 * FreeBSD port of SAGE.
Line 8: Line 14:
 * MSI Windows installer
 * Cygwin port of SAGE, build tests and small compilation fixes		  * optional spkgs: CoCoA 4.7.x, ApCoCoALib & CoCoALib, g++ 4.2
 * hunt mem-leaks in C/C++ code of Sage
 * DebianSAGE
 * whatever else currently needs fixing
Line 11: Line 20:
 * [:windows:port Sage to Windows]
 * build unified Setup.py for gdmodule - less important now due to drop of the Cygwin drop (officially)
Line 15: Line 26:
Line 17: Line 29:
Line 20: Line 33:
Line 21: Line 35:
 * FIXME  * See the Changelog, the google groups sage-devel and sage-support and #sage-devel on freenode.
Line 26: Line 40:
 * Porting mathematical open source code to Solaris, Windows and any odd Unix out there.
Line 32: Line 47:
 * #sage-devel on freenode

----
CategoryHomepage

Michael Abshoff's Wiki SAGE page

Hello, I study math at the University of Dortmund. Most of the time I spend with SAGE is dedicated around packages and their portability. I added valgrind support to Sage 2.8.3 and have been using various valgrind tools to investigate Sage's memory consumption.

I also recently become a release manager for Sage and I chaired a number of releases: 2.8.11, 2.8.13-2.8.15 and 2.9. Since it looks like few people want to do this job it is very likely that I will do a lot more of those.

Task Table

Currently Working on

  • Probably chairing the current Sage release
  • Solaris port of SAGE.
  • FreeBSD port of SAGE.
  • DMG installation image for MacOSX

  • optional spkgs: CoCoA 4.7.x, ApCoCoALib & CoCoALib, g++ 4.2

  • hunt mem-leaks in C/C++ code of Sage
  • DebianSAGE
  • whatever else currently needs fixing

Short Term

  • [:windows:port Sage to Windows]
  • build unified Setup.py for gdmodule - less important now due to drop of the Cygwin drop (officially)
  • multivariate polynomial arithmetic via CoCoALib
  • computation of approximate vanishing ideals via ApCoCoALib (needs multivariate polynomial arithmetic via CoCoALib)
  • check targets for various SAGE packages like gmp and linbox
  • make all packages using BLAS/Lapack use the Accelerate Framework on MacOSX. Patch for Linbox exists and will hopefully show up in Linbox svn soon

Long Term

  • F4/F5 in CoCoALib with interface to SAGE

Interesting Ideas

  • port SAGE code to MinGW/MSVC - probably done when hell freezes over - but one can at least dream.
  • fix pari issue on cygwin - details FIXME

Done Tasks

  • See the Changelog, the google groups sage-devel and sage-support and #sage-devel on freenode.

Other Software Interests

  • Windows gmp port
  • Linbox with MSVC
  • Porting mathematical open source code to Solaris, Windows and any odd Unix out there.

Places where I can be found

CategoryHomepage

MichaelAbshoff (last edited 2009-05-04 13:13:24 by MichaelAbshoff)