From 125002d32a2c9ea88bdbc722a888d3788901fc27 Mon Sep 17 00:00:00 2001 From: Francois Fleuret Date: Sat, 14 Jan 2017 09:44:06 +0100 Subject: [PATCH] Update. --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f2fac30..fbb7a96 100644 --- a/README.md +++ b/README.md @@ -56,14 +56,15 @@ The DAG can deal with modules which take as input and produce as output tensors and nested tables of tensors. If a node has a single predecessor, the output of the latter is taken -as-is as the input of the former. If it has multiple predecessors, all +as-is as the input to the former. 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 edges where created in the DAG:connect() commands. +input. The indexes of the outputs in that table reflect the +chronological order in which the edges where created in the +DAG:connect() commands. 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) +modules given as argument 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 -- 2.20.1