|
|
@@ -1,8 +1,43 @@
|
|
|
# TODO
|
|
|
|
|
|
+# Flow types
|
|
|
+
|
|
|
+* Graph
|
|
|
+* Pipeline
|
|
|
+
|
|
|
+## Graph
|
|
|
+
|
|
|
+Graph will have one output and several inputs, a graph is commanded by the output node
|
|
|
+like a function the node runs by fetching inputs and processing them.
|
|
|
+
|
|
|
+* Several inputs
|
|
|
+* One output
|
|
|
+* Graph is started by the last node
|
|
|
+* Process will follow from current fetching the input nodes
|
|
|
+* Each input can only have one source
|
|
|
+* Fetch result from any node
|
|
|
+
|
|
|
+computational graphs can have several purposes but the primal goal was machine learning
|
|
|
+and have a flow of tensors
|
|
|
+
|
|
|
+## Pipeline
|
|
|
+
|
|
|
+Pipeline will have a single input and output and its commanded by the first node
|
|
|
+when a node is finish it will trigger the next nodes with data generated by the node
|
|
|
+
|
|
|
+* One input
|
|
|
+* One output
|
|
|
+* Nodes trigger other to process
|
|
|
+* One input can have several sources, a node can send to several outputs
|
|
|
+* Nodes are dependend on input, process should start from the initial pipeline node
|
|
|
+
|
|
|
+Pipelines can also have several purposes but started with the idea of creating
|
|
|
+some kind of CI where we can graphically see nodes processing,
|
|
|
+from build to staging
|
|
|
+
|
|
|
# Minimal idea
|
|
|
|
|
|
-UI to create multipurpose tensorflow alike graphs,
|
|
|
+UI to create multipurpose flow graphs,
|
|
|
upload to the server
|
|
|
pass inputs and do training
|
|
|
fetch model and use it with new inputs
|
luis