Programming Master Task List: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
No edit summary
No edit summary
Line 8: Line 8:
| '''Status'''
| '''Status'''
|-
|-
| Split into sub-subteams
| Drive-train low-level autonomous
| Everyone!-
| Andrew + Mike
| We will have several sub-subteams focusing on different areas. Some example areas: low-level mechanism control, drive code, controls programming, autonomous, vision, and minibot programming.
| Create functions to be called by high level autonomous to perform driving tasks
| NOT DONE - Think about what you'd like to work on!
| Code written, needs testing
|-
|-
| Install LabVIEW on 1-2 of the new laptops
| Drive-train low-level drive code
| Andy and friends
| Andrew + Mike
| Install LabVIEW from the 2011 DVD onto one or two of the new (black) laptops. Be sure to apply the update for it!!
| Implement low-level functions to drive robot manually
| Finished, Installed on 2-6<br>
| Code written, needs testing
|-
|-
| Install 2011 Driver's station on AT LEAST two of the new laptops
| Line following algorithm
| Matt
| Peter
| Install 2011 Driver's Station software from FIRST website (link on manual page) onto one or two of the new (black) laptops.  
| Develop line following algorithm - outline on Wiki page?  then implement in code. Needs to implement interface we designed in ThunderDrive.h
| Finished, downloaded on laptops 2-1 and 2-3
| Started research and brainstorming
|-
|-
| Brainstorm autonomous
| Arm low-level
| All
| Calvin + Mike
| Brainstorm AT A HIGH LEVEL autonomous. Not "how" we will do it; this is the "what" we will do. Try to rope in some of the strategy folks. Do ''not'' write code yet! Results should go on a new page on the wiki under programming. Be sure to think ''defensive'' in addition to offensive.  
| Implement arm low-level code -- manual actions first, then "preset" automatic motions.
| Finished, see [[Autonomous|Autonomous]]<br>
| In Progress
|-
|-
| Experiment with vision
| Manipulator low-level
| Justin
| Calvin + Mike
| Use camera on 2011 robot to experiment with detecting the retro-reflective material. Try different lighting scenarios!!
| Implement manipulator low-level code -- manual actions first, then autonomous-specific twists and placement.
| NOT DONE
| Manual done, not tested. Autonomous outlined.
|-
|-
| Drive-train low-level autonomous
| Implement controls code
| Andrew + Mike
| Alex
| Create functions to be called by high level autonomous to perform driving tasks
| Map operator interface functions to low-level robot function calls in arm, drive, etc.  Start with all manual motions for the controls we have defined already on Controls team's wiki pages. Add others as we go.
| Code written, not tested
| Started.
|-
| Arm/Manipulator low-level autonomous
| Calvin + Mike
| Create functions to be called by high level autonomous to perform arm raising and tube manipulation
| NOT DONE
|-
|-
| Create dashboard "autonomous playbook" in lab-view
| Create dashboard "autonomous playbook" in lab-view
Line 47: Line 42:
| create a lab-view program to be able to intuitively chose autonomous strategy before matches
| create a lab-view program to be able to intuitively chose autonomous strategy before matches
| in progress
| in progress
|-
| Design and implement a class for on-robot indicators
| Unassigned
| Design and implement a class that will encompass control of the on-robot feedback mechanisms (lights).
| Not started, low priority
|-
| Autonomous Design
| Matt
| Continue to round out autonomous pesudo-code/detailed design steps on Wiki page.
| Started, but needs much clean-up
|-
| Autonomous Implementation
| Matt
| Implement the various steps detailed in the autonomous design document, using the low-level arm, drive, etc. classes.
| Not yet started
|}
|}


<br>
<br>

Revision as of 15:53, 27 January 2011

Note: These are not in any order currently!!

Task
 Assigned To
 Description
 Status
Drive-train low-level autonomous Andrew + Mike Create functions to be called by high level autonomous to perform driving tasks Code written, needs testing
Drive-train low-level drive code Andrew + Mike Implement low-level functions to drive robot manually Code written, needs testing
Line following algorithm Peter Develop line following algorithm - outline on Wiki page? then implement in code. Needs to implement interface we designed in ThunderDrive.h Started research and brainstorming
Arm low-level Calvin + Mike Implement arm low-level code -- manual actions first, then "preset" automatic motions. In Progress
Manipulator low-level Calvin + Mike Implement manipulator low-level code -- manual actions first, then autonomous-specific twists and placement. Manual done, not tested. Autonomous outlined.
Implement controls code Alex Map operator interface functions to low-level robot function calls in arm, drive, etc. Start with all manual motions for the controls we have defined already on Controls team's wiki pages. Add others as we go. Started.
Create dashboard "autonomous playbook" in lab-view Alex create a lab-view program to be able to intuitively chose autonomous strategy before matches in progress
Design and implement a class for on-robot indicators Unassigned Design and implement a class that will encompass control of the on-robot feedback mechanisms (lights). Not started, low priority
Autonomous Design Matt Continue to round out autonomous pesudo-code/detailed design steps on Wiki page. Started, but needs much clean-up
Autonomous Implementation Matt Implement the various steps detailed in the autonomous design document, using the low-level arm, drive, etc. classes. Not yet started


Retrieved from "https://wiki.penfieldrobotics.com/wiki/index.php?title=Programming_Master_Task_List&oldid=4673"