How the runner is used. #2
rayk
started this conversation in
Why, What & How
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Walker Signature
(Graph, Processor) => Future<Graph>Actors
1. Consumer: Code that async calls the walker and received but
<Graph>.2. Graph: Mutatable data structure containing Typed Vertex and Edges.
3. Processor: Self-contained program that produces a subgraph from the graph that was passed int.
4. Walker: Handles the effective traversal of
<Graph>yielding nodes to<Processor>.Dependency Structure & Importing.
Whilst Graph is read and mutated outside Walker, Processor is only executed by Walker. Yet Consumer may create instances of Processor with particular parameters, or get value from the processor to determine what it does or any state that may be contained within.
Use Case Examples
( g , p ) => rA. Graph Visualization
The consumer wants to produce a visualization of the graph that includes every vertex and edge in the graph. The actual visualization is handled by another package like gviz, which requires building a series of nodes with some data point from each of the vertex and edges in g.
(r)
<Graph>produced by p as a result of consuming all the vertex and edges in g.B. Subgraph Extraction
The consumer wants to operate on a subset of vertex and edges which are contained in g, criteria of which is defined in p. As p receives each vertex and edge from g, it decides if the node is of interest and places it in r.
(p)
C. Subgraph Visualization
The consumer wants to visualise only a subset of the graph.
D. Calculation From Node Values.
The consumer whats to a calculation using the values contained in a path of vertex and edges.
Beta Was this translation helpful? Give feedback.
All reactions