Re: [sage-combinat-devel] Re: Skew tableaux
How about we just implement both? Currently in #14101, the former is there for Tableaux, and the latter would be straightforward to add as well. On Nicolas' second point, don't we want Tableau to inherit from SkewTableau (and likewise for the parents)? Best, Travis On Thursday, July 11, 2013 3:13:16 AM UTC+5:30, Nicolas M. Thiery wrote: On Wed, Jul 10, 2013 at 01:36:40PM -0400, Mike Zabrocki wrote: I prefer that one not need to specify skew= True because it seems redundant. As for WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2]) Vs. WeakTableaux_core(3, [5, 2, 1], inner_shape=[2], [3,2]) I have a slight preference for the former, but I see that the latter is more verbose and slightly clearer. I have no strong opinion. However one advantage of the later is that it avoids a corner case: if someone is playing with a bunch of skew tableaux, among which some might have an empty inner shape, this makes sure that they are all handled identically. Otherwise, one has to make sure that a tableau behaves strictly exactly as a skew tableau (e.g. implements an inner_shape method, ...). Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
On Thursday, July 11, 2013 1:58:36 PM UTC+5:30, Nicolas M. Thiery wrote: On Thu, Jul 11, 2013 at 01:14:09AM -0700, Travis Scrimshaw wrote: On Nicolas' second point, don't we want Tableau to inherit from SkewTableau I am not sure: at least not if the internal data structures are not the same, which is probably what we want. On the other hand, on the abstract class level, the answer is probably yes. The internal data structures are the same; the only difference is SkewTableau will have None's representing the removed boxes. (and likewise for the parents)? Yes. Just being a bit careful that we conform to the ``isA`` paradigm: the class of ``Tableaux()`` should not inherit from that of ``SkewTableaux()``: the unique set of all tableaux is not the unique set of all skew tableaux. Oh the other hand, the class of ``StandardTableaux(shape)`` could well inherit from that of ``StandardSkewTableaux(outer_shape, inner_shape)``: a set of all standard tableaux of a given shape is indeed a special case of a set of all standard tableaux of a given outer shape and inner shape. Will do. Best, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
On 7/11/13 1:28 AM, Nicolas M. Thiery wrote: On Thu, Jul 11, 2013 at 01:14:09AM -0700, Travis Scrimshaw wrote: On Nicolas' second point, don't we want Tableau to inherit from SkewTableau I am not sure: at least not if the internal data structures are not the same, which is probably what we want. On the other hand, on the abstract class level, the answer is probably yes. (and likewise for the parents)? Yes. Just being a bit careful that we conform to the ``isA`` paradigm: the class of ``Tableaux()`` should not inherit from that of ``SkewTableaux()``: the unique set of all tableaux is not the unique set of all skew tableaux. Oh the other hand, the class of ``StandardTableaux(shape)`` could well inherit from that of ``StandardSkewTableaux(outer_shape, inner_shape)``: a set of all standard tableaux of a given shape is indeed a special case of a set of all standard tableaux of a given outer shape and inner shape. Just to let you know: for the weak k-tableaux I have now implemented the WeakTableaux(k, shape, inner_shape = [], weight, representation = core) option! That seems the most natural in this setting! Best, Anne -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
What about an optional argument for the inner shape which is by default the empty partition? Tableaux( 5, inner_shape=[2,2] ) This does not need to be the case for Tableau because you would just enter your tableau with None entries. -Mike On Tuesday, 9 July 2013 16:46:16 UTC-4, Anne Schilling wrote: Hi Travis, An extra Boolean skew = False/True is indeed how I have implemented the skew weak k-tableaux. I will push this code soon, so that you can see. Best, Anne On 7/9/13 12:03 PM, Travis Scrimshaw wrote: Hey all, I've started this process in #14101 by having Tableaux create a SkewTableaux parent if it is given a skew shape as input. However, I don't know if we can completely merge the two into a single interface cleanly. For example, how should we take care of creating all (skew) tableaux of size n? At present, the only way I can see it working is using a extra bool argument skew=True or something similar. Best, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
Hi Mike, Currently I have for the element class of weak tableaux sage: from sage.combinat.k_tableau import WeakTableau_core sage: t = WeakTableau_core([[None, None, 1, 1, 2], [1, 2], [2]],3, skew = True) sage: t [[None, None, 1, 1, 2], [1, 2], [2]] But I agree, I can remove the skew option from the element class, since it can be detected from the None objects inside the tableau. For the parent class, I currently have sage: from sage.combinat.k_tableau import WeakTableaux_core sage: T = WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2], skew = True) sage: T._shape ([5, 2, 1], [2]) sage: T._weight (3, 2) So the shape is a tuple with the outer and inner shape in accordance with skew partitions. Of course, this could be changed to sage: from sage.combinat.k_tableau import WeakTableaux_core sage: T = WeakTableaux_core(3, [5, 2, 1], inner_shape = [2], [3,2]) sage: T._shape ([5, 2, 1], [2]) sage: T._outer_shape = [5, 2, 1] sage: T._inner_shape = [2] sage: T._weight (3, 2) with inner_shape = [] as the default for non-skew tableaux. Do people prefer this? Then I will change weak tableaux in this way! Let me know soon (before it is too late :-) )! Best, Anne On 7/10/13 4:27 AM, Mike Zabrocki wrote: What about an optional argument for the inner shape which is by default the empty partition? Tableaux( 5, inner_shape=[2,2] ) This does not need to be the case for Tableau because you would just enter your tableau with None entries. -Mike On Tuesday, 9 July 2013 16:46:16 UTC-4, Anne Schilling wrote: Hi Travis, An extra Boolean skew = False/True is indeed how I have implemented the skew weak k-tableaux. I will push this code soon, so that you can see. Best, Anne On 7/9/13 12:03 PM, Travis Scrimshaw wrote: Hey all, I've started this process in #14101 by having Tableaux create a SkewTableaux parent if it is given a skew shape as input. However, I don't know if we can completely merge the two into a single interface cleanly. For example, how should we take care of creating all (skew) tableaux of size n? At present, the only way I can see it working is using a extra bool argument skew=True or something similar. Best, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
I prefer that one not need to specify skew= True because it seems redundant. As for WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2]) Vs. WeakTableaux_core(3, [5, 2, 1], inner_shape=[2], [3,2]) I have a slight preference for the former, but I see that the latter is more verbose and slightly clearer. -Mike On Wednesday, July 10, 2013, Anne Schilling wrote: Hi Mike, Currently I have for the element class of weak tableaux sage: from sage.combinat.k_tableau import WeakTableau_core sage: t = WeakTableau_core([[None, None, 1, 1, 2], [1, 2], [2]],3, skew = True) sage: t [[None, None, 1, 1, 2], [1, 2], [2]] But I agree, I can remove the skew option from the element class, since it can be detected from the None objects inside the tableau. For the parent class, I currently have sage: from sage.combinat.k_tableau import WeakTableaux_core sage: T = WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2], skew = True) sage: T._shape ([5, 2, 1], [2]) sage: T._weight (3, 2) So the shape is a tuple with the outer and inner shape in accordance with skew partitions. Of course, this could be changed to sage: from sage.combinat.k_tableau import WeakTableaux_core sage: T = WeakTableaux_core(3, [5, 2, 1], inner_shape = [2], [3,2]) sage: T._shape ([5, 2, 1], [2]) sage: T._outer_shape = [5, 2, 1] sage: T._inner_shape = [2] sage: T._weight (3, 2) with inner_shape = [] as the default for non-skew tableaux. Do people prefer this? Then I will change weak tableaux in this way! Let me know soon (before it is too late :-) )! Best, Anne On 7/10/13 4:27 AM, Mike Zabrocki wrote: What about an optional argument for the inner shape which is by default the empty partition? Tableaux( 5, inner_shape=[2,2] ) This does not need to be the case for Tableau because you would just enter your tableau with None entries. -Mike On Tuesday, 9 July 2013 16:46:16 UTC-4, Anne Schilling wrote: Hi Travis, An extra Boolean skew = False/True is indeed how I have implemented the skew weak k-tableaux. I will push this code soon, so that you can see. Best, Anne On 7/9/13 12:03 PM, Travis Scrimshaw wrote: Hey all, I've started this process in #14101 by having Tableaux create a SkewTableaux parent if it is given a skew shape as input. However, I don't know if we can completely merge the two into a single interface cleanly. For example, how should we take care of creating all (skew) tableaux of size n? At present, the only way I can see it working is using a extra bool argument skew=True or something similar. Best, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
Hi Mike, Yes, I can take the skew option out of WeakTableau. As for the parent WeakTableaux, in the __init__ I will need to make some case distinctions if the shape is skew or not. If we only specify WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2]) would the straight tableaux have to be inputted as WeakTableaux_core(3, [[5, 2, 1], []], [3,2,2]) or do you prefer WeakTableaux_core(3, [5, 2, 1], [3,2,2]) or either? I will somehow have to make a case check whether shape is a list/tuple of integers or of lists/tuples/partitions if I do not specify the skew Boolean. Best, Anne On 7/10/13 10:36 AM, Mike Zabrocki wrote: I prefer that one not need to specify skew= True because it seems redundant. As for WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2]) Vs. WeakTableaux_core(3, [5, 2, 1], inner_shape=[2], [3,2]) I have a slight preference for the former, but I see that the latter is more verbose and slightly clearer. -Mike On Wednesday, July 10, 2013, Anne Schilling wrote: Hi Mike, Currently I have for the element class of weak tableaux sage: from sage.combinat.k_tableau import WeakTableau_core sage: t = WeakTableau_core([[None, None, 1, 1, 2], [1, 2], [2]],3, skew = True) sage: t [[None, None, 1, 1, 2], [1, 2], [2]] But I agree, I can remove the skew option from the element class, since it can be detected from the None objects inside the tableau. For the parent class, I currently have sage: from sage.combinat.k_tableau import WeakTableaux_core sage: T = WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2], skew = True) sage: T._shape ([5, 2, 1], [2]) sage: T._weight (3, 2) So the shape is a tuple with the outer and inner shape in accordance with skew partitions. Of course, this could be changed to sage: from sage.combinat.k_tableau import WeakTableaux_core sage: T = WeakTableaux_core(3, [5, 2, 1], inner_shape = [2], [3,2]) sage: T._shape ([5, 2, 1], [2]) sage: T._outer_shape = [5, 2, 1] sage: T._inner_shape = [2] sage: T._weight (3, 2) with inner_shape = [] as the default for non-skew tableaux. Do people prefer this? Then I will change weak tableaux in this way! Let me know soon (before it is too late :-) )! Best, Anne On 7/10/13 4:27 AM, Mike Zabrocki wrote: What about an optional argument for the inner shape which is by default the empty partition? Tableaux( 5, inner_shape=[2,2] ) This does not need to be the case for Tableau because you would just enter your tableau with None entries. -Mike On Tuesday, 9 July 2013 16:46:16 UTC-4, Anne Schilling wrote: Hi Travis, An extra Boolean skew = False/True is indeed how I have implemented the skew weak k-tableaux. I will push this code soon, so that you can see. Best, Anne On 7/9/13 12:03 PM, Travis Scrimshaw wrote: Hey all, I've started this process in #14101 by having Tableaux create a SkewTableaux parent if it is given a skew shape as input. However, I don't know if we can completely merge the two into a single interface cleanly. For example, how should we take care of creating all (skew) tableaux of size n? At present, the only way I can see it working is using a extra bool argument skew=True or something similar. Best, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
On Wed, Jul 10, 2013 at 01:36:40PM -0400, Mike Zabrocki wrote: I prefer that one not need to specify skew= True because it seems redundant. As for WeakTableaux_core(3, [[5, 2, 1], [2]], [3,2]) Vs. WeakTableaux_core(3, [5, 2, 1], inner_shape=[2], [3,2]) I have a slight preference for the former, but I see that the latter is more verbose and slightly clearer. I have no strong opinion. However one advantage of the later is that it avoids a corner case: if someone is playing with a bunch of skew tableaux, among which some might have an empty inner shape, this makes sure that they are all handled identically. Otherwise, one has to make sure that a tableau behaves strictly exactly as a skew tableau (e.g. implements an inner_shape method, ...). Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
Hi Travis! On Tue, Jul 09, 2013 at 12:03:35PM -0700, Travis Scrimshaw wrote: I've started this process in #14101 Thanks! by having Tableaux create a SkewTableaux parent if it is given a skew shape as input. However, I don't know if we can completely merge the two into a single interface cleanly. For example, how should we take care of creating all (skew) tableaux of size n? At present, the only way I can see it working is using a extra bool argument skew=True or something similar. For the input, if there is no natural and unambiguous interface, I guess it's fair to require the user to call explicitly Tableau(s) or SkewTableau(s). Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
Hi Travis, An extra Boolean skew = False/True is indeed how I have implemented the skew weak k-tableaux. I will push this code soon, so that you can see. Best, Anne On 7/9/13 12:03 PM, Travis Scrimshaw wrote: Hey all, I've started this process in #14101 by having Tableaux create a SkewTableaux parent if it is given a skew shape as input. However, I don't know if we can completely merge the two into a single interface cleanly. For example, how should we take care of creating all (skew) tableaux of size n? At present, the only way I can see it working is using a extra bool argument skew=True or something similar. Best, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: Skew tableaux
Hi, Oops, per popular request, let me be a bit more specific: what is CAT complexity Constant Amortized Time; roughly speaking this means that, in average, each step of the iteration takes a constant amount of time: http://stackoverflow.com/questions/200384/constant-amortized-time In practice, since we usually create a full new element at each step of the iteration, we can't really achieve CAT; so it's fair to aim at an amortized time complexity that is linear in the size of the elements that are iterated through. and how can one use crystal operations for generation of all SSYT? Do they form a connected digraph on the set of all SSYT with given max_entry and shape?) Precisely. You get all SSYT from the highest weight one by applying successively the f (or e? I never know) crystal operators: sage: CrystalOfTableaux(['A',2], shape = [3,2]).list() [[[1, 1, 1], [2, 2]], [[1, 1, 2], [2, 2]], [[1, 1, 3], [2, 2]], [[1, 1, 3], [2, 3]], [[1, 2, 3], [2, 3]], [[1, 1, 3], [3, 3]], [[1, 2, 3], [3, 3]], [[2, 2, 3], [3, 3]], [[1, 1, 1], [2, 3]], [[1, 1, 2], [2, 3]], [[1, 2, 2], [2, 3]], [[1, 1, 1], [3, 3]], [[1, 1, 2], [3, 3]], [[1, 2, 2], [3, 3]], [[2, 2, 2], [3, 3]]] And there is a way to build an iterator out of those operations that is essentially CAT; see ClassicalCrystals.ParentMethods.__iter__. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: Skew tableaux
I would like to chime in on what Anne said. I would rather see that Tableau and Tableaux be able to handle skew-tableaux than copy-paste the tableaux functions into skew-tableaux. There is functionality in SkewTableau which is not in Tableau (cells_by_content, entries_by_content) and vice versa. -Mike On Monday, 1 July 2013 15:06:46 UTC-4, darijgrinberg wrote: Hi all (Travis in particular since he's working on the file), A few days ago, the lack of functionality in combinat/skew_tableau.py (as opposed to combinat/tableau.py) bit me: I was trying to generate all skew semistandard tableaux of a given shape with a given max_entry, and noticed that there is no such option. This isn't the only thing missing, and it seems that skew_tableau.py never got the love that tableau.py received during development. Are there any updates to the file floating around between combinat people? I am aware of trac #14101 (which depends on #14772, which conflicts with #14808; but even without #14808, the #14101 patch fails on my sage-5.11beta3 at patching sage/combinat/integer_vector_weighted.py for some reason). But as far as I understand, this mainly changes the OOP structure, while leaving the functionality as it is; right, Travis? Anyway, I'm assuming this is the wrong time for me to mess with the file, but once Travis's stuff is positively reviewed, would it be a good idea to basically copypaste the structure of tableau.py into skew_tableau.py (with the appropriate changes to the algorithms), or do you think tableau.py is a mess and should not be imitated? (I'm asking because such things were told to me about some parts of the code; I don't have particular reservations about tableau.py.) Best regards, Darij -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: Skew tableaux
On Monday, 1 July 2013 21:06:46 UTC+2, darijgrinberg wrote: This isn't the only thing missing, and it seems that skew_tableau.py never got the love that tableau.py received during development. One many things that skew tableaux (and skew partitions) are currently missing is a latex method. As part of a review of Travis huge categorification patch for partitons I updated sage.combinat.output.py so that the routines there now work for skew tableaux (and diagrams of skew partitions) but we didn't add the corresponding methods to skew tableaux. If any one wants these, I think that it is enough to simply copy the corresponding routines across from the non-skew classes, although there will be some trickery due to the global option classes...I'm fairly snowed under at the minute, but if there is sufficient demand I could look in to this. Andrew -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: Skew tableaux
Hey Darij and everyone, You are correct, it is just a restructuring of skew* and ribbon[shaped](tableaux) to follow the category framework and better naming conventions. #14101 and its dependency #14772 and possibly #14519 are basically done; although #14101 still actually has some work still needed doctest wise... Nicolas, are you still willing to do the review of #14519? I believe Mike will do the full review of #14772. Arthur and I are planning on cross reviewing #14101. Darij, if you want some extra features for skew tableaux and/or you want #14772 to depend on #14808, just go ahead and ask. Even better if you could provide code for those features. Best, Travis On Monday, July 1, 2013 9:06:46 PM UTC+2, darijgrinberg wrote: Hi all (Travis in particular since he's working on the file), A few days ago, the lack of functionality in combinat/skew_tableau.py (as opposed to combinat/tableau.py) bit me: I was trying to generate all skew semistandard tableaux of a given shape with a given max_entry, and noticed that there is no such option. This isn't the only thing missing, and it seems that skew_tableau.py never got the love that tableau.py received during development. Are there any updates to the file floating around between combinat people? I am aware of trac #14101 (which depends on #14772, which conflicts with #14808; but even without #14808, the #14101 patch fails on my sage-5.11beta3 at patching sage/combinat/integer_vector_weighted.py for some reason). But as far as I understand, this mainly changes the OOP structure, while leaving the functionality as it is; right, Travis? Anyway, I'm assuming this is the wrong time for me to mess with the file, but once Travis's stuff is positively reviewed, would it be a good idea to basically copypaste the structure of tableau.py into skew_tableau.py (with the appropriate changes to the algorithms), or do you think tableau.py is a mess and should not be imitated? (I'm asking because such things were told to me about some parts of the code; I don't have particular reservations about tableau.py.) Best regards, Darij -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: Skew tableaux
I believe Mike will do the full review of #14772. Arthur and I are planning on cross reviewing #14101. To clarify, it is Mike Hanson. -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
