Website Details

The website is a major part of our project. It will be informing everybody about the progress of our project. It will continuously need to be updated throughout the semester.

Recover Old Website & Add Content

We had a problem in late summer with a meltdown in the Engineering Building. The server where our website was stored had a problem with the cooling fans. Needless to say, we lost everything. The first part of the semester was spent rebuilding what we had last semester, along with adding a lot of content to make it better.

Update Minutes

Brad is the Lead Documenter, and part of that job includes taking minutes at our team meetings. He will produce these minutes to the lead web designer, J.D., and J.D. will put the minutes up on the web. This process will happen repeatedly throughout the semester. See the Minutes page for more details.

Post Contingency Plan

Matt is in charge of the Contingency Plan. He will produce the Contingency Plan to the web designer when everyone is done proofreading the document. J.D. will then put the Contingency Plan on the website. See the Contingency Plan for more details.

Work on Releases Page

J.D. will spend a few days working on designing the Releases Page. Dr. White wants us to have three separate releases for our project, so we decided to have a page dedicated to it.

Work on Robots Page

We have a lot of hardware and a different type of software to work with for our project. J.D. will spend a day or so making a page dedicated to the hardware and software of the robot.

Work on Concepts Page

We decided to come up with a list of concepts that will be needed for our project. Peter volunteered to write about the Object Recognition section, while J.D. will write about the Artificial Intelligence and Obstacle Avoidance. We decided it could be helpful to anyone who looks at our site to see the types of obstacles we must overcome to get our project done. You can see for yourself here.

Update Releases Page

J.D. must update the Releases page to include the updated criteria after talking to Dr. White. Everyone will contribute to the material on the page. J.D. will spawn out the releases page to have a separate page for each release.

Update Progress Section for Movement

Brad is in charge of the Movement module. He will submit a nicely formatted version of his code to J.D., who will then update the progress section to include the movement module.

Update Progress Section for Object Recognition

When Peter and J.D. get a nicely working version of Object Recognition, it will be formatted nicely, and submitted to the progress section for everyone to view .

Update TeamInfo Page

J.D. will update the TeamInfo page to include individual roles in the project. Initially, we had the title of each group member, but Dr. White wanted individual roles to be added to the list.

Code Documentation Plan

J.D. will spend a day to put the coding standards up on the website.

Update Progress Section for Object Recognition

Peter and J.D.'s final version of object recognition will be added to the progress page.

Update Progress Section for Chair Movement

Matt will submit a neatly formatted copy of the Chair Movement module to J.D. to put on the progress page.

Update Releases Page for Release 2

Once the RAFS team meets to discuss the details of Release 2, J.D. will post the updated version online, under the Releases page.