#19339: Use digraph labels if present for ClusterAlgebra and ClusterQuiver
-----------------------------------+------------------------
Reporter: aram.dermenjian | Owner:
Type: PLEASE CHANGE | Status: new
Priority: minor | Milestone: sage-6.9
Component: algebra | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------------+------------------------
Changes (by aram.dermenjian):
* priority: major => minor
* cc: gmoose05 (added)
* component: PLEASE CHANGE => algebra
Old description:
New description:
'''Information from Gregg Musiker'''
I recently realized that if one starts with a digraph D (with vertices
labeled however) and then writes
S = ClusterSeed(D), then the code will effectively call
Q = ClusterQuiver(D) and then assign S = ClusterSeed(Q).
In the same spirit as the last ticket, I think it makes sense to add other
vertex names to ClusterQuiver and allow these to be passed on to Cluster
Seed. Since we only changed the behavior of cluster_seed.py in the last
ticket, I believe the behavior of quiver.py was unaffected.
In particular, if one writes ClusterSeed(D) or ClusterQuiver(D), then I
believe Sage should then use the vertices of digraph as labels rather than
defaulting to [0,...,n-1]. (Although we will have to think somewhat about
backwards compatibility.)
In particular, I'm thinking of two changes.
1) In ClusterQuiver()'s init command, if a digraph is the input, then the
vertices of ClusterQuiver agree with the labels of the vertices of the
input digraph. (Although for internal data, sage would also have a
dictionary from {0,..., n-1} to these vertex labels so that it understands
the "ij-th" entry of the B-matrix for instance.
2) In ClusterSeed()'s init command, if a ClusterQuiver is the input, then
it uses those vertices as labels for the cluster variables as if the user
had given user_labels.
The only exception would be if the user puts in such a ClusterQuiver and
also user_labels as a separate input, then the new user_labels should
override the old ones from the ClusterQuiver.
--
--
Ticket URL: <http://trac.sagemath.org/ticket/19339#comment:1>
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.