Differences between revisions 159 and 177 (spanning 18 versions)
Revision 159 as of 2012-07-30 06:26:03
Size: 8871
Editor: tscrim
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 5: Line 5:
In practice, Sage-combinat is a collection of experimental patches (i.e. extensions) on top of [[http://www.sagemath.org/|Sage]], developed by a community of researchers. The intent is that most of those patches 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. In practice, Sage-combinat is a collection of extensions on top of [[http://www.sagemath.org/|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.
Line 15: Line 15:
 * April 7-11, 2014 [[http://wiki.sagemath.org/days57|Sage(-Combinat) Days 57]], Cernay
Line 17: Line 19:
 * [[https://combinat.sagemath.org:8080|Experimental Sage notebook with the Sage-Combinat patches applied]]

 * 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]]

== Past news ==

 * November 4-8, 2013 [[http://wiki.sagemath.org/days54|Sage(-Combinat) Days 54]], University of California at Davis, USA
   Organized by Dan Bump, Anne Schilling and Travis Scrimshaw

 * June 17-21, 2013 [[combinat/FPSAC13|Sage(-Combinat) days 49]], in Orsay as satellite event to [[http://www.liafa.jussieu.fr/fpsac13/|FPSAC'13]]
   Organized by Alejandro Morales, Anne Schilling, Nicolas M. Thiery
Line 18: Line 34:

 * February 11-15, 2013 [[http://icerm.brown.edu/sp-s13/|Sage Days: Multiple Dirichlet Series, Combinatorics, and Representation Theory]], ICERM, Brown, USA
   Organized by Franco Saliola, Anne Schilling, Nicolas M. Thiery

 * January 21-25, 2013 [[http://www.aimath.org/ARCC/workshops/onlinedata.html|Online Databases:from L-functions to combinatorics]], Edinburgh
   Organized by Paul-Olivier DeHaye, Nicolas M. Thiery.
Line 22: Line 44:

== Past news ==
   Organized by Gregg Musiker, Franco Saliola, Anne Schilling, Nicolas M. Thiery.
Line 36: Line 57:
   Organized by Eva Curry and Hugh Thomas.
Line 43: Line 65:
   It includes several Sage and Sage-Combinat sessions    It includes several Sage and Sage-Combinat sessions.
   Organized by Anne Schilling and Mike Zabrocki.
Line 87: Line 110:
 * [[combinat/CiteSageCombinat|Cite Sage-Combinat]] when you use it for research publications.

 * Plume's review pages on Sage-Combinat: [[http://www.projet-plume.org/en/relier/sage-combinat-0|English]] and [[http://www.projet-plume.org/fr/relier/sage-combinat|French]]

 * [[http://combinat.sagemath.org/misc/raw-file/tip/articles/2013-01-17-Poster/main.pdf|Sage-Combinat's poster]]

 * [[combinat/CoolPictures|Cool pictures we produced with Sage-Combinat for our research]]
Line 102: Line 133:
 * [[combinat/CiteSageCombinat|Cite Sage-Combinat]] when you use it for research publications.
 * Plume's review pages on Sage-Combinat: [[http://www.projet-plume.org/en/relier/sage-combinat-0|English]] and [[http://www.projet-plume.org/fr/relier/sage-combinat|French]]
 * [[combinat/CoolPictures|Cool pictures we produced with Sage-Combinat for our research]]
Line 108: Line 135:
 * The collection of patches is managed using a [[http://combinat.sagemath.org/patches/|patch server]] (mercurial queues). Use it to try out the latest experimental features, or contribute your own patches! The Sage-Combinat extensions used to be managed as a collection of
patches on our [[http://combinat.sagemath.org/patches/|patch server]],
using a so-called mercurial queue. Since Sage 6.0, the
[[http://trac.sagemath.org/wiki/QuickStartSageGit|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.

 * [[http://trac.sagemath.org/query?status=closed&component=combinatorics&or&status=closed&cc=~sage-combinat&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&order=priority|Closed tickets related to combinatorics]]
 * [[http://trac.sagemath.org/query?status=needs_info&status=needs_review&status=needs_work&status=positive_review&component=combinatorics&or&status=needs_info&status=needs_review&status=needs_work&status=positive_review&cc=~sage-combinat&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&order=priority|In-progress tickets related to combinatorics]]

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)