On Sat, Mar 09, 2013 at 12:50:24PM +0530, Kannappan Sampath wrote:
>That was very enlightening. I haven't been able to come back to this
>because of the exams. So, let me summarise the changes we have agreed to
>make:
>(1) Move the method in question, long_element to the Coxeter Gr
Hello!
That was very enlightening. I haven't been able to come back to this
because of the exams. So, let me summarise the changes we have agreed to
make:
(1) Move the method in question, long_element to the Coxeter Groups
category.
(2) Deprecate this method and redirect the user to longest_eleme
On Wed, Mar 06, 2013 at 04:27:57AM -0800, Travis Scrimshaw wrote:
> I'd throw a type error if the group W was infinite since this does not
>exist. Also I would think it would be (relatively) easy to check if
>subgroup the group is finite since there are only 3 infinitely families
>
> Of
> course this would only be after it has been broken up into connected
> components. Perhaps I'm over simplifying things...
If I understand it right, Nicolas suggested to move that stuff the the
CoxeterGroups category. In this generality, this approach of checking
finite types doesn't work, b
Hey,
Thanks Kannappan for your work on this! By the way: would you mind
> using the occasion to move this method to the CoxeterGroups category?
> Of course, calling "W.longest_element()" for an infinite coxeter group
> W is not a wise thing to do; but we recently had the need for
> computing l
On Tue, Mar 05, 2013 at 03:11:00AM -0800, tom d wrote:
>I think longest_element is fine;
Ok for me, unless someone finds something better.
>long_word indicates that there will be a word returned instead of
>an element, which is maybe not what we're after here.
+1
Thanks Kannappan f
Hah! Fantastic!! I'll go ahead and implement this later tonight if I
receive no more information regarding this issue. Thanks for the
enlightenment, Tom.
With Sincere Regards,
Kannappan.
On Tue, Mar 5, 2013 at 4:41 PM, tom d wrote:
> I think longest_element is fine; long_word indicates that th
I think longest_element is fine; long_word indicates that there will be a
word returned instead of an element, which is maybe not what we're after
here.
Wiser minds than mine will have more knowledge of how to handle
deprecation, but here's an example from skew_partition.py:
sage: x.r_quotient
