Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-04-13 Thread Christian Stump
Salut Nicolas, I was just brainstorming of how to use PairwiseCompatibleSubsets to construct not only antichains but also chains and multichains in posets. It might be a good optional argument fixing a given size, or fixing a given maximal size of subsets. chains of a given length then become stra

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-04-13 Thread Christian Stump
> There is also a bug to fix in HasseDiagram. Maybe I add another patch > after 10998, that's easier to review then... I added another patch doing this after 10998, its number is 11187. I like the facade option for posets, I use it in the finite reflection group code for constructing the noncross

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-04-13 Thread Christian Stump
> Otherwise I would change this and add it to my review patch... There is also a bug to fix in HasseDiagram. Maybe I add another patch after 10998, that's easier to review then... -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post t

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-04-13 Thread Christian Stump
Salut Nicolas, I was just creating some lattices and saw that LatticePoset does not take the same input as Poset. Have you touched the patch these days? Otherwise I would change this and add it to my review patch... Best, Christian -- You received this message because you are subscribed to the

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-04-04 Thread Nicolas M. Thiery
On Mon, Apr 04, 2011 at 10:45:23AM -0400, Christian Stump wrote: > Hi Nicolas, > > > thanks, Nicolas, for all the work! I gonna look at it as soon as I > > find some time, say until the end of next week... > > after applying #10651 (empty set), #9065 (facade sets), #10938 > (Set-issubset), #8288

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-04-04 Thread Christian Stump
Hi Nicolas, > thanks, Nicolas, for all the work! I gonna look at it as soon as I > find some time, say until the end of next week... after applying #10651 (empty set), #9065 (facade sets), #10938 (Set-issubset), #8288 (search forest), the poset patch #10998 has a reject in categories/all.py, it d

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-28 Thread Christian Stump
> So that's a call for volunteers for reviewing it. Christian, Frédéric, > are you still up for that? What's your time line? thanks, Nicolas, for all the work! I gonna look at it as soon as I find some time, say until the end of next week... Best, Christian -- You received this message because

[sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-28 Thread Nicolas M. Thiery
Dear Poset fans, My patch is now under "needs review": http://trac.sagemath.org/sage_trac/ticket/10998 So that's a call for volunteers for reviewing it. Christian, Frédéric, are you still up for that? What's your time line? Cheers, Nicolas -- Nicolas M. T

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-24 Thread Nicolas M. Thiery
On Thu, Mar 24, 2011 at 09:24:19AM +0100, Martin Rubey wrote: > Are libraries somewhat similar in spirit to the method .an_element? Nothing has been formalized about them. But yeah, graphs, digraphs, posets, species all have a role between "collection of examples" (similar in spirit to an_element(

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-24 Thread Martin Rubey
"Nicolas M. Thiery" writes: > How does this all sound? Very nice! Martin -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send e

[sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-24 Thread Nicolas M. Thiery
Hi Poset fans, I just recalled that there already exists two categories PartialyOrderedSets and PartialyOrderedMonoids, with aliases OrderedSets and OrderedMonoids. At this point, those categories are stubs, and are not used anywere in the Sage code. Since the terminology "Poset" (rather

Re: [sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-24 Thread Martin Rubey
Are libraries somewhat similar in spirit to the method .an_element? Martin -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send em

[sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-24 Thread Nicolas M. Thiery
Hi Rob! On Wed, Mar 23, 2011 at 09:47:34AM -0700, Rob Beezer wrote: > The only advantage I could see to uppercase would be if every category > *automatically* came with the infrastructure for collections. This triggers my curiosity. Do you have some specific features you would dream of ab

[sage-combinat-devel] Re: [sage-devel] Re: Refactoring of posets

2011-03-23 Thread Nicolas M. Thiery
On Wed, Mar 23, 2011 at 12:54:13PM -0400, David Roe wrote: > I have another little conflict in that the name Posets is, since > recently, used for the library of posets: > > sage: Posets.ChainPoset(3) > Finite lattice containing 3 elements > > very much like graphs