Difference between revisions of "ME132a TA-Instructor Meeting, Winter 2011"

From Murray Wiki
Jump to navigationJump to search
Line 33: Line 33:
 
** ER-1: there is some maintenance to do. The unit I was using summer had a motor controller failure. We have bought the
 
** ER-1: there is some maintenance to do. The unit I was using summer had a motor controller failure. We have bought the
 
replacement, but haven't installed yet (it is not a 5 minute thing, as the software driver has changed, so there will be a little tinkering required).
 
replacement, but haven't installed yet (it is not a 5 minute thing, as the software driver has changed, so there will be a little tinkering required).
 +
** New ER-1: new motor control module has player/stage interface?
  
 
* Sensors:
 
* Sensors:

Revision as of 00:49, 17 December 2010

This page is used for facilitating discussion between the instructors and TAs of ME/CS 132a (Winter 2010). Please note that the content of this page is open to the public.

Course Preparation

Course Organization

  • Homework
    • How many: 1/week
    • Due date: 1 week later.
    • How to turn in: box in Steele? Thomas? (will be decided)
    • Office hours: Instructors -- 303 TOM, Andrea and I will decide the TA OH
    • Grading: when? how (percentage, late hw)? 3-5 days grace period, no extension on labs
  • Midterm/Final: NO exams
  • Web page, mailing list
    • Where to set up the web page: Murray Wiki? IMSS? Andrea/Shuo's site?
    • Format: plain HTML? Wiki?
    • Upload: by TA (probably easier)? by instructors?
    • Access (incl. solutions, hw sets, lecture notes): soln-caltech only, others-open to the public
    • Mailing list: email IMSS to set up one?
  • Honor code
    • Collaboration policy: hw? lab? exams? (cf. CDS_101/110a,_Fall_2008)
    • Use of other materials: previous hw solns, other textbooks
  • Textbooks/references: Larry will send us the links (two free textbooks)
  • Prerequisites: check with Richard & Joel, linear alg, basis prob and stat.
  • Programming skills: Matlab & C

Platform

  • Which robots we are going to use (ER-1 from Joel's lab vs Pioneers from JPL)
    • ER-1: there is some maintenance to do. The unit I was using summer had a motor controller failure. We have bought the

replacement, but haven't installed yet (it is not a 5 minute thing, as the software driver has changed, so there will be a little tinkering required).

    • New ER-1: new motor control module has player/stage interface?
  • Sensors:
    • SICK: should be enough
    • Stereo cameras: should be enough
  • Laptops
    • Need a Firewire ports
  • Software stack.
    • What interface/drivers do you want people to work with? (player, ROS, ...)
    • What would be the format for data files? (HDF, carmen, ...)
  • Labs organization
    • For example, the first lab assignment: Should I give them a charged robot with installed drivers, and let them write the software to collect the log? Or should I write all the software and let them collect the log? Is this done as a group (all the students together), as many small groups, or once for individual students?
    • First test on a simulator
  • Matlab vs. Python