On 3/23/11 9:34 AM, Martin Rubey wrote:
"Nicolas M. Thiery"<nicolas.thi...@u-psud.fr>  writes:

        Dear poset fans,

In the process of refactoring / categorifying the poset code, I am
creating a category for posets which are lattices. What should be the
name for this category? Lattices() would be natural, but might get
into conflict with other kind of lattices. Should we use
LatticePosets() instead?

I like LatticePosets or perhaps LatticeOrders.

Yes, LatticePosets seems fine.

> Arr, sorry, I actually meant 1. For my penance a concrete example to
> think about::
>
>    sage: P = Poset((Subsets(2), attrcall("issubset")))
>
> Option (1):
>
>    sage: P.hasse_diagram().edges()
>    [({}, {2}, None), ({}, {1}, None), ({2}, {1, 2}, None), ({1}, {1, 2}, 
None)]
>    sage: P.hasse_diagram().__class__
>    <class 'sage.graphs.digraph.DiGraph'>
>
> Option (2):
>
>    sage: P.hasse_diagram().edges()
>    [(0, 1, None), (0, 2, None), (1, 3, None), (2, 3, None)]
>    sage: P.hasse_diagram().__class__
>    <class 'sage.combinat.posets.hasse_diagram.HasseDiagram'>

Ah, yes, it would be more user friendly to use the actual vertices of the poset 
rather
than numbers from 0,1,...,n-1. Does it matter that in one case the class is a
DiGraph and in the other a separate class?

Best,

Anne

--
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 email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.

Reply via email to