#20564: KleshchevPartitions
-------------------------------------+-------------------------------------
       Reporter:  andrew.mathas      |        Owner:  andrew.mathas
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-7.3
      Component:  combinatorics      |   Resolution:
       Keywords:  Kleshchev          |    Merged in:
  partition tuples                   |
        Authors:  Andrew Mathas      |    Reviewers:  Travis Scrimshaw
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  public/combinat/kleshchev_partitoins-20564|  
deeae1f2545ac91b3b9148ca612fe93f05f1eab0
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by andrew.mathas):

 Replying to [tscrim] (form email correspondence, but it should be on the
 ticket...):
 >The biggest problem I see is this:
 >
 > sage: P = KleshchevPartitions(3)  # direction = 'up' is the default IIRC
 > sage: regular_partition = P([4,4])   # I might be backwards on which is
 the correct direction for this, I forget offhand
 > sage: regular_partition in P
 > True
 > sage: P.options.order = 'down'  # This cannot change
 regular_partition...
 > sage: regular_partition in P   #  so this now fails
 > False
 >
 > Granted, I agree that I don't think anyone will really do this except by
 accidentally forgetting to set it beforehand, but it can cause subtle bugs
 (e.g., the multiplication convention for permutations option).
 This possibility had occurred to me but I thought to ignore it. What do
 you think of having simple_labelling as an option but making it possible
 to over ride this when calling KleshchevPartitions and then hard-wiring
 the choice into the class. So I am thinking:

     sage: KleshchevPartitions(3)
     regular Kleshchev partitions with e=3
     sage: KleshchevPartitions(3, labelling='restricted')
     restricted Kleshchev partitions with e=3

 My main aim was to get rid of the need to specify the convention in all of
 the (co)good, (co)normal, mullineux_map, ... methods You are likely to
 object to my removing the direction from these as well as with my current
 of the code the only way to get the previous functionality is with a
 kludge like:

     simple_labelling = Partitions.options.simple_labelling
     Partitions.options.simple_labelling='restricted'
     mu.good_nodes(3)
     Partitions.options.simple_labelling = simple_labelling

 I thought about giving GlobalOptions a context manager to make it possible
 to instead write

     with Partitions.options.simple_labelling:

         Partitions.options.simple_labelling='restricted'
         mu.good_nodes(3)

 but I am not sure if this is a good idea...

 Btw, with the default "direction" (simple_labelling is more meaningful I
 think), it used to be "down" but during the code revisions it seems to
 have changed to "up" in some places but not others (in particular the
 documentation). My preference for "restricted Kleshchev's" but I am not
 really fussed. What would you like to me to make it?

--
Ticket URL: <https://trac.sagemath.org/ticket/20564#comment:25>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to