#10527: Implementation of quiver mutation type
-----------------------------------------------+----------------------------
       Reporter:  stumpc5                      |         Owner:  sage-combinat
           Type:  enhancement                  |        Status:  needs_review 
       Priority:  major                        |     Milestone:  sage-5.3     
      Component:  combinatorics                |    Resolution:               
       Keywords:  quiver mutation type days38  |   Work issues:               
Report Upstream:  N/A                          |     Reviewers:  Hugh Thomas  
        Authors:  Christian Stump              |     Merged in:               
   Dependencies:                               |      Stopgaps:               
-----------------------------------------------+----------------------------

Comment (by gmoose05):

 I have now rolled back my recent changes.  I believe there are some
 advantages to making further changes to the quiver_mutation_type.py file,
 but these advantages only occur in conjunction with the quiver.py file.
 Thus, we still should discuss my ideas to see if there's possible bugs
 that I'm not foreseeing, but these no longer affect #10527, only #10538.
 I have moved those changes (except for the bugs you found) out of my
 recent patch.

 The general point is that I don't want to add more quiver mutation types,
 I only want to allow more flexibility in the user building a quiver.
 Since quiver_mutation_type.py is where we define all the digraphs anyway,
 my default plan was to eventually define more digraphs in
 quiver_mutation_type.py through a private method that a user won't
 directly access.  In fact, we already have this programmed,
 !QuiverMutationType_Irreducible, which is not imported into the global
 name space.  In #10538, I was planning to have a patch that will allow the
 !ClusterQuiver class to call this command for certain user inputs.  This
 is somewhat like the suggestion you just made, if I understood correctly.

 Short summary: my patch now only takes care of the issues you recently
 raised.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10527#comment:120>
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.

Reply via email to