Mercurial > pylearn
changeset 1364:01157763c2d7
Reply to Razvan
| author | Olivier Delalleau <delallea@iro> |
|---|---|
| date | Fri, 12 Nov 2010 11:36:30 -0500 |
| parents | 18b2ebec6bca |
| children | 049b99f4b323 |
| files | doc/v2_planning/datalearn.txt |
| diffstat | 1 files changed, 7 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/v2_planning/datalearn.txt Fri Nov 12 11:11:49 2010 -0500 +++ b/doc/v2_planning/datalearn.txt Fri Nov 12 11:36:30 2010 -0500 @@ -219,6 +219,13 @@ transformation rooted in a dataset, and if you want same transformation for a different dataset you have to re-write everything. +OD replies: Still not sure I understand. If you have a "graph" function that +takes a dataset as input and outputs a new dataset, you can use this same +function with both (1) and (2). With (2) it is: + theano.function([index], graph(my_dataset)[index].variable) +while with (1) the same function is compiled implicitly with: + for sample in graph(my_dataset): + ... - in approach (1) the initial dataset object (the one that loads the data) decides if you will use shared variables and indices to deal with the