Release 3
In the third release, we are planning on bringing releases one and two together.
We will also trace a path from the chair to the desk, and program the gripper
to grasp the chair automatically. This is also our major debugging phase. A
schedule of each person's task is as follows (Brad - Green, Matt - Red, Peter
- Gray, J.D. - Blue, Entire Group - White):
Grip Chair
Gripping the chair is going to be a major problem with our project. In this
task, we will decide on an algorithm to use, and try to get the robot to grip
the chair from any angle it is approached, as opposed to in Release
2, where the robot assumed the chair leg was in the correct gripping place.
Advanced Chair Movement
This module will start out with the chair movement already written, and devise
a way to make it work in a more confined space (EB 2029). The major problem
with this is getting the robot to know the chair is in front, and ignore that
point.
Module Integration/Testing
This stage of the project will involve merging all of our completed/tested
code modules into a fully functioning automated program. This task will involve
resolving task concurrency and other issues which arise while merging code written
by several programmers. Each module integration will consist of similar tasks.
Evaluate the modules for appropriate entry/exit points. Test task suspension
and resumption. Test overall module interaction. When a module agrees with the
rest of the integrated/tested modules, it will become part of the official release
build.
Coding/Algorithm Design Document
Further refinement of this document will include updates to what is already
written, along with the new algorithms implemented in Release 3.
User's Guide
The third release will require a complete User’s Guide 5 to 10 pages
in length covering several points. Some of the items that will need to be added
to the User’s Guide from Release 2 are: an introductory overview to the
product, instructions for using all functionality, and a table of contents.
The User’s Guide will not be a complete guide for how to use the robot,
but will rather hit some of the high points on using the RAFS team software
and point the user in the direction of ActivMedia’s
robot documentation.
We need to get some sort of feedback on how our project works, so we will present
our project to the CS490 (Robotics) class. A questionnaire will be developed
to hand out to all participants in the feedback. We will tabulate these results,
and post them online.
This document will discuss the positive/adverse implications that may result
from a project in the field of robotics. We will collect ideas from the in class
exercise and from group discussion. This exercise will require compiling a document
for submission to Dr. White and for publishing on our project website.
Website
The website is simply updates at this stage. The Progress
page will need to be updated as modules complete, along with the Minutes
page, etc.
