Good morning, Nicolas!
I finalized the new crystal patches (affine-E-as.patch,
affine-E-revised-as.patch). I left the facade = True option
for direct sums when no crystal is repeated. Also, HighestWeightCrystals
now only takes one weight as input. In the process I removed the
__class__ method which did not seem necessary any longer.
The _test_fast_iter should also hopefully be compliant now.
If it looks ok, I'll upload this onto trac.
------------------------------------------------------------------------------
When meaningful, one can further customize on which elements
the tests are run. Here, we use it to *prove* that the
multiplication is indeed associative, by running the test on
all the elements::
sage: S._test_associativity(elements = S)
Adding a new test boils down to adding a new method in the class
of the object or any super class (e.g. in a category). This method
should use the utility :meth:`._tester` to handle standard options
and report test failures. See the code of
:meth:`._test_an_element` for an example.
------------------------------------------------------------------------------
Looks ok.
Where should the method for weight.highest_weight_crystal() go? In
weight_lattice_realization.py?
Ideally yes. Do the various crystal accept as well weights in the
weight lattice and in the ambient space?
I think I will not include this in this patch, since currently
only type E6 and E7 highest weight crystals are implemented
and hence this does not seem so useful yet.
Cheers,
Anne
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To post to this group, send email to sage-combinat-de...@googlegroups.com.
To unsubscribe from this group, send email to
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sage-combinat-devel?hl=en.
