]> gitweb.michael.orlitzky.com - sage.d.git/commit
eja: ensure that Sage doesn't think EJAs are associative.
authorMichael Orlitzky <michael@orlitzky.com>
Mon, 5 Aug 2019 18:06:24 +0000 (14:06 -0400)
committerMichael Orlitzky <michael@orlitzky.com>
Mon, 5 Aug 2019 18:06:24 +0000 (14:06 -0400)
commit17aee61574caf7f62a70d181840c2be69879a3e7
tree8da0c64cb071adb75d0d3dc6aa48b074fa773874
parent78b54b562e1eedbb919dc442b2b3f6996440a1a2
eja: ensure that Sage doesn't think EJAs are associative.

It turns out that the FiniteDimensionalAlgebrasWithBasis category
somehow has both the legacy Algebras() category and the newer
MagmaticAlgebras() category as super-categories. Problem is, the
legacy one is associative! To fix that, we now use MagmaticAlgebras
directly.

Of course, we have to reimplement some of the stuff that was done for
us before... and we have to add a bunch of hacks for parts of Sage
that break when you don't have a ring.... and we can't use a matrix
for our multiplication table any more. But it was all doable.
mjo/eja/eja_algebra.py
mjo/eja/eja_element.py
mjo/eja/eja_subalgebra.py