Mercurial > pylearn
comparison doc/v2_planning/dataset.txt @ 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 | 319de699fb67 |
| children | 5e6d7d9e803a |
comparison
equal
deleted
inserted
replaced
| 1092:aab9c261361c | 1094:75175e2e697d |
|---|---|
| 317 this feature we will need to find hacks around it .. | 317 this feature we will need to find hacks around it .. |
| 318 | 318 |
| 319 OD: I have like zero experience with GPU so hopefully someone else can answer | 319 OD: I have like zero experience with GPU so hopefully someone else can answer |
| 320 this. But the way I see it, hopefully it could work by having some dataset | 320 this. But the way I see it, hopefully it could work by having some dataset |
| 321 object that would take care of storing its input data into a shared variable. | 321 object that would take care of storing its input data into a shared variable. |
| 322 | 322 OD (continued): After thinking a bit more about it, I am not sure that would |
| 323 work. I definitely need to look at some code doing it to get a better | |
| 324 understanding of it, but my feeling is that you need your learner to be | |
| 325 written in a specific way to achieve this, in which case it may be up to the | |
| 326 learner to take its input data and store it into a shared variable. |