#10527: Implementation of quiver mutation type
-----------------------------------------------+----------------------------
Reporter: stumpc5 | Owner: sage-combinat
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: combinatorics | Resolution:
Keywords: quiver mutation type days38 | Work issues:
Report Upstream: N/A | Reviewers: Hugh Thomas
Authors: Christian Stump | Merged in:
Dependencies: #10349 | Stopgaps:
-----------------------------------------------+----------------------------
Comment (by nthiery):
> Sweet, he?
Pretty sweet indeed!
> Beside that, the class !CartanMatrix is not yet very advanced,
> and several important decisions are still to be made (e.g., how should
> !CartanMatrix, !CartanType, !RootSystem, !RootSpace, and so on,
> interact?), but that's a different topic.
>
> How do you think to change the organization of the methods by using
> !CartanMatrix (or !CartanType)?
Having cartan_type return a Cartan matrix would seem just natural to
me, as long as all operations on cartan types (building the root
system, the weyl group, ...) are available from a cartan matrix (they
should). In the long run, we probably want to rename all our
cartan_type methods to cartan_datum.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <[email protected]>
http://Nicolas.Thiery.name/
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10527#comment:52>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
