Mercurial > pylearn
changeset 1094:75175e2e697d
dataset: Continued comment about GPU and shared variables
| author | Olivier Delalleau <delallea@iro> |
|---|---|
| date | Mon, 13 Sep 2010 09:11:43 -0400 |
| parents | aab9c261361c |
| children | 520fcaa45692 |
| files | doc/v2_planning/dataset.txt |
| diffstat | 1 files changed, 5 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/v2_planning/dataset.txt Sun Sep 12 15:12:19 2010 -0400 +++ b/doc/v2_planning/dataset.txt Mon Sep 13 09:11:43 2010 -0400 @@ -319,4 +319,8 @@ OD: I have like zero experience with GPU so hopefully someone else can answer this. But the way I see it, hopefully it could work by having some dataset object that would take care of storing its input data into a shared variable. - +OD (continued): After thinking a bit more about it, I am not sure that would +work. I definitely need to look at some code doing it to get a better +understanding of it, but my feeling is that you need your learner to be +written in a specific way to achieve this, in which case it may be up to the +learner to take its input data and store it into a shared variable.