Hi Paul,

Thanks for this. I should have known about your patch but didn't. (I
thought that I had seen once but couldn't find in the patch queue...)

Ultimately I need multipartitions because they index representations
for cyclotomic (quiver) Hecke algebras and they label basis vectors
for highest weight modules of the affine special linear group -- which
the former categorify. For the time being I only really need standard
tableau of multipartition shape, which index bases for the Specht
modules of these algebras.

Mostly I need standard combinatorial properties of the
multipartitions, which relate to inducing and restricting the
corresponding modules and to the crystal graph structure of the
corresponding highest weight modules. There are some coinvariant
algebras hiding behind the scenes so your work which symmetric
polynomials might be interesting to me.

I'll download your patch and merge it with what I have been doing --
and get back to you with questions no doubt!

Cheers,
Andrew



On Jun 2, 11:53 am, Paul Bryan <pabr...@gmail.com> wrote:
> Hi Andrew. I began implementing a MultiPartitions class based on Partitions
> but other things took over. This Trac 
> tickethttp://trac.sagemath.org/sage_trac/ticket/10630has the relevant patch. 
> You
> may find this cuts out some of your work. I also had ideas for cleaning up
> Partitions but never quite got there either and so the multipartitions code
> I wrote may also need some modifications in line with your cleanup. I also
> was not at all interested in writing optimised code to begin with and the
> code needs much attention in that direction. Correctness first I always say!
>
> My main interest was in multi symmetric polynomials and functions for which
> I have some code, but not a lot.
>
> Since at least one other person is interested in multi partitions at least,
> I may be able to find some time to collaborate on this work. Could you
> (either on list of privately) share some of your thoughts/work so far?
>
> Also, is there still interest in multi-symmetric functions? I can certainly
> provide what I have so far and may find some time to work on the code again
> if there's interest.
>
> Cheers,
> Paul.
>
> On 2 June 2011 10:49, Andrew Mathas <a.mat...@usyd.edu.au> wrote:
>
>
>
>
>
>
>
> > Dear All,
>
> > I need to implement multipartitions and (standard) (multi)tableaux so
> > I am in the process of writing the relevant classes. While doing this
> > I have been testing Jason's tableaux patch and discovering a lot of
> > debris in partition.py which I'm cleaning up.
>
> > Please let me know what you think of the following.
>
> > 1. PartitionTuples() appears to be unused. The term "multipartition"
> > and is compatible with SkewMultipartition, so I propose depreciating
> > (or deprecating for my American friends:) these classes and creating
> > Multipartitions classes, which are parents, whose elements will belong
> > to the class Multipartition(). An element of  Multipartition() will be
> > CombinatorialClass-es which wrap lists of Partition_class().
>
> > 2.. Given the lack of enthusiasm to my previous suggestion of
> > overloading Tableau(),  StandardTableau() as the entry point for
> > constructing different tableaux classes I am now creating new classes
> > of Multitableaux() in multitableau.py. These tableaux will be wrapped
> > lists of tableau.
>
> > 3. Depreciate the following functions/classes in partition.py:
> >    deprecation('"partitions_set()" is deprecated. Use the
> > SetPartitions(S,k) instead')
> >    deprecation('"number_of_partitions_set()" is deprecated. Use the
> > SetPartitions(S,k).cardinality() instead')
> >    deprecation('"number_of_partitions()" is deprecated. Use the
> > Partitions(n).cardinality() or Compositions(n,k).cardinality()
> > instead')
> >    deprecation('"partitions()" is deprecated. Use the iterator from
> > Partitions() instead')
> >    deprecation('"ordered_partitions()" is deprecated. Use the
> > Compositions() instead')
> >    deprecation('"number_of_ordered_partitions()" is deprecated. Use
> > the Compositions().cardinality() instead')
> >    deprecation('"partitions_greatest()" is deprecated. Use
> > PartitionsGreatestLE(n,k).list() instead')
> >    deprecation('"partitions_greatest_eq()" is deprecated. Use
> > PartitionsGreatestEQ(n,k).list() instead')
> >    deprecation('"partitions_tuples()" is deprecated. Use
> > Multipartitions(n,k).list() instead')
> >    deprecation('"number_of__partition_tulpes()" is deprecated. Use
> > Multipartitions(n,k).cardinality() instead')
> >    deprecation('"power_partition()" is deprecated. Use
> > Partition(pi).power(k) instead')
>
> > 4. Remove all of the code in partition.py that was depreciated in
> > 2009.
>
> > My plan is post these changes as two patches, one cleaning up the
> > partition.py code and creating multipartitions and the other creating
> > multitableaux. Alternatively, I could do this as three patches: create
> > multipartitions, clean up partitions and then implement multitableaux.
>
> > Please let me know what you think of these.
>
> > Finally, an unrelated question:  does sage have nice class for
> > wrapping tables, or labelled matrices? As far as I can see it doesn't.
> > The labelled tables that I am thinking specifically are for wrapping
> > decomposition matrices, or formal characters but they could be used
> > equally well for character tables, multiplication tables and so on.
> > Thomas Breuer and Frank Lübeck  have a very nice interface
> > "browse" (seehttp://www.math.rwth-aachen.de/~Browse/) for doing this
> > inside Gap4. A similar object in sage would be nice...
>
> > Cheers,
> > Andrew
>
> > --
> > 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.

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