Differences between revisions 22 and 73 (spanning 51 versions)
⇤ ← Revision 22 as of 2008-12-17 13:53:42 →
Size: 2318
Editor: NicolasThiery
Comment:
← Revision 73 as of 2009-05-10 08:27:23 → ⇥
Size: 5005
Editor: VincentDelecroix
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Sage-combinat = = Sage-Combinat =
Line 5: Line 5:
=== SageCombinat
Line 7: Line 6:
There will be a [[http:/combinat/SageCombinatWorkshopOrsay|Sage-Combinat Workshop]] in Orsay in January or February. ----
== NEWS ==
 * February 22-26, 2010: [[http://wiki.sagemath.org/daysmarseille|Sage days]]
   The thematic month [[https://www.lirmm.fr/arith/wiki/MathInfo2010/MathInfo2010|MathInfo 2010]] at CIRM, Marseille will include a Sage days session. FlorentHivert, NicolasThiéry, and FrancoSaliola will be among the organizers, there will be a serious combinatorics slant.
   
 * July 25-29, 2009: *-Combinat 2009
Line 9: Line 13:
=== NEWS: 2008-06-19: MuPAD-Combinat join forces with Sage ===    We will hold an International Sage Workshop on [[http:/combinat/FPSAC09|Free and Practical Software for Algebraic Combinatorics]] at RISC, Linz, Austria, right after [[http://www.risc.uni-linz.ac.at/about/conferences/fpsac2009/|FPSAC'09]]
Line 11: Line 15:
Sage-combinat was born as a partial port of [[http://mupad-combinat.sf.net|MuPAD-Combinat]]. After months of discussions and experiments, an enthusiastic consensus emerged in the MuPAD-Combinat community to join Sage. Sage-combinat henceforth became the natural successor of MuPAD-Combinat.  * April 15th, 2009: Software demonstration accepted for [[http://www.risc.uni-linz.ac.at/about/conferences/fpsac2009/|FPSAC'09]]
 [[attachment:2009-07-20-FPSAC.pdf|PDF]], [[attachment:.2009-07-20-FPSAC.tex|LaTeX Source]] [[attachment:2009-07-20-FPSAC.bbl|LaTeX bibliography]]
Line 13: Line 18:
The transition is going to be a massive investment: seven years of hard work to port over! However a lot of experience was gained since 2000, and most of the design is now pretty clear. By sharing the work the transition will hopefuly be relatively quick.  * January 26-30, 2009: [[http:/combinat/SageCombinatWorkshopOrsay|Sage-Combinat Workshop in Orsay]]
Line 15: Line 20:
See the [[http:/combinat/RoadMap|road map and current status]] of the port.  * 2008-06-19: MuPAD-Combinat join forces with Sage
Line 17: Line 22:
=== How to participate and contribute ===
 - Join our mailing list: http://groups.google.com/group/sage-combinat-devel.		     Sage-combinat was born as a partial port of [[http://mupad-combinat.sf.net|MuPAD-Combinat]]. After months of discussions and experiments, an enthusiastic consensus emerged in the MuPAD-Combinat community to join Sage. Sage-combinat henceforth became the natural successor of {{{MuPAD-Combinat}}}.
Line 20: Line 24:
 - Post bug reports, suggestion, patches on the [[http://sagetrac.org/sage_trac/milestone/sage-combinat|Sage-combinat trac server]] or on the [[http://groups.google.com/group/sage-combinat-devel|mailing list]].    The transition is going to be a massive investment: seven years of hard work to port over! However a lot of experience was gained since 2000, and most of the design is now pretty clear. By sharing the work the transition will hopefuly be relatively quick.
Line 22: Line 26:
 - The collection of patches is managed using a [[http://sage.math.washington.edu:2144/|patch server]] (mercurial queues). Use it to try out the latest experimental features, or contribute your own patches!    See the [[http://sagetrac.org/sage_trac/wiki/SageCombinatRoadMap|road map and current status]] of the port.
Line 24: Line 28:
  - [[http:/combinat/MercurialBasic|Basic instructions]] (in particular, how to '''download sage-combinat''') ----
Line 26: Line 30:
  - [[http:/combinat/Mercurial|Advanced instructions]]. == Who are we? ==
Line 28: Line 32:
 - Contribute to the list of [[http:/combinat/Weirdness|quirks and weirdness issues]] in the *-Combinat design;  * [[http:/combinat/Contributors|Contributors]]

 * [[http:/combinat/Institutions|Institutions and sponsors]]

----

== How to participate and contribute ==


=== Communication ===

 * Join our mailing lists:
    * Announcement mailing list (to come)
    * [[http://groups.google.com/group/sage-combinat-devel|sage-combinat-devel]]: Developpers mailing list
    * [[http://groups.google.com/group/sage-combinat-commits|sage-combinat-commits]]: A low traffic mailing list which receives an automatic notice whenever a sage-combinat related ticket is modified (and eventually whenever a commit is done on the patch server).
 * Check the [[http://sagetrac.org/sage_trac/wiki/SageCombinatRoadMap|road map and current status]]
 * Post bug reports, suggestions, patches on the [[http://sagetrac.org/sage_trac/milestone/sage-combinat|Sage-Combinat trac server]] or on the [[http://groups.google.com/group/sage-combinat-devel|mailing list]].
 
 * Cite Sage-Combinat when you use it for research publications (TODO: provide a standard citation here).

=== Code ===

 * 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! (You may still need to access to the [[http://sage.math.washington.edu:2144/|old patch server]])

 * Please read the [[http://wiki.sagemath.org/combinat/MercurialStepByStep|Step by step tutorial]] (in particular, how to '''download Sage-Combinat''')

 * For the curious: [[http://wiki.sagemath.org/combinat/Mercurial|Technical background on the Sage-Combinat patch server (messy)]].

 * For hg lovers: [[http://hgbook.red-bean.com/read/|Mercurial: The Definite Guide]] an e-book by Bryan O'Sullivan

 * [[http://combinat.sagemath.org/misc/file/|Mercurial server for miscelleanous files and documents]]
   To check them out, use {{{hg clone http://combinat.sagemath.org/misc/ Sage-Combinat-misc-file}}}. This will create a subdirectory {{{Sage-Combinat-misc-file}}} in the current directory; you can use any other name for this subdirectory.

=== Design ===

 * Have a look and participate to [[http:/combinat/DesignDiscussion|design discussions]].

 * Contribute to the list of [[http:/combinat/Weirdness|quirks and weirdness issues]] in the {{{*-Combinat}}} design.

=== Documentation ===

 * From sage 3.4 on, the documentation system is based on ReST/Sphinx. Here are some [[combinat/HelpOnTheDoc|help about the new doc system]]

Sage-Combinat

Sage-combinat is a collection of experimental patches (i.e. extensions) on top of Sage, developed by a community in algebraic combinatorics. Its main purpose is to improve Sage as an extensible toolbox for computer exploration, and foster code sharing between researchers in this area. The intent is that most of those patches eventually will get 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.

NEWS

Who are we?

How to participate and contribute

Communication

  • Join our mailing lists:
    • Announcement mailing list (to come)

    • sage-combinat-devel: Developpers mailing list

    • sage-combinat-commits: A low traffic mailing list which receives an automatic notice whenever a sage-combinat related ticket is modified (and eventually whenever a commit is done on the patch server).

  • Check the road map and current status

  • Post bug reports, suggestions, patches on the Sage-Combinat trac server or on the mailing list.

  • Cite Sage-Combinat when you use it for research publications (TODO: provide a standard citation here).

Code

Design

Documentation

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