New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in k-bounded symmetric functions #13743
Comments
comment:1
That Partitions accepts a set is in fact not a bug. Granted, it should be documented, and there certainly are many cases like this one where this is not supported (so I agree with the existence of this ticket). But this is definitely a feature we want (and that is, more or less, implemented in IntegerListsLex). Cheers, |
comment:2
You can just do
Anne |
Dependencies: 13605 |
comment:3
As far as I can tell, Travis' changes to Partitions may fix this bug. I am adding him as cc on this ticket. There are currently still conflicts between the symmetric functions and Partitions. Perhaps they are resolved it is possible that they will fix this problem so he can take this into account as he writes his patch. So for instance after I apply Travis' patch trac_13605-partition_options-ts.patch I have:
However the same patch currently causes a different problem with symmetric functions:
Travis, was it your intention to allow |
comment:4
Replying to @zabrocki:
I'll go through now and scrub all instances of
Do you mean |
comment:5
I meant |
Changed dependencies from 13605 to #13605 |
comment:7
In an ideal world, yes, that should be all partitions with max part What I'm doing in #13605 won't really affect how input is handled, and if I understand this ticket correctly, it is to port the list input aspect of
On a slight side note, |
comment:8
Two small comments: First,
returns a value error. Second, your set
has repr:
which is confusing. I have implemented something similar to Travis' first suggested solution to deal with the k-quotient side of things. |
comment:9
Found another bug which is really related to this one. If we give an input to a kSchur function which isn't k-bounded, then it should return an error:
But this should also return an error:
|
comment:12
We both end up deleting the |
comment:13
Everything looks good. This seems to catch all the issues with having the correct indices in k-Schur functions that I can find. Thanks for coming back to this one. |
comment:14
Thank you for doing the review. |
Reviewer: Mike Zabrocki |
Changed author from Chris Berg to Travis Scrimshaw |
comment:17
This should be rebased to sage-5.8.rc0. |
comment:18
I've rebased to 5.8.rc0. Apply: trac_13743-fix_kschur-ts.2.patch |
comment:19
It still doesn't apply properly, are you sure you have a clean build of sage-5.8.rc0?
|
Attachment: trac_13743-fix_kschur-ts.2.patch.gz |
comment:20
I am restoring positive review. I had to recompile sage-5.8.rc0 to ensure that I didn't have a problem. This patch now applies cleanly. |
Merged: sage-5.9.beta0 |
The indices method of the KBoundedSubspace class is done wrong. The code is:
Partitions is not meant to take a set. It will usually complain if you input something like NonNegativeIntegers but due to a bug in partitions, it allows it if you have optional arguments.
This creates the following bugs when playing around with k-Schur functions:
Depends on #13605
Depends on #14228
CC: @anneschilling @zabrocki @tscrim
Component: combinatorics
Author: Travis Scrimshaw
Reviewer: Mike Zabrocki
Merged: sage-5.9.beta0
Issue created by migration from https://trac.sagemath.org/ticket/13743
The text was updated successfully, but these errors were encountered: