#10527: Implementation of quiver mutation type
-----------------------------------------------+----------------------------
Reporter: stumpc5 | Owner: sage-combinat
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: combinatorics | Resolution:
Keywords: quiver mutation type days38 | Work issues:
Report Upstream: N/A | Reviewers: Hugh Thomas
Authors: Christian Stump | Merged in:
Dependencies: #10349 | Stopgaps:
-----------------------------------------------+----------------------------
Comment (by stumpc5):
Replying to [comment:40 hthomas]:
> Christian, could you please explain to me the distinction between
!QuiverMutationTypeFactory and !QuiverMutationType? Sorry, I am very much
a beginning when it comes to object-oriented stuff like classes.
I basically took this idea from Nicolas' implementation of !CartanType:
!CartanTypeFactory just delegates different input to the right place -- we
have an object
{{{
QuiverMutationType = QuiverMutationType()
}}}
and if the input is irreducible, we return a
!QuiverMutationType_irreducible object and if the input is reducible we
return a !QuiverMutationtype_reducible object. Moreover,
!QuiverMutationType also provides samples of quiver mutation types, see
the samples methods in the factory.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10527#comment:43>
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.
