#12630: Add representations of quivers and quiver algebras to sage
-------------------------------------------+--------------------------------
       Reporter:  JStarx                   |         Owner:  AlexGhitza  
           Type:  enhancement              |        Status:  needs_review
       Priority:  major                    |     Milestone:  sage-5.10   
      Component:  algebra                  |    Resolution:              
       Keywords:  algebra, quiver, module  |   Work issues:              
Report Upstream:  N/A                      |     Reviewers:              
        Authors:  Jim Stark                |     Merged in:              
   Dependencies:  #12412, #12413           |      Stopgaps:              
-------------------------------------------+--------------------------------

Comment (by SimonKing):

 I am both puzzled and impressed: Aren't modules in Sage currently only
 defined over commutative algebras? But then, why does it work to let
 `QuiverRep_generic` inherit from sage.modules.module.Module?

 Concerning the location of the class definitions, I think that one should
 not squeeze all code into sage.modules.quiver_module: This file should
 only contain `QuiverRep_generic` and related definitions, but not
 `Quiver_generic`, `QuiverPath` or `QuiverAlgebra`:

 - If one thinks that a quiver is a graph, then it should be defined
 somewhere in sage.graphs. If one thinks that a quiver is an associative
 magma that also happens to be a graph (I'd prefer this point of view!),
 then one might create a new section sage.magmas for it, or simply put it
 into sage.monoids.
 - A quiver algebra is an algebra. Hence, it should be put into
 sage.algebras.
 - If one thinks of `QuiverPath` as an element of a quiver-the-associative-
 magma, then it should be put into the same section (sage.magmas or
 sage.monoids) and used as element_class of quiver-the-associative-magma;
 but even in this case, `QuiverPath` and quiver-the-associative-magma
 should be defined in different files, so that it will later be easier to
 change `QuiverPath` into optimized Cython code.

 IMHO, the code will be much easier to maintain when it was divided into
 smaller parts distributed into appropriate sections of Sage.

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