Mercurial > pylearn
changeset 1338:91637815b7ca
Added a comment on the dataset vs. task issue
| author | Olivier Delalleau <delallea@iro> |
|---|---|
| date | Thu, 21 Oct 2010 14:03:12 -0400 |
| parents | 7dfc3d3052ea |
| children | 158493f8dff9 |
| files | doc/v2_planning/dataset.txt |
| diffstat | 1 files changed, 6 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/v2_planning/dataset.txt Thu Oct 21 13:00:49 2010 -0400 +++ b/doc/v2_planning/dataset.txt Thu Oct 21 14:03:12 2010 -0400 @@ -567,4 +567,10 @@ - Ideally, data should be deterministic (i.e. __call__() should always return the same thing). It would probably be up to the user to be super careful if he decides to use a non-deterministic dataset. + - About the "task vs. dataset" distinction. This could be achieved by + associating to a task the names of the fields it requires (e.g. "input" + and "target" for the regression task), and if the dataset does not + already defines these fields, using a dataset wrapper than does it + (saying for instance that "input" is the concatenation of "x1" and "x2", + and "target" is "y", for a dataset whose fields are x1, x2 and y).