Changes between Version 10 and Version 12 of Ticket #13072
 Timestamp:
 08/29/12 04:57:15 (8 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

Ticket #13072 – Description
v10 v12 9 9 The idea is to implement a fully function class for PartitionTuples as I currently need this together with a class for tuples of (standard) tableaux (coming soon). 10 10 11 PartitionTuples of level 1 are in natural bijection with Partitions so when given a 1tuple of partitions or a partitionPartitionTuples() returns the corresponding Partition. This works almost seamlessly, making it possible to almost ignore the distinction between Partitions() and PartitionTuples(). One exception is that the expected behaviour of11 PartitionTuples of level 1 are in natural bijection with Partitions so when given a 1tuple of partitions, or a partition, PartitionTuples() returns the corresponding Partition. This works almost seamlessly, making it possible to almost ignore the distinction between Partitions() and PartitionTuples(). One exception is that the expected behaviour of 12 12 13 13 {{{ 14 14 for component in mu: 15 15 do X 16 }}} 16 17 17 }}} 18 is different for partitions and partition tuples (in the first case, you expect to loop over the pars of the partition and in the second over the component of the tuple). To get around this both classes now have a components() method so that you can uniformly write 18 is different for partitions and partition tuples (in the first case, you expect to loop over the parts of the partition and in the second over the components of the tuple). To get around this both classes now have a components() method so that you can uniformly write 19 19 20 20 {{{ … … 29 29 PartitionTuples(level=l, n=n) 30 30 }}} 31 31 32 where `level` and `n` are both optional named arguments BUT level is specified first. Previously, `n` was given first and `level` second. I think that it makes much more sense this way around, but if people feel really strongly about this I will change it back. Previously, `level` was just called `k`, which is a fairly random variable whereas `level` makes sense in terms of categorification and higher level Fock spaces. (Replacing `n` with `size` would also be sensible but I didn't go there.) 32 33 33 Finally, in addition to these new classes as discussed previously on sagecombinat I have removed a bunch functions which were depreciated years ago. I also added normal_nodes() and good_nodes methods to Partition_class andreinstated the beta_numbers() methods which were removed in the last patch to partition.py (this patch said that beta_numbers and frobenius_coordinates are identical objects, but they are actually different).34 Finally, in addition to these new classes I have removed a bunch functions which were depreciated years ago and depreciated some more functions, as discussed on sagecombinat. I also reinstated the beta_numbers() methods which were removed in the last patch to partition.py (this patch said that beta_numbers and frobenius_coordinates are identical objects, but they are actually different). 34 35 35 For discussion about the functions being deprecated please see the following two disc ssions on sagecombinat:36 For discussion about the functions being deprecated please see the following two discussions on sagecombinat: 36 37 * [https://groups.google.com/forum/?fromgroups=#!topic/sagecombinatdevel/NFNRYjqoouM Implementation of partition tuples] 37 38 * [https://groups.google.com/forum/?fromgroups=#!topic/sagecombinatdevel/utAsQzZQKLo number_of_partitions and friends]