On Fri, Jul 12, 2013 at 12:45:47PM -0700, Frédéric Chapoton wrote:
>I vote for
>
> 1. The invalid path maps to the zero of the algebra,
>
>since you have chosen to linearise the free category into an algebra,
>that's the logical thing to do
+1
It will be consistent with group
On Friday, July 12, 2013 3:03:58 PM UTC-4, Simon King wrote:
> > 3. Disallow invalid paths as paths and path algebra elements.
>
> No way. Otherwise, the algebra would only have a partially defined
> multiplication, which makes it not an algebra.
Why? Multiplication in the algebra is perfectl
Hey Anne,
Fixed. It was due to whitespace changes in #12250. I removed the
affected whitespace changes in #14101 to avoid this conflict.
Best,
Travis
On Friday, July 12, 2013 8:45:51 AM UTC-7, Anne Schilling wrote:
>
> Hi Travis,
>
> Once again
>
> applying trac_14101-remove_cc_skew-ts
I vote for
1. The invalid path maps to the zero of the algebra,
since you have chosen to linearise the free category into an algebra,
that's the logical thing to do
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To unsubscribe from
PS:
On 2013-07-12, Simon King wrote:
> Hi Volker,
>
> On 2013-07-12, Volker Braun wrote:
>> How about
>>
>> 3. Disallow invalid paths as paths and path algebra elements.
>
> No way. Otherwise, the algebra would only have a partially defined
> multiplication, which makes it not an algebra.
Put
Hi Volker,
On 2013-07-12, Volker Braun wrote:
> How about
>
> 3. Disallow invalid paths as paths and path algebra elements.
No way. Otherwise, the algebra would only have a partially defined
multiplication, which makes it not an algebra.
Best regards,
Simon
--
You received this message beca
How about
3. Disallow invalid paths as paths and path algebra elements.
On Friday, July 12, 2013 2:27:37 PM UTC-4, Simon King wrote:
>
> Two possible solutions come to mind:
> 1. The invalid path maps to the zero of the algebra, or
> 2. If i comes from the invalid path and x is any element,
Hi!
I am about to fix some further issues with quivers, their
representations and algebras (namely: I'd like that TestSuite(...).run()
passes) at #12630.
One problem: Each quiver has an invalid path, which is currently mapped
to a non-zero element in the algebra of that quiver, but this non-zero
Dear Tableaux Fans!
Mike and I have some questions regarding the design for weak and strong
k-tableaux
(and tableaux in general):
- Currently in Tableaux, the weight of a tableau is returned as a list.
However, because of UniqueRepresentation the input needs to be parsed into a
tuple
Hi Travis,
Once again
applying trac_14101-remove_cc_skew-ts.patch
patching file sage/combinat/skew_tableau.py
Hunk #25 FAILED at 1031
1 out of 44 hunks FAILED -- saving rejects to file
sage/combinat/skew_tableau.py.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in
Hi!
Currently, Homset.__call__ has nothing to do whatsoever with
Parent.__call__. In particular, it won't to assign a certain
Morphism baseclass to an attribute Element---which would be the way to
proceed in the case of a Parent.
But Homset *is* a Parent, by definition of the class!
Hence, do yo
11 matches
Mail list logo
