On Jan 9, 3:58 am, "Nicolas M. Thiery" <nicolas.thi...@u-psud.fr>
wrote:
> On Sat, Jan 09, 2010 at 10:53:30AM +0100, Vincent Delecroix wrote:
> > I get the following with sage-4.3, is it normal to have [2, 1] and [1,
> > 2] as partitions ?
>
> > {{{
> > sage: for p in Partitions(3, max_slope=1):
> > ....: print p
> > ....:
> > [3]
> > [2, 1]
> > [1, 2]
> > [1, 1, 1]
> > }}}
>
> Well, that's consistent with max_slope=1. Did you mean max_slope=-1?
> Of course, it would have been nicer to get an error (since the highest
> meaningful max_slope for a partition is 0). Hopefully we will be able
> to do that when the IntegerListsLex kernel will be rewritten
> (volunteers for that welcome!).
While we're on this topic, here's a bug which I don't know if anyone
has worked on recently: compare
sage: Partitions(4, max_slope=-1).list()
[[4], [3, 1]]
to
sage: Partitions(4, max_slope=-1, length=3).list() # doesn't work
[[2, 1, 1]]
See <http://trac.sagemath.org/sage_trac/ticket/6538>.
--
John
--
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-de...@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.
