#17798: Create a class for Coxeter matrices and types
-------------------------------------+-------------------------------------
Reporter: tscrim | Owner: sage-combinat
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.6
Component: group theory | Resolution:
Keywords: Coxeter groups, | Merged in:
matrices, types, days64 | Reviewers:
Authors: Travis Scrimshaw, | Work issues:
Jean-Philippe Labbé | Commit:
Report Upstream: N/A | d0932c325ede70e04db1b659bcfbf86a7b691e06
Branch: | Stopgaps:
public/combinat/coxeter_matrices-17798|
Dependencies: #17990 |
-------------------------------------+-------------------------------------
Comment (by jipilab):
Yes... It is a bummer that Coxeter does have a graph with its actual name
tagged to it!
In the end, it is just a name, I guess we should try to be consistent in
the naming convention since we are at it, and I'd like to know how to
proceed...
As far as I know, Humphreys is careful not to give the graphs a name. On
p.1 of Bjoerner&Brenti, they call it a "Coxeter graph (or Coxeter
diagram)".
I would vote for Coxeter graph and Dynkin diagram since it emphasizes the
difference between the two structures. About the confusion with the actual
Coxeter graph, I believe it is not a so dreadful danger of confusion.
I think that the Coxeter graph is not so commonly used as to need it
directly from the sage prompt, right?
Agreed with refactor common code later.
--
Ticket URL: <http://trac.sagemath.org/ticket/17798#comment:24>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
