Recent Changes - Search:

TEAMS Academy Wiki

THS

Explore TEAMS!
for visiting sophomores & juniors


Robotics


EnvBioTech

Bat Design

Assistive Tech

Students

Instructors

TEAMS Forum

TEAMS Calendar

TEAMS Web Site

Wiki Info

edit Robots.SideBar

HW 12 Post Labs 3 & 4

1. Go back and review class notes from the past few days (due next class)

The latter two topics are somewhat more advanced topics that are testable. As for using them in you code, you might find the equations I work out to linearize the Sharp sensors to be useful (it's pretty easy to use). I expect that everyone will use some form of proportional control for Lab 5. Derivative control is a bit more advance, but isn't too hard to implement, and may be quite useful (bonus on Lab 5 if you use it).
(Special note for Red Cohort: I formalized some documentation relating to the PID control discussion we had in class on Monday)

2. Review the Egg Hunt information (due next class)

  • You may request/suggest changes or clarifications in the rules through December 21. After that, rules are fixed.
  • Select a teammate and a robot (for Lab 5 and Egg Hunt)
    • You may team up with anyone from either cohort
    • Make sure you discuss how wo evenly divide the tasks evenly, and set timelines to get the work done!
  • Start brainstorming ideas (do this over the next week)
    • What strategy chould you use?
    • What are the key tasks your robot must perform?
    • How can you divide the programming and other design tasks with your partner?
  • Have an interesting alternative project you'd like to try? If you would like to consider trying something interesting and creative rather than the egg hunt, you (and a teammate) should give me a one to two paragraph description/proposal of comparable complexity (get approval before before vacation)

3. Post your Lab 3 and 4 information on line ( due date: you must "go live" between noon and midnight on Monday)

  • Over the weekend, save a copy of your lab 3 & 4 reports under a new new file
    • edit it to include markup language to format it for the wiki
    • don't go overboard with the wiki formatting, just make it look neat using simple commands!
    • My favorite simple formatting commands...
      • headings (! !! !!! etc.)
      • bullets (* ** *** etc.)
      • numbered lists (# ## ### etc.)
      • indents (-> --> ---> etc.)
      • bold, italics, etc.
      • Colored text is useful
      • etc.
  • Create a wiki page in on your personal page for each of these labs
    • When you upload your lab to the wiki page, all you need to do is cut and paste the text from your revised document into the wiki edit window
    • DO NOT POST THIS INFORMATION ON WIKI EARLY (before noon on Monday) - or else you get a zero for this assignment! Some people have not turned in these assignments yet, so you need to keep "secret" until Monday after noon.
    • The wiki page should include your code using the Attach wiki command - see other sample code we attached to see how we did it
    • You should also include your flow chart
  • Some people asked for an opportunity to revise Lab 3 for additional credit
    • This is your opportunity!
    • To convince me to regrade this (or another assignment)...
      • You should take on an extra programming task(show me something that you did that is unique, interesting, useful)
      • The programming task doesn't have to be a massive undertaking if it was a minor rewrite, but should be more substantial if it is a major rewrite
      • Show me what you can do! Be creative!
  • If you want to make a pdf you can use a free pdf builder found here
Edit - History - Print - Recent Changes - Search
Page last modified on December 19, 2007, at 08:35 AM