projects:gpu_exploration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
projects:gpu_exploration [2013/12/19 22:11] nceghtebas |
projects:gpu_exploration [2013/12/19 22:19] (current) nceghtebas [Work Plan reflection] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| This involved everything from getting the correct drivers installed and the developing environment up and running to understanding and implementing some GPU code and doing something useful (or cool) with it. In writing the code I also found it helpful to have some understanding of the GPU architecture or hardware implementation. | This involved everything from getting the correct drivers installed and the developing environment up and running to understanding and implementing some GPU code and doing something useful (or cool) with it. In writing the code I also found it helpful to have some understanding of the GPU architecture or hardware implementation. | ||
| - | I have planned on teaching peers about the topics I had researched into through [[gpu_exploration: my documentation]]. This includes information about the "important" aspects of the GPU hardware, difference in coding specifically for GPU versus just regular C/C++, and built upon that by explaining how to run simple example code. | + | I have planned on teaching peers about the topics I had researched into through [[gpu_exploration: my documentation]]. This includes information about the "important" aspects of the GPU hardware, difference in coding specifically for GPU versus just regular C/C++, built upon that by explaining how to run simple example code, and why GPU's are super awesome in the first place. |
| ==== Why I did it ==== | ==== Why I did it ==== | ||
| Line 35: | Line 35: | ||
| === A possible TODO to extend the depth of the project=== | === A possible TODO to extend the depth of the project=== | ||
| - | Chug on learning about GPU's. What is left to do is go back over everything and make it more intuitive and less abstract. Especially since this document requires some prior programming experience and it builds on the fundamentals learned in computer architecture this semester, a technically competent but not experienced person may still have some trouble here and there. In fact, one of the most difficult and time consuming parts of my project was writing it up in a way that would make sense to people other than just me. This may have been due to me not understood everything at the level I was supposed to. As Einstein once said "If you can't explain it simply, you don't understand it well enough." | + | Chug on learning about GPU's. What is left to do is go back over everything and make it more intuitive and less abstract. Especially since this document requires some prior programming experience and it builds on the fundamentals learned in computer architecture this semester, a technically competent but not experienced person may still have some trouble here and there. In fact, one of the most difficult and time consuming parts of my project was writing it up in a way that would make sense to people other than just me. This may have been due to me not understanding everything at the level I was supposed to. As Einstein once said "If you can't explain it simply, you don't understand it well enough." |
| Hopefully the audience will leave this document with a better understanding of GPU's overall. | Hopefully the audience will leave this document with a better understanding of GPU's overall. | ||
| Line 49: | Line 49: | ||
| By Friday (12/7/13) (10 hrs): Have idea of what code I could implement on GPU by putting together the sample code in preparation for demoing cool aspects of the GPU. | By Friday (12/7/13) (10 hrs): Have idea of what code I could implement on GPU by putting together the sample code in preparation for demoing cool aspects of the GPU. | ||
| - | Reality: (10-ish hrs only a few which were fruitful) I still didn't know the specifics but I knew that it would involve image manipulation or processing of some sort. 3 hrs for the first Udacity lecture (included pauses for me to google GPU things) 1+ hr for hw. I thought would have done more code done by now though... | + | Reality: (10-ish hrs only a few which were fruitful) I still didn't know the specifics but I knew that it would involve image manipulation or processing of some sort. 3 hrs for the first Udacity lecture (included pauses for me to google GPU things) 1+ hr for hw. I thought would have more code done by now though... |
| By Monday (12/10/13) (5 hrs): Have (first draft) of GPU lesson/paper write up or power point/ video. | By Monday (12/10/13) (5 hrs): Have (first draft) of GPU lesson/paper write up or power point/ video. | ||
| - | Reality: (0 hrs at this time but it eventually took me 3+ hrs to put lecture stuff together and proctice and so more write up stuff.) This happened a week later. Link to my lecture which I presented during Demos: https://docs.google.com/presentation/d/1NES0bAm9jxaOL4bJg8l-u4YT1W42-Vagd6c48s8__fs/edit#slide=id.p | + | Reality: (0 hrs at this time but it eventually took me 3+ hrs to put lecture stuff together and practice and do more write up stuff.) This happened a week later. Link to my lecture which I presented during Demos: https://docs.google.com/presentation/d/1NES0bAm9jxaOL4bJg8l-u4YT1W42-Vagd6c48s8__fs/edit#slide=id.p |
| By Thursday (12/12/13) (3 hrs): Finish write up/ video lesson of how awesome GPU’s are. | By Thursday (12/12/13) (3 hrs): Finish write up/ video lesson of how awesome GPU’s are. | ||
| Line 68: | Line 68: | ||
| Due (12/19/13) (max 40 hrs spent on project) | Due (12/19/13) (max 40 hrs spent on project) | ||
| + | |||
| + | Reality: About right with an error plus minus 5 hrs. | ||
projects/gpu_exploration.1387509115.txt.gz · Last modified: 2013/12/19 22:11 by nceghtebas
Page Tools
