Programming Master Task List: Difference between revisions
From 1511Wookiee
Jump to navigationJump to search
Programming (talk | contribs) (New page: {| width="100%" cellspacing="1" cellpadding="15" border="1" |- | '''Task'''<br> | '''Assigned To'''<br> | '''Description'''<br> |- | Remove hard-coded I/O mappings from Ball_Manipulator<br...) |
Programming (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{| | {| cellspacing="1" cellpadding="15" border="1" width="100%" | ||
|- | |- | ||
| '''Task'''<br> | | '''Task'''<br> | ||
| '''Assigned To'''<br> | | '''Assigned To'''<br> | ||
| '''Description'''<br> | | '''Description'''<br> | ||
|- | |- | ||
| Implement & Test Ball_Manipulator Class<br> | |||
| Calvin<br> | |||
| Implement & Test Ball_Manipulator Class<br> | |||
| Calvin<br> | |||
| Refine Ball_Manipulator class implementation based on additional design details. Test on the robot using mock inputs and outputs and/or dashboard.<br> | | Refine Ball_Manipulator class implementation based on additional design details. Test on the robot using mock inputs and outputs and/or dashboard.<br> | ||
|- | |- | ||
| Ball manipulator OI-based contol<br> | | Ball manipulator OI-based contol<br> | ||
| Christian<br> | | Christian<br> | ||
| Create code to read OI inputs and correctly call the member functions of Ball_Manipulator based on those inputs. Use the Logitech gamepad for the test input device. You will need to guess which inputs will be used for now. Put guesses at inputs in to dsmap.h <br> | | Create code to read OI inputs and correctly call the member functions of Ball_Manipulator based on those inputs. Use the Logitech gamepad for the test input device. You will need to guess which inputs will be used for now. Put guesses at inputs in to dsmap.h <br> | ||
|- | |- | ||
| Make a class (or add to ThunderBot) all robot I/O driver objects<br> | | Make a class (or add to ThunderBot) all robot I/O driver objects<br> | ||
| -<br> | | -<br> | ||
| I/O driver objects '''must''' be singleton (cannot make, for example, two Encoder objects on same channel). These will be used by multiple parts of the program. We need a common place where these are obtainable and/or passable from.<br> | | I/O driver objects '''must''' be singleton (cannot make, for example, two Encoder objects on same channel). These will be used by multiple parts of the program. We need a common place where these are obtainable and/or passable from.<br> | ||
|- | |- | ||
| Dashboard output<br> | | Dashboard output<br> | ||
| Eric & Jeff<br> | | Eric & Jeff<br> | ||
| Dashboard output needs to be more robust and actually output all values as appropriate. A solution is known, but has issues. Work to integrate.<br> | | Dashboard output needs to be more robust and actually output all values as appropriate. A solution is known, but has issues. Work to integrate.<br> | ||
|- | |- | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|- | |- | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
|} | |} | ||
<br> | <br> | ||
Revision as of 19:47, 21 January 2009
| Task |
Assigned To |
Description |
| Implement & Test Ball_Manipulator Class |
Calvin |
Refine Ball_Manipulator class implementation based on additional design details. Test on the robot using mock inputs and outputs and/or dashboard. |
| Ball manipulator OI-based contol |
Christian |
Create code to read OI inputs and correctly call the member functions of Ball_Manipulator based on those inputs. Use the Logitech gamepad for the test input device. You will need to guess which inputs will be used for now. Put guesses at inputs in to dsmap.h |
| Make a class (or add to ThunderBot) all robot I/O driver objects |
- |
I/O driver objects must be singleton (cannot make, for example, two Encoder objects on same channel). These will be used by multiple parts of the program. We need a common place where these are obtainable and/or passable from. |
| Dashboard output |
Eric & Jeff |
Dashboard output needs to be more robust and actually output all values as appropriate. A solution is known, but has issues. Work to integrate. |
