#13425: Compute mutation type of a ClusterSeed or ClusterQuiver
---------------------------------------------------+------------------------
       Reporter:  gmoose05                         |         Owner:  
sage-combinat                  
           Type:  enhancement                      |        Status:  
needs_review                   
       Priority:  major                            |     Milestone:  sage-5.9   
                    
      Component:  combinatorics                    |    Resolution:             
                    
       Keywords:  cluster algebra, quiver, days45  |   Work issues:             
                    
Report Upstream:  N/A                              |     Reviewers:  Christian 
Stump, Gregg Musikier
        Authors:  Gregg Musiker, Christian Stump   |     Merged in:             
                    
   Dependencies:  #13424                           |      Stopgaps:             
                    
---------------------------------------------------+------------------------

Comment (by gmoose05):

 Hi Christian,

 It seems to work for me except for two small issues.

 1) It seems that if I run save_quiver_data( ... ), and then load_data( ...
 ), I don't see the data I just saved.  If I close and restart sage, this
 seems okay, or maybe there's just a time-lag but let me know if you see
 similar behavior.

 2) Let's say that a user runs save_quiver_data(2,
 up_to=False,'types'=Classical).
 This saves data to the ./sage folder.

 If the user now runs the load_data(2) command, it looks in the ./sage
 folder and sees and prints data for ['A', (1,1),1], ['A', 2], ['B', 2],
 and ['BC', 1, 1].

 If I then close sage and run ../../sage -i cluster_seed-1.0.spkg
 (technically with the -f option since I'm reinstalling after having
 deleted the folder for testing purposes), then, I should also have the
 exceptional data now too, but when I run load_data(2), it still only loads
 the classical data from the ./sage folder.

 Do you get similar behavior?  I think it would be slightly better if
 load_data( n ) loaded the union of the dig6 data from the two sources.
 Otherwise, if one saved the classical data (for e.g. for rank 9 or 10)
 then unless one also saved classicalexceptional, one would no longer have
 the exceptional data.

 However, this is still better than the version before where
 save_quiver_data and the spkg were writing to the same filenames so the
 same problem would have been appearing there.

 Best, Gregg

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13425#comment:26>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to