#14654: implement flow polytopes
-------------------------------------+-------------------------------------
Reporter: ahmorales | Owner: graphcomponentowner
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-wishlist
Component: graph theory | Resolution:
Keywords: flow polytopes, | Merged in:
kostant partition function, sage | Reviewers:
days 47.5 | Work issues:
Authors: ahmorales | Commit:
Report Upstream: N/A | a1fa21827894719e987b1ac3e41527e92df43f68
Branch: u/chapoton/14654 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by chapoton):
Replying to [comment:18 ncohen]:
> It seems that what appears in `polytopes.<tab>` are the functions
defined in `sage.geometry.polyhedron.library.Polytopes`.
Yes, but is there a way to just import the function as a method
`polytopes.flow_polytope` ?
> Also, since you changed the status to `needs_review`: the documentation
of `DiGraph.flow_polytope` mentions a source and a sink with a non-null
flow, while the function only takes one argument, i.e. the graph.... Is
that normal ? `O_o`
Well, for quiver guys like me, a source is a vertex with only outgoing
edges, and a sink with only incoming edge. Maybe you give them other
names. So there is no need to provide them as arguments. Of course one
needs to have as many sources as sinks for the flow polytope to make
sense. Every source gets an input of 1 and every sink an output of 1.
--
Ticket URL: <http://trac.sagemath.org/ticket/14654#comment:19>
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.
