From: Francois Fleuret Date: Fri, 13 Jan 2017 07:39:45 +0000 (+0100) Subject: Oups, fixed a very wrong explanation regarding the input/output flowing in the graph. X-Git-Url: https://fleuret.org/cgi-bin/gitweb/gitweb.cgi?a=commitdiff_plain;h=d8fd868f94ce0b66cd2cc1a4615df10a88b5d5ec;p=dagnn.git Oups, fixed a very wrong explanation regarding the input/output flowing in the graph. --- diff --git a/README.md b/README.md index 58c386f..b122ee0 100644 --- a/README.md +++ b/README.md @@ -46,9 +46,9 @@ Note that DAG:connect allows to add a bunch of edges at once. This is particular ##Input and output## -If a node has a single successor, its output is sent unchanged as input to that successor. If it has multiple successors, the outputs are collected into a table, and the table is used as input to the successor node. The indexes of the outputs in that table reflects the order of the DAG:connect() commands. +If a node has a single predecessor, its output is taken as-is. If it has multiple predecessors, all the outputs are collected into a table, and the table is used as input. The indexes of the outputs in that table reflects the order in which the predecessors appeared in the DAG:connect() commands. -The expected input (respectively the produced output) is a nested table of inputs reflecting the structure of the nested table of modules provided to DAG:setInput (respectively DAG:setOutput) +The input to the DAG (respectively the produced output) is a nested table of inputs reflecting the structure of the nested table of modules provided to DAG:setInput (respectively DAG:setOutput) So for instance, in the example above, the model expects a tensor as input, since it is the input to the module a, and its output will is a table composed of two tensors, corresponding to the outputs of d and e respectively.