Differences between revisions 173 and 177 (spanning 4 versions)
Revision 173 as of 2014-02-06 13:45:55
Size: 11087
Editor: nthiery
Comment:
Revision 177 as of 2014-02-19 17:15:49
Size: 11386
Editor: nthiery
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Sage-Combinat = = Sage-Combinat: enhancing Sage as a toolbox for computer exploration in algebraic combinatorics =
Line 21: Line 21:
 * A new [[http://combinat.sagemath.org/misc/raw-file/tip/articles/2013-01-17-Poster/main.pdf|poster]] for Sage-Combinat!  * A new [[http://combinat.sagemath.org/misc/raw-file/tip/articles/2013-01-17-Poster/main2014.pdf|poster]] for Sage-Combinat!

 * [[http://wiki.sagemath.org/TentativeConventions|Help for new Git workflow]]
Line 26: Line 28:
   Organized by Dan Bump, Anne Schilling and Travis Scrimshaw
Line 28: Line 31:
   Organized by Alejandro Morales, Anne Schilling, Nicolas M. Thiery
Line 32: Line 36:
   Organized by Franco Saliola, Anne Schilling, Nicolas M. Thiery.    Organized by Franco Saliola, Anne Schilling, Nicolas M. Thiery

Sage-Combinat: enhancing Sage as a toolbox for computer exploration in algebraic combinatorics

Sage-Combinat is a software project whose mission is: to improve the open source mathematical system Sage as an extensible toolbox for computer exploration in (algebraic) combinatorics, and foster code sharing between researchers in this area.

In practice, Sage-combinat is a collection of extensions on top of Sage, developed by a community of researchers. The intent is that most of those extensions get eventually integrated into Sage as soon as they are mature enough, with a typical short life-cycle of a few weeks. In other words: just install Sage, and you will benefit from all the Sage-combinat development, except for the latest bleeding edge features.


Installation instructions


NEWS

Past news


Who are we? What is Sage-Combinat used for?


How to participate and contribute

Communication

Code

The Sage-Combinat extensions used to be managed as a collection of patches on our patch server, using a so-called mercurial queue. Since Sage 6.0, the development workflow has been reworked in depth, and we are in the progress of migrating the extensions as git branches.

Quite some stuff below is thus outdated, and will be progressively replaced by information on the new workflow.

Design

Documentation

combinat (last edited 2022-04-05 01:35:07 by mkoeppe)