User Tools

Site Tools


projects:cpu_display

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
projects:cpu_display [2013/12/19 23:26]
lsilverwolf
projects:cpu_display [2013/12/19 23:34]
lsilverwolf
Line 130: Line 130:
  
 ====Work Plan==== ====Work Plan====
-**Goal** +**Goal**\\
 To create a physical display that explains what a CPU does and how it works. There will be several nested black boxes (IRL) and each one will be labeled with a description explaining what goes on inside of that black box. The largest box will be the CPU as a whole and the smallest black boxes will be the simple gates. The audience for these descriptions will be a parent or sibling that doesn’t know anything about computer architecture. To create a physical display that explains what a CPU does and how it works. There will be several nested black boxes (IRL) and each one will be labeled with a description explaining what goes on inside of that black box. The largest box will be the CPU as a whole and the smallest black boxes will be the simple gates. The audience for these descriptions will be a parent or sibling that doesn’t know anything about computer architecture.
  
 I would also like to show some simple operations taking place in the CPU, preferably user-controlled. I could have a knob or series of buttons that activated a different set of lights through the display depending on the operation, or it could be as simple as using different colors of yarn for different operations with careful labeling. I would also like to show some simple operations taking place in the CPU, preferably user-controlled. I could have a knob or series of buttons that activated a different set of lights through the display depending on the operation, or it could be as simple as using different colors of yarn for different operations with careful labeling.
  
-**Final demo** +**Final demo**\\
 The above display with a short presentation that I could give at expo explaining what a CPU is and why Computer Architecture is so cool. The above display with a short presentation that I could give at expo explaining what a CPU is and why Computer Architecture is so cool.
  
-**Rough Schedule** +**Rough Schedule**\\
 Wednesday Dec 4th - Have “schematic” of entire system, begin procuring boxes (2 hours)\\ Wednesday Dec 4th - Have “schematic” of entire system, begin procuring boxes (2 hours)\\
 Saturday Dec 7th - Decide which operations will be shown and how (1 hour)\\ Saturday Dec 7th - Decide which operations will be shown and how (1 hour)\\
Line 152: Line 149:
  
 ==== Work Plan Reflection ==== ==== Work Plan Reflection ====
 +I massively mis-judged this project. Not only did I want to include all of the possible detail on every level of abstraction,​ but I also wanted to have non-trivial user control over information flow, both of which turned out to be harder than they seemed. ​
 +
 +As far as the schedule goes, the order I laid out for myself did not end up to be effective either. I did come up with the schematic first, but the rest was dictated by the boxes that I had available to me, so I built the project module-by-module rather than writing all the descriptions and then putting them on the boxes. I also mis-judged how long it would take to assemble something of this scale, so instead of taking 4 hours to put it all together, it took me at least 20 total. Therefore, I was unable to implement the user-controlled data path following through the system.
  
 +I also did not judge how far apart Monday and Thursday are in finals week, so instead of having my whole project done by Monday, I only had 1.5 modules done by that point. Therefore, I was unable to give the type of presentation that I had anticipated giving during the final block for CompArch.
  
-Include everything necessary ​to pick up where you left off. This should include:  +I did implement a basic version of what I had planned ​to do, and I did learn a lot doing it, so overall I'd call my project ​a success. I was just not super accurate in my original work plan.
- Code  +
- Schematics  +
- build instructions  +
- A list of difficulties ​and ‘gotchas’ while doing this project  +
- Work Plan reflection  +
- A possible TODO to extend the depth of the project ​+
projects/cpu_display.txt · Last modified: 2013/12/19 23:35 by lsilverwolf