https://maslab.mit.edu/2011/w/index.php?title=Special:NewPages&feed=atom&hideliu=&hidepatrolled=&hidebots=&hideredirs=&limit=250&offset=20101227203112&namespace=0Maslab 2011 - New pages [en]2024-03-28T20:42:03ZFrom Maslab 2011MediaWiki 1.16.0https://maslab.mit.edu/2011/wiki/BotClientBotClient2010-12-25T00:11:13Z<p>Yichen: Created page with "'''BotClient''' allows you visualize your robot's processing from another computer. == Running BotClient == # Run <code>add 6.186</code>. # Run <code>/mit/6.186/bin/botclient</..."</p>
<hr />
<div>'''BotClient''' allows you visualize your robot's processing from another computer.<br />
<br />
== Running BotClient ==<br />
<br />
# Run <code>add 6.186</code>.<br />
# Run <code>/mit/6.186/bin/botclient</code>.<br />
#* If this doesn't work, do <code>java -cp /mit/6.186/2006/maslab.jar maslab.telemetry.botclient.BotClient</code>.<br />
# In the "control panel" window, enter your robot's IP address. <br />
# Channels published by the robot will appear in the control panel. Double-click a channel to display it.<br />
<br />
== Running BotClient from Windows ==<br />
<br />
One of the advantages of BotClient is that it is a platform independent program, because it is written in Java. Any Java code can run on any machine as long as there is a Java Virtual Machine designed for that machine. If you have the latest Java Runtime Environment (1.6.0 or greater) installed on your Windows PC, you can run botclient from the command line and it will function just as if you were running it on Athena. <br />
<br />
Assuming you have Java 1.6.0 or later installed: (If you are not sure, go [http://java.com/en/download/index.jsp Download Java]).<br />
<br />
To run BotClient on your Windows PC, do the following:<br />
# Copy maslab.jar onto your PC, and remember the path you stored it to. (For advanced users, add the jar to your CLASSPATH environmental variable)<br />
# Click Start, hit Run<br />
# In the box, type : <code>java -cp "c:/path/to/maslab.jar" maslab.telemetry.botclient.BotClient</code><br />
# Click ok.<br />
<br />
The botclient window you are used to should pop up momentarily.<br />
<br />
== Channel Types ==<br />
<br />
(See <code>maslab.telemetry.channel</code> in the Maslab API for details.)<br />
<br />
; ImageChannel<br />
: As the mouse pointer hovers over a pixel, the RGB and HSV values are reported. Click to see where the color falls on an HSV colorwheel. You can save an image (the captured image is saved in the directory where BotClient was invoked; the filename is <code>capture''NN''.png</code>), as well as pause/resume a video feed. <br />
; TextChannel<br />
: Yup, text. <br />
; ScopeChannel<br />
: For plotting values graphically over time. <br />
; VectorChannel<br />
: Channel for sending vector graphics to the BotClient. Useful for anotating an image or plotting sensor data in space.<br />
<br />
You can also have your robot listen for commands from the BotClient using the "command" field in the control panel.</div>Yichenhttps://maslab.mit.edu/2011/wiki/GyroscopeGyroscope2010-12-24T22:05:06Z<p>Yichen: </p>
<hr />
<div>The gyro is an ADXRS300 (google for datasheet) and the board is<br />
manufactured by Intempco<br />
(http://www.intempco.ca/index.php3?country=can&language=en&content=products&section=motion),<br />
0 to 5V output with 2.5V being center equal to no rotation.<br />
<br />
See the Orc Manual, section 4.3. You can either make a cable as shown there, or (carefully!) solder one piece of female header to a position in the fourth row of the I/O pins on the orcboard, so that you can plug it in directly. The fourth row is also signal, and is connected directly to the third row.<br />
<br />
[[File:Gyro.png]]</div>Yichenhttps://maslab.mit.edu/2011/wiki/Quadphase_encodersQuadphase encoders2010-12-24T21:55:17Z<p>Yichen: </p>
<hr />
<div>== Encoder kit contents ==<br />
<br />
* 2 encoder boards<br />
* 2 1uF capacitors (surface mount, smaller brown one, white strip). Solder these in C1 on each board.<br />
* 2 10uF capacitors (surface mount, larger brown one, clear strip) in C2.<br />
* 4 220ohm resistors (surface mount, labeled 2200) in R1 and R2.<br />
* 12 10K resistors (small surface mount components in a strip, labeled 1002) in R3-R8.<br />
* 2 TLC352 comparators (8-pin chip) in U1. Make sure that pin 1 (nearest the dot) is in the square hole on the board, nearest the printed notch.<br />
* 8 QSC114 phototransistors (smaller, black lens) in Q1-Q4. Make sure that the flat side matches the drawing on the board, and that the shorter lead is in the square hole. These should be put in as far in as they go, and '''as straight as possible'''.<br />
* 4 IR LEDs (larger, clear lens) in LED1 and LED2. Again, check the flat side and the lead length for orientation. These must also be flush against the board and '''as straight as possible'''.<br />
* 4 spacers. Find screws and screw the encoder to the motor mount with the spacers.<br />
<br />
== Assembly ==<br />
<br />
* Solder the components to the boards as indicated above. Plastic guides are available to help align the phototransistors and LEDs; ask the staff to borrow one. First insert the components in the board, paying attention to orientation. Then, slide the plastic guide over them. Try both sides; one is easier to insert and remove. Solder the components, and remove the guide. Remember to return it to one of the staff.<br />
<br />
* Solder a 5-wide ribbon cable into the connector on the back of each board, and assemble the connector on the other end with male header. Pay attention to the ground wire (the square hole, labeled GND, backwards by mistake) for orientation when plugging it in, and mark the wire near the connector if necessary. Put hot glue around the joint of the cable and board- without this, it may break after flexing a few times.<br />
<br />
* Punch two holes in each motor mount for the encoders, if needed. The holes should be 0.74" above the center of the motor shaft, and 0.9" apart.<br />
<br />
* Put tape on the back of the encoder or the motor mount to make sure that nothing is shorted. Add washers if necessary to keep the encoder from touching the motor mount.<br />
<br />
* Print and mount the encoder pattern ([http://web.mit.edu/danyq/Public/encoder.ps encoder.ps]) to the wheel. You can mount it first to a circular disk cut out of cardboard, then glue that to the wheel.<br />
<br />
* Screw the wheels on so that they are as close as possible to the encoders, while not scraping against them. You may even need to press your wheel hubs in further, but make sure the set screw is still accessible. Finally, when connecting the encoders, make sure that the ground wires are going to the "-" pins on the orcboard.<br />
<br />
You can print the pattern on athena with "lpr -Pee08 encoder.ps". That encoder pattern provides 12 ticks per revolution. If you need higher resolution, you may experiment with the triple-res version ([http://web.mit.edu/danyq/Public/encoderhighres.ps encoderhighres.ps]). However, be warned that your component alignment must be extremely accurate for this to work reliably.<br />
<br />
To emphasize, the most important factor is the alignment of the LEDs and phototransistors. Positioning also matters; the hole measurements above are calibrated to the encoder pattern. Finally, make sure that the pattern is as close as possible to the encoders, but does not scrape against them.<br />
<br />
'''Be sure to test your encoders to make sure they not only work, but are reliable. Try counting revolutions in both directions and at different speeds.'''<br />
<br />
[[image:Encoderfront.jpg]] [[image:Encoderback.jpg]]</div>Yichenhttps://maslab.mit.edu/2011/wiki/Kit_contentsKit contents2010-12-22T04:21:29Z<p>Yichen: Created page with "== 2011 Maslab Kit Contents== Each team starts out with the same kit containing: '''Computer and uORC''' * Computer (10.1" EeePC) (150GB SD, Ubuntu Netbook 10.10) ** Computer C..."</p>
<hr />
<div>== 2011 Maslab Kit Contents==<br />
<br />
Each team starts out with the same kit containing:<br />
<br />
'''Computer and uORC'''<br />
* Computer (10.1" EeePC) (150GB SD, Ubuntu Netbook 10.10)<br />
** Computer Charger<br />
* uORC [http://www.orcboard.org/wiki/index.php/Main_Page Orcboard Development Page]<br />
<br />
'''Battery and Cable'''<br />
* 2 Batteries (12 V lead acid) (PN: LA-12V4.5 from [http://www.batteryspace.com])<br />
* Battery Charger<br />
* Cable: Battery to Orc Board<br />
** Fuse<br />
** Fuse holder<br />
** 14 AWG wire (red and black)<br />
** 2 Battery terminal clips<br />
** Battery to Orc Board connector and 2 connector crimps<br />
* Cable: Orc Board to Computer (ethernet)<br />
<br />
'''Pegbot'''<br />
* Pegboard (12” x 12”)<br />
* Caster (6460K31 from McMaster)<br />
* Camera (Microsoft LifeCam VX-2000)<br />
* 2 Motor Assemblies (Banebots wheels, couplings, and brackets http://banebots.com/c/WHB)<br />
** Motor with 6 mm shaft<br />
** Bracket<br />
** Wheel <br />
** Attachment for wheel to motor shaft<br />
** Hardware (screws etc..)<br />
* Container (Tub) <br />
<br />
'''Other'''<br />
* Gyroscope (Analog Devices ADXRS300 with board from Intempco) (collect from a staff member when you see appropriate).</div>Yichenhttps://maslab.mit.edu/2011/wiki/Playing_fieldPlaying field2010-12-22T04:12:02Z<p>Yichen: Created page with "'''Note:''' Please do not step on the playing field with shoes! It makes the carpet dirty! The playing field will have an unknown arrangement, but will be composed of the follo..."</p>
<hr />
<div>'''Note:''' Please do not step on the playing field with shoes! It makes the carpet dirty!<br />
<br />
The playing field will have an unknown arrangement, but will be composed of the following known components. <br />
<br />
=== Balls ===<br />
Balls are 2.25" in diameter and will be painted green or red.<br />
<br />
=== Floor ===<br />
The floor is composed of sheets of light blue indoor/outdoor carpet which may have seams or small gaps. The robot should be able to cope with such imperfections.<br />
* Students should examine the floor of 26-100 as it is notorious for its dips and bumps.<br />
* Small pieces of painters tape may appear on the playing field surface. They will be about 1" long and no less than 3" apart. They will be used by the judges to mark scoring areas for the audience. Their presence, shape, etc are not guaranteed. Robots must be able to cope with such electrical tape appearing at any location.<br />
<br />
=== Walls ===<br />
Walls are guaranteed to be at least 6" high, painted white on the bottom with blue tape on the top 2". Walls may be straight or circular, but the minimum heads-on profile will be at least 3". (i.e., a wall will not be shaped such that you could view one from any direction and see less than 3" of material.) <br />
* The blue line will have irregularly spaced tick marks of identical blue tick marks 1.5" wide.<br />
* There may be imperfections where the wall units meet. Organizers will attempt to minimize these.<br />
* The playing field may have island obstacles, in addition to an irregular perimeter. There will be a path at least 18" wide connecting all targets, scoring areas, and the starting location.<br />
<br />
=== Mouseholes ===<br />
A mousehole is a 6"-high by 10"-wide hole at the bottom of a wall. The mousehole is trimmed on the both sides and the top by a 2"-wide yellow stripe.<br />
* The porch is the 14" by 14" area on the floor centered in front of each mousehole.<br />
* A cardboard box will be placed behind the mouse hole so that from the majority of angles on the playing field, nothing other than the box is visible through the hole. From extreme angles, non-box may be visible.<br />
* There will be a minimum of 2 mouse holes, and a maximum of 4.<br />
* Goals may be located in islands.<br />
<br />
=== Yellow Scoring Walls ===<br />
These walls are yellow with a blue line above. The opposing team's field is guaranteed to be on the other side. These are scoring walls. These walls are not guaranteed to be continuous and may be very short.</div>Yichenhttps://maslab.mit.edu/2011/wiki/Course_policiesCourse policies2010-12-22T04:06:22Z<p>Yichen: Created page with "=== Course Credit === Maslab is a for-credit course with 6 units of P/F and 6 engineering design points. Only passing teams with passing members will be allowed to keep their equ..."</p>
<hr />
<div>=== Course Credit ===<br />
Maslab is a for-credit course with 6 units of P/F and 6 engineering design points. Only passing teams with passing members will be allowed to keep their equipment. There are a number of requirements to receive a passing grade, including:<br />
<br />
* Adequate effort and time invested in Maslab<br />
* Attendance of mandatory events and activities<br />
* Majority of work done in lab<br />
* Completion of assignments<br />
* Daily journal entries<br />
* Final paper<br />
<br />
For explanation of these points, please see the sections below. These requirements are not intended to be an undue burden, but rather to ensure a quality educational experience and that your work is preserved for use by future students.<br />
<br />
=== Damaged Equipment/Tools ===<br />
Maslab uses a lot of expensive hardware, and cannot absorb the cost of replacing equipment that is broken. To encourage students to exercise care in their use of the equipment, including both general-use tools and kit contents, students will be expected to pay for replacements. The staff knows that accidents happen, and consequently Maslab will, at the staff’s discretion, split the cost of a first replacement part with the team.<br />
<br />
Please note that you are responsible for keeping your valuables safe at all times. Maslab parts are expensive. The staff does not take responsibility for stolen parts, and teams will be fined sensor points if a staff member discovers parts unattended.<br />
<br />
In a situation where you destroy your computer or uOrc board, you will be charged the cost to replace the item.<br />
<br />
=== Collaboration ===<br />
Collaboration, with citation when appropriate, is highly encouraged.<br />
<br />
== Activities ==<br />
=== All Students All/Most Days ===<br />
==== Journal Entries ====<br />
Each team should make a short entry in their team journal for each day of IAP. Include what you accomplished, outstanding issues, and any planning you did (all of this need not be more than 3–5 sentences). The journal serves several purposes:<br />
* It allows teams to reflect on their accomplishments and develop short and long-term goals.<br />
* It helps staff members to track teams' progress. (Note: if you have a specific issue that a staff member should address, send an email as well as including it in your journal.)<br />
* It preserves what you've learned from your experience, for the benefit of other teams in both this year and future years. (Note: if this knowledge includes fixes to important bugs, you should also email the staff.) <br />
<br />
Journal entries need not be formal, but they should be informative, clear, and concise. All journal entries will be checked by the staff.<br />
<br />
To create or edit your team journal, click on its link from the Main Page. For instructions, see: http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide<br />
==== Working in Lab ====<br />
Teams are expected to perform the majority of their Maslab work in lab during open hours. Lab space consists of the 6.01 and 6.02 course labs, and is open while staff members are present (typically noon - 10:00 pm, check the calendar for specifics).<br />
<br />
This provides an opportunity for the students to work in a supportive environment, where they can interact with the staff and fellow classmates.<br />
<br />
It also provides a safety net for staff to identify teams that need help or advice.<br />
<br />
=== All Students on Certain Days ===<br />
All students are expected to attend the following events when they are scheduled.<br />
==== Lectures ====<br />
Lectures are held in 32-155, from noon - 4 pm. Classes will most likely end earlier than 4 pm depending on the day. Feel free to bring your lunch!<br />
<br />
As a courtesy to the speakers, we ask you to not use your laptop in lecture. A great effort is put into creating interesting and informative lectures. Using laptops to check email, play video games, or browse the web is insulting to the speaker and creates a classroom distraction.<br />
==== Mock Contests ====<br />
All teams are expected to be present for the mock contests, which will be held in 26-100, starting at 1 pm, ending at 5 pm. Your team must be present when called, and we will run the event like the actual contest. After every team has had a go, we will allow teams to go again on a first-come-first-serve basis.<br />
<br />
To make the best use of the mock contest:<br />
* All mock competitions are manditory<br />
* You should be using your own robot, not the pegbot. After the first Mock Contest, this will become a requirement: teams will not be allowed to participate if they are still using a pegbot.<br />
* Take time before the contest and between rounds to gather pictures for calibration.<br />
* Test code that is functional. The mock contest is a time to test how your robot performs in complex situations, not to try out untested code for the first time. Make sure that you know your robot will do more than spin in circles at each Mock Contest.<br />
* We will not allow you to start your robot at a Mock Contest through any mechanism other than pushing buttons. In particular, it CANNOT be started by running some command over ssh. Please test this before coming to the mock contest; it is easy to setup. Your robot should conform to all contest rules during each of the mock contests.<br />
* Your robot should stop before the 3-minute time limit.<br />
<br />
==== Sponsor Dinner ====<br />
All Maslab students are expected to attend the Sponsor Dinner from 6-8 pm, in the Grier room (34-401). If a student cannot make it, they should email the staff before the dinner with a good reason. A no-show may result in loss of sensor points and/or failure from the course.<br />
<br />
This event is meant to link sponsors with potential interns (i.e. you). It is also meant to be a networking opportunity. Even if you are adamant that you will never work for one of Maslab's sponsors, networking is a worthwhile endeavor. It never hurts to get your name out there and meet people!<br />
<br />
This is a casual-formal event. Please be clean and wear clean clothing. Try to look nice, but there is no need for a suit and tie. Wear what will keep you comfortable and snazzy! Feel free to leave lab before the event to refresh. Additionally, if you are particularly interested in an internship, think about printing out some copies of your resume to distribute, or researching the Maslab sponsors.<br />
<br />
As insinuated in the title, you can expect to eat dinner at this event.<br />
=== Seeding, Impounding and Final Competition ====<br />
These events are mandatory and the rules can be found at:<br />
* [[Assignments#Seeding|Seeding]]<br />
* [[Assignments#Impounding|Impounding]]<br />
* [[Assignments#Final Competition|Final Competition]]<br />
<br />
==== Cleanup Day ====<br />
Cleanup day begins at 12:30 pm in the 6.02 lab, and may last as late as 6:00 pm.<br />
<br />
All students will need to attend to help the staff pack up Maslab materials for storage.<br />
<br />
=== Certain Teams on Certain Days===<br />
Teams are assigned to specific tasks on particular days. These tasks are described in more detail on the Course Calendar, and include:<br />
* Cleanup<br />
* Mock Contest Setup<br />
* Mock Contest Teardown<br />
* Sponsor Dinner Setup<br />
* Sponsor Dinner Teardown<br />
* Contest Teardown<br />
<br />
== Checkpoints ==<br />
Some Checkpoints will involve a 20 minute meeting with two or more staff members and at least one other team. Your entire team must attend this meeting, please email the staff if there is a problem. Missing the meeting will result in loss of sensor points and/or failure from the course.<br />
<br />
If there is a problem attending your assigned time, please contact and arrange a swap with another team. If a swap is made, be sure to email the staff.<br />
<br />
Materials prepared for these assignments should be posted on your team's assignments page, which can be found on the Main Page.</div>Yichenhttps://maslab.mit.edu/2011/wiki/Rules_%26_Sensor_PointsRules & Sensor Points2010-12-22T03:49:54Z<p>Yichen: /* Contest Rules */</p>
<hr />
<div>== Robot Restrictions ==<br />
To participate in the final contest, your robot must meet the following restrictions:<br />
# Robots can have a footprint no larger than 14x14 inches. Height is not restricted, but keep in mind that your team is responsible for housing your robot outside of lab hours. Therefore you will be carrying your robot around (likely in your team tub) and an excessively tall robot will be hard to handle.<br />
# Robots must not use any power sources except those provided by or approved by Maslab.<br />
# Robots must be able to boot unattended and run your robot from button presses (2) without network access.<br />
# Robots may only use one camera (unless you are planning on using stereo vision, in which case you should discuss your plans with staff). <br />
# Robots must not consume more than ~30 sensor points (see below).<br />
<br />
== Sensor Points ==<br />
Each team gets ~30 sensor points (if you can come up with a very convincing reason, the staff may allow you to have a few additional points), to be spent on the following items, provided by Maslab:<br />
<br />
{| border="1" cellpadding="4" cellspacing="0" style="border: 1px solid #000000; border-collapse: collapse;"<br />
|- style="text-align: center; background: #666666; color: #FFFFFF"<br />
! Item<br />
! Value<br />
|- <br />
| Extra drive motor <br />
| 7 points<br />
|- <br />
| Extra stock motor (see stock bin) or self-obtained motor <br />
| 5 points<br />
|-<br />
| Servo <br />
| 5 points<br />
|-<br />
| Ultrasound<br />
| 4 points<br />
|-<br />
| IR<br />
| 4 points<br />
|-<br />
| Solenoid<br />
| 2 points<br />
|-<br />
| Photodiodes, etc.<br />
| 1 point<br />
|-<br />
| Optical encoders pair<br />
| 0 points<br />
|-<br />
| Whisker switch<br />
| 0 points<br />
|-<br />
| Moment buttons<br />
| 0 points<br />
|-<br />
| Original gyroscope and camera in your kit<br />
| 0 points<br />
|}<br />
<br />
Notes <br />
*teams may only use one camera<br />
*home-built optical encoders are also 0 pts/pair<br />
<br />
Teams are allowed to spend at most $100 on additional active components not provided in the Maslab kit. An additional allowance of $50 for batteries and $70 for motors and wheels is allowed for additional customization. Please return our motors, wheels, and batteries if you choose to use this option. Items obtained "for free" should be valued according to how much it would cost another team to get the same part (so if you happened to have a cool motor lying around, you should count it as its value).<br />
<br />
== Contest Rules ==<br />
Your robot will have three minutes on the playing field on each side. Points are scored by the following system:<br />
<br />
'''Possession: 1 point'''<br />
: A ball (of your side's color) is possessed by the robot if it is within the robot chassis or within the robot's control - i.e. if the robot moves, the ball moves.<br />
<br />
'''Porch: 2 points'''<br />
: A ball (of your side's color) is on the porch if it is within a 12 inch radius of the center of the yellow goal.<br />
<br />
'''Goal: 4 points'''<br />
: The ball (of your side's color) remains mostly past the goal entrance after the round is over.<br />
<br />
'''Wall: 6 points'''<br />
: Balls (of your side's color) lobbed over the yellow wall. Remember that your robot cannot go more than half way over the wall (within reason). <br />
<br />
'''The Other Team's Balls: 0 points'''<br />
: If you happen to score, porch, posses, or lob over the wall the other team's balls, these will not count for or against you. On the other hand, if you lob the other team's balls over the wall, then they may no longer have these points thereby decreasing their score.<br />
<br />
'''Outside the Field Penalty: -1 points'''<br />
: If you happened to put a ball outside the field. The party responsible for this will obtain this penalty. If the ball was worth points to the opponent, the opponent will keep their points. If the ball was worth points to the party who put it out of play, those points will be lost.<br />
<br />
'''Stop on Time Penalty: -3 points'''<br />
: Robots that do not stop within 10 seconds after running for 3 minutes will be fined.<br />
<br />
Qualifiers are assessed at the end of the 3 minutes. Therefore, no points will be awarded for capturing then losing a ball.<br />
<br />
A single ball can count for points as a possession, porch, or goal exclusively. If a ball qualifies for more than one of these, the qualifier with the largest point value will be assigned.<br />
<br />
The winner is determined from the sum of two games (once on each side of the field). In the event of ties, the tie-breakers will be determined in the following order:<br />
* Number of balls moved/displaced<br />
* Seating rank<br />
* Robot that weighs the least</div>Yichenhttps://maslab.mit.edu/2011/wiki/Athena_listsAthena lists2010-12-22T03:41:03Z<p>Yichen: Created page with "We have set up several Athena lists for your convenience. You can contact the members of a list by emailing listname@mit.edu. ;maslab-staff :Use this to email the staff members...."</p>
<hr />
<div>We have set up several Athena lists for your convenience. You can contact the members of a list by emailing listname@mit.edu.<br />
<br />
;maslab-staff<br />
:Use this to email the staff members. <br />
;maslab-2011-team-1, ...<br />
:Lists for communicating with your team. <br />
;maslab-2011-teams<br />
:Contains all the above team lists. Feel free to e-mail with questions/ideas that you have!</div>Yichenhttps://maslab.mit.edu/2011/wiki/RepositoriesRepositories2010-12-22T03:40:04Z<p>Yichen: </p>
<hr />
<div>We've set up SVN and git repositories for your teams. Feel free to use whichever one you want. Your SVN repositories are located at (replace NUM with your team number):<br />
<br />
https://svn.csail.mit.edu/maslab/2011/teamNUM<br />
<br />
your git repositories are at:<br />
<br />
https://webdav.csail.mit.edu/~etimmons/maslab/2011/teamNUM.git<br />
<br />
Instructions on how to set up your git client over a webdav share are here (start at step 3): http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt<br />
<br />
Your username is your Kerberos name (or the email address you provided when you registered). Your password is your MIT ID number. If you can't access your repository, it's most likely because we don't have your ID number (Send it to Ellen and Eric to fix it). If you want to change your password, email Eric and he can give you directions on how to do that.</div>Yichenhttps://maslab.mit.edu/2011/wiki/Old_WikisOld Wikis2010-12-22T03:38:06Z<p>Yichen: Created page with "*[http://maslab.mit.edu/2006/wiki/Maslab_2006 2006 Wiki] *[http://maslab.mit.edu/2007/wiki/Maslab_2007 2007 Wiki] *[http://maslab.mit.edu/2008/wiki/Maslab_2008 2008 Wiki] *[http:..."</p>
<hr />
<div>*[http://maslab.mit.edu/2006/wiki/Maslab_2006 2006 Wiki]<br />
*[http://maslab.mit.edu/2007/wiki/Maslab_2007 2007 Wiki]<br />
*[http://maslab.mit.edu/2008/wiki/Maslab_2008 2008 Wiki]<br />
*[http://maslab.mit.edu/2009/wiki/Maslab_2009 2009 Wiki]<br />
*[http://maslab.mit.edu/2010/wiki/Maslab_2010 2010 Wiki]</div>Yichenhttps://maslab.mit.edu/2011/wiki/AssignmentsAssignments2010-11-30T15:24:33Z<p>Maslab: /* Final Competition */</p>
<hr />
<div>=== Overview ===<br />
<br />
Checkpoints should be completed on the assigned date unless you are explicitly excused in which case you should finish the checkpoint ASAP. Please find a staff member to check you off. The check-offs are recorded on the staff wiki.<br />
<br />
=== Checkpoint 1 ===<br />
When you get to lab, your team should find a place to sit and start looking over the wiki. There are some things on the wiki we did not tell you in lecture! It is critical that you thoroughly read through the material in the course related links. <br />
<br />
Your team should wait to be called to do the following things. Your entire team should come when you are called to:<br />
# Pick up your kit.<br />
# Pick up your computer and uOrc board.<br />
<br />
When you can, you should:<br />
# Verify that your kit is complete.<br />
# Assemble the pegbot: bolt on motors, etc.<br />
# Write a "hello world" program. This program should be run on the eeePC and transmit "Hello World" to BotClient running on your personal computer. In other words run BotClient on your computer and send messages to it using the classes in the maslab.telemetry.channel package.<br />
# Program your pegbot to perform a simple task such as driving forward for three seconds and stopping.<br />
# Add a file to your subversion repository.<br />
# Show your finished eeePC hello world and pegbot to a staff member.<br />
<br />
Once you have completed these tasks, you are free to leave. However, you are strongly encouraged to stay in lab until it closes, designing your robot and working on your future assignments. We encourage you to look at the wikis from past years to see what teams have done in the past, and whether those ideas have worked.<br />
<br />
=== Checkpoint 2 ===<br />
You should prepare information (a document or something posted on your wiki) of the following information.<br />
# Must have a robot strategy<br />
# Must have a schedule for IAP<br />
# Must have a mechanical outline, drawings or SolidWorks<br />
# Must have a software architecture outline<br />
<br />
Schedule (To Be Finalized):<br />
*2:00pm - Teams 1 & 2<br />
*2:20pm - Teams 3 & 9<br />
*2:40pm - Teams 5 & 6<br />
*3:00pm - break<br />
*3:20pm - Teams 7 & 8<br />
*3:40pm - Teams 10<br />
*4:00pm - Teams 11 & 13<br />
<br />
=== Checkpoint 3 ===<br />
Use a bump sensor, IR, or Ultrasound to:<br />
# Drive up to a wall, <br />
# sense it (maybe back up), <br />
# and turn to the side<br />
<br />
Experiment with other data inputs (sonar, gyro, camera, encoders).<br />
<br />
=== Checkpoint 4 ===<br />
# Publish images from the camera to the botclient<br />
# Can see and identify the color palate correctly<br />
# This is your chance to get help with your vision code!<br />
<br />
=== Checkpoint 5 ===<br />
# Robot can turn, see a ball, and drive towards it, stop, and publish to the botclient<br />
# This is your chance to get help with your PID code!<br />
<br />
=== Checkpoint 6 ===<br />
Your robot must pass all the compliance tests for the final competition including:<br />
# Must be able to calibrate colors within 1 minute <br />
# Must be able to select starting color (using one of two buttons) Cannot be started over ssh.<br />
# Must stop after 3 minutes of operation<br />
<br />
=== Checkpoint 7 ===<br />
Progress Report Meeting<br />
This checkpoint is the final assessment before the final contest. Your robot should be mostly done, except for minor tweaking.<br />
<br />
After this point (and if at all possible, for some time before it), you should probably be spending most of your time testing your robot in full multi-minute runs of your exploration code on the largest playing area you can find, and finding bugs where your robot gets stuck or otherwise fails to recover from an error condition. Every year, we see several teams who put a lot of effort into robots that get stuck early in the contest because of some stupid bug that they didn't test enough to catch. Don't let this happen to your team.<br />
<br />
# Update staff on status of your robot and notify us of any changes to the strategy or design.<br />
# Please prepare a list of critical things your team feels that it still needs to finish, how critical these are, how long you think it will take to finish these items, and how you plan on doing so.<br />
# Please bring your robot to the meeting.<br />
<br />
Schedule (To Be Finalized):<br />
*1:00pm - Team 1 <br />
*1:20pm - Team 2<br />
*1:40pm - Team 3<br />
*2:00pm - Team 6<br />
*2:20pm - Team 7<br />
*2:40pm - Team 9<br />
*3:00pm - Team 10<br />
*3:20pm - Team 11<br />
*3:40pm - Team 13<br />
<br />
=== Checkpoint 8 ===<br />
Playability Test<br />
<br />
Your robot:<br />
# Must be able to identify color palate in 26-100 in multiple distinct test locations. We will put your robot at different places on the field to test this.<br />
# Must be able to wander, find balls, get balls and attempt to score.<br />
# Robots may be asked to demo for sponsors later in the day for the sponsor dinner. <br />
<br />
Schedule:<br />
*11:00am - Team 1 <br />
*11:20am - Team 2<br />
*11:40am - Team 3<br />
*12:00pm - Team 6<br />
*12:20pm - Team 7<br />
*12:40pm - Team 9<br />
*1:00pm - Team 10<br />
*1:20pm - Team 11<br />
*1:40pm - Team 13<br />
<br />
== Mock Contests ==<br />
The purpose of mock competitions is to allow you to test your robot in real situations. During mock competitions, no students will be allowed in lab unless it is for an emergency robot fix. Mock competitions will often be conducted at the same time as assignments so please make sure that you are there for your scheduled slot for your assignment. Mock competitions 1 and 2 will be run like the first round of the final competition and each team is required to run at least once. Mock competitions 3 and 4 will be run like the final competitions. Winning teams will run in the next round of the bracket after every team has already run once. In mock 4, additional runs will be completed for seating purposes. At the end of all mock competitions, the field will be left up for a few hours for testing.<br />
<br />
== Seeding ==<br />
You will be played against a stationary robot and your seating position will be determined based on the sum of two runs. The top seated teams will be given an advantage during the final competition and will play weaker teams during the first round. It is definitely possible for a weaker team to beat a higher seating team during the final competition so nothing is set in stone!<br />
<br />
Seeding Assignment:<br />
# Please have a finalized TEAM NAME and ROBOT NAME for each robot you will be seeding.<br />
# Please write a paragraph describing your robot and email it to me by the time we finish seeding (5pm). This is for the pamphlet we hand out, advertising and website. People in the past have submitted cute descriptions including lines of code or short poems, etc. Be descriptive and creative!<br />
# We will be taking pictures of your robot for publishing as well.<br />
<br />
== Impounding ==<br />
Impounding will begin the day before the final competition starting at 5pm and ending at 10pm. You may volunteer to impound at any time during this period.<br />
<br />
*No additional changes to the robot can be made after this point<br />
*Return all unused materials and sensors<br />
*Please be prepared to talk about the design and features of your robot for assessment for the engineering award<br />
*Your robot must pass all compliance tests again including:<br />
**Pass all size requirements<br />
**Adhere to all strategy restrictions<br />
*We will tally up sensor points and inform you of any additional costs due to broken materials <br />
*Get your Maslab T-shirts <br />
*Take a team photo with your robot <br />
*Leave your robot, batteries, and kit with us. The battery and computer will be left charging in a locked closet overnight. You may not take any kit contents with you.<br />
<br />
== Final Competition ==<br />
Teams will be able to pick up their robots from Impounding at 10:00 am. You may go straight to 26-100 as we are setting the field up. You should NOT change your robot's code at that point! Using untested code is a sure way to disappointing results at the final contest. Instead, teams should <br />
*ensure that all parts of their robot are functional, batteries are charged <br />
*ensure that the robot will stop after three minutes <br />
*add decoration <br />
<br />
At noon, we will be doing the first round of the competition, no audience members allowed. This round is done so to reduce the time for the final competition. After this round, we will determine the order of the winners bracket and the losers bracket. The field will be changed after this round. You should get lunch when this is over.<br />
<br />
At 3:30pm, all teams will meet in 26-100 to go over the final contest logistics and take a group photo (make sure you're wearing your Maslab t-shirt!). You will also have an opportunity to calibrate your sensors. You may want get food beforehand or keep something to eat with you. <br />
<br />
At 4 pm, spectators will begin arriving. The robots will be set up on the front table of 26-100 and one representative of each team will be in front talking about their robots. <br />
<br />
At 5 pm, the contest will begin. There will always be two teams on deck. When your team is on deck, you should <br />
*make sure that your robot running color is ready and can start from a button press <br />
*have your robot's IP address ready <br />
*do any last minute calibrations <br />
When your team is called, you will need people to do the following <br />
*Robot handler: your job is to carry the robot to the start position and start it. In the event that your robot gets stuck, you and the contest judge will decide together when to stop the round. <br />
*Speaker: your job is to talk about your robot's behaviors. You and the MC will explain what the robot is doing to the audience. <br />
*Bot Client: when your robot is on deck, you will present your robot's IP address to the tech team that will be running the bot client. <br />
<br />
After the contest is over, teams are free to go with their robots. Clean-up teams should stay to help carry materials back to the labs upstairs.<br />
<br />
== Final Paper ==<br />
Your final paper should be 1250–1750 words (5–7 pages) long, and should summarize your<br />
# overall strategy<br />
# mechanical design and sensors<br />
# software design<br />
# overall performance<br />
# conclusions/suggestions for future teams<br />
<br />
The paper must be complete by 11:59 pm on January 30th for your team to receive credit for Maslab. (That's the latest we can push the deadline, since grades need to be turned in).<br />
<br />
Use clean spelling, grammar, and punctuation, and exhibit clear, concise language. You're welcome write in an informal tone and have fun with the paper, but we do expect to see content and will not accept large quantities of BS or incoherent writing. (See previous year's papers for examples of what we expect).<br />
<br />
Your paper should be written as part of the wiki (please do not upload a document). Images should be uploaded to the wiki as well; do not include links (we archive all the papers, and we don't want to lose pictures when links change!).<br />
<br />
Note: if you have suggestions for the staff on improvements to Maslab that weren't included in the feedback survey, please include them in your final papers. We're always looking for ways to improve the course.<br />
<br />
== Resumes ==<br />
Maslab collects student resumes for Maslab and sponsor use. The resumes are used to assess the interests and background of Maslab students, and to provide information for our sponsors who are looking to recruit interns and employees. Please email to Ellen (yichen@mit.edu) your document in PDF or Microsoft Word format.</div>Yichenhttps://maslab.mit.edu/2011/wiki/Maslab_2011Maslab 20112010-11-24T03:25:54Z<p>Yichen: /* Announcements */</p>
<hr />
<div>{| cellpadding="0" style="width: 50%; border-collapse: collapse;"<br />
|- style="vertical-align: top"<br />
|style="background:#CCEEEE"|<br />
==Announcements==<br />
{| cellpadding="0" style="width: 1000px; border-collapse: collapse;"<br />
|- style="vertical-align: top"<br />
|style="width: 5%; background:#CCEEEE"|<br />
|style="width: 95%; background:#CCEEEE"|<br />
[[File:Teams2011.png|right]]<br />
'''Congratulations Teams for a Great Final Competition!''' <br><br><br />
'''First Place: Team 2: PTZERS and putzputz'''<br><br />
'''Second Place: Team 3: We-ski and Monsieur Robot'''<br><br />
'''Third Place: Team 11: Team 11 and reFUSES'''<br><br />
'''Engineering Award: Team 13: 41w and A.W.E.S.O.M.-O''' <br><br />
'''Best Dressed Award: Team 3: We-ski and Monsieur Robot''' <br><br><br />
[[FinalScores| Final Competition Scores]]<br><br />
[http://www.youtube.com/MITMaslab Watch the Youtube Videos on the Maslab Channel]<br><br><br />
'''IAP Videos'''<br><br />
[http://www.youtube.com/mitmaslab#p/c/0/yarssg8vlDA Mock 1 (day 8 of 26) Video]<br><br />
[http://www.youtube.com/mitmaslab#p/c/1/plR4XmozLJo Mock 2 (day 12 of 26) Video]<br><br />
[http://www.youtube.com/mitmaslab#p/c/2/RxiwAiYOfsk Mock 3 (day 17 of 26) Video]<br><br />
[http://www.youtube.com/mitmaslab#p/c/3/5mp4Zuqz7n4 Maslab 2011 Teaser Trailer]<br><br><br />
'''Final Competition Videos'''<br><br />
[http://www.youtube.com/mitmaslab#p/c/6/uMNerkUxYt4 Maslab 2011 Highlights Video]<br><br />
[http://www.youtube.com/mitmaslab#p/c/4/rry8o8ZYR9o Winners Bracket Semifinals]<br><br />
[http://www.youtube.com/mitmaslab#p/c/5/1kvLC3O37OM Competition Finals]<br><br />
<br />
|}<br />
<br />
|}<br />
{| cellpadding="0" style="width: 100%; border-collapse: collapse;"<br />
|- style="vertical-align: top;"<br />
|style="width: 49%"|<br />
__NOTOC__<br />
<br />
== General Information ==<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
*[[Course calendar]]<br />
*[[Assignments]]<br />
*[[Rules & Sensor Points]]<br />
*[[Course policies]]<br />
*[[Playing field]]<br />
*[[Kit contents]]<br />
*[[FAQ forum]]<br />
*[[Tools and Stock Request]]<br />
*[[Athena lists]]<br />
*[[Old Wikis]]<br />
*[[Repositories]]<br />
</div><br />
<br />
== Technical Information ==<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
*[[Software]]<br />
*[[Quadphase encoders]]<br />
*[[Gyroscope]]<br />
*[[BotClient]]<br />
*[[Battery Connection]]<br />
*API Documentation<br />
**[http://java.oracle.com/javase/6/docs/api/ Java 1.6 API]<br />
**[http://web.mit.edu/maslab/2011/doc/maslab/api Maslab Java API 2011]<br />
**[http://web.mit.edu/maslab/2011/doc/uorc/api OrcBoard Java API]<br />
**[http://math.nist.gov/javanumerics/jama/doc/ Jama numerics library API]<br />
*[http://www.orcboard.org/wiki/index.php/Main_Page Orc Board]<br />
**[http://web.mit.edu/6.186/2011/Lectures/manual.pdf uOrcManual]<br />
**[http://web.mit.edu/6.186/2011/Lectures/OldOrc5manual.pdf Old OrcManual] <br />
**[[Orc Layout]]<br />
*Tutorials<br />
**[http://web.mit.edu/6.186/2011/tutorials/imagetutorial/ImageTutorial.pdf Vision]<br />
**[http://web.mit.edu/6.186/2007/tutorials/odomtutorial/odomtutorial.pdf Odometry]<br />
*[[student tips]]<br />
</div><br />
<br />
== Lectures ==<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[Lecture List]] <br />
<br />
* [http://web.mit.edu/6.186/2011/Lectures/Lecture0.pdf Welcome Meeting Slides]<br />
* [http://web.mit.edu/6.186/2011/Lectures/Introduction.pdf Introduction Lecture Slides]<br />
* [http://web.mit.edu/6.186/2011/Lectures/MaslabStrategy2011.pdf Strategy Lecture Slides] [http://web.mit.edu/6.186/2011/Lectures/MaslabStrategy2011.pptx PPTX]<br />
* [http://web.mit.edu/6.186/2011/Lectures/sensors.pdf Sensor Lecture Notes]<br />
* [http://web.mit.edu/6.186/2011/Lectures/maslab-control-talk_2011.pdf Behavior and Control Lecture]<br />
* [http://web.mit.edu/6.186/2011/Lectures/AdminTasks-1-4.pdf 11/4 Administrative Tasks]<br />
* [http://web.mit.edu/6.186/2011/Lectures/maslab-software.pdf Software Lecture Notes] [http://web.mit.edu/6.186/2011/Lectures/maslab-software.pptx PPTX] [http://web.mit.edu/6.186/2011/Lectures/maslab-software-examples.zip Code]<br />
* [http://web.mit.edu/6.186/2011/Lectures/AdminTasks-1-5.pdf 11/5 Administrative Tasks]<br />
* [http://web.mit.edu/6.186/2011/Lectures/controls/ControlsandSignals.pdf Controls Lecture Notes] [http://web.mit.edu/6.186/2011/Lectures/controls/ControlsandSignals.ppt PPT] [http://web.mit.edu/6.186/2011/Lectures/controls/PIDScripts.zip PID Matlab Scripts] [http://web.mit.edu/6.186/2011/Lectures/controls/ControllersFilters.zip Filters, Kalman, ALS Scripts]<br />
* [http://web.mit.edu/6.186/2011/Lectures/maslab-vision.pdf Vision Lecture Notes] [http://web.mit.edu/6.186/2011/Lectures/maslab-vision.pptx PPTX] [http://web.mit.edu/6.186/2011/Lectures/maslab-vision-examples.zip Code]<br />
* [http://web.mit.edu/6.186/2011/Lectures/mapping_maslab_2011.pdf Mapping Lecture Notes] [http://web.mit.edu/6.186/2011/Lectures/mapping_maslab_2011.ppt PPT]<br />
<br />
Tutorials<br />
* [http://web.mit.edu/6.186/2011/Lectures/L298.pdf L298 H-bridge Tutorial Datasheet]<br />
* [http://web.mit.edu/6.186/2011/tutorials/ant-tutorial.pdf Short ant tutorial]<br />
</div><br />
<br />
== Assignments ==<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2"><br />
* [[Assignments#Checkpoint_1|Checkpoint 1]]<br />
* [[Assignments#Checkpoint_2|Checkpoint 2]]<br />
* [[Assignments#Checkpoint_3|Checkpoint 3]]<br />
* [[Assignments#Checkpoint_4|Checkpoint 4]]<br />
* [[Assignments#Checkpoint_5|Checkpoint 5]]<br />
* [[Assignments#Checkpoint_6|Checkpoint 6]]<br />
* [[Assignments#Checkpoint_7|Checkpoint 7]]<br />
* [[Assignments#Checkpoint_8|Checkpoint 8]]<br />
* [[Checkoffs and Sensor Points]]<br />
* [[Assignments#Mock contest|Mock contests]]<br />
* [[Assignments#Seeding|Seeding]]<br />
* [[Assignments#Impounding|Impounding]]<br />
* [[Assignments#Final Competition|Final Competition]]<br />
* [[Assignments#Final Papers|Final Papers]]<br />
* [[Assignments#Resumes|Resumes]]<br />
* [[Lab Cleanup]]<br />
* [[Team Journals]]<br />
|style="width: 2%"|<br />
|style="width: 49%;"|<br />
</div><br />
<br />
== Teams ==<br />
[[Team One|1]] - [[Team Two|2]] - [[Team Three|4]] - [[Team Three|3]] - [[Team Three|6]] - [[Team Seven|7]] - [[Team Nine|9]] - [[Team Ten|10]] - [[Team Eleven|11]] - [[Team Thirteen|13]]<br />
<br />
; [[Team One |Team One - if(config){18.111.97.222}]]<br />
: Erons (Snake Eyes) Ohienmhen, Cory (Olis Force) Robinson, Andrea (Iron Maiden) Lincoln, Allan (Iron Man) Miramonti, Matthew (Mr. Diamonds) Redmond<br />
: [[Team One/Journal|Journal]], [[Team One/Assignments|Assignments]], [[Team One/Final Paper|Final Paper]]<br />
<br />
; [[Team Two|Team Two - putzputz]] <br />
: Leighton Barnes, Stanislav Nikolov, Cathy Wu, Dan Fourie<br />
: [[Team Two/Journal|Journal]], [[Team Two/Assignments|Assignments]], [[Team Two/Final Paper|Final Paper]]<br />
<br />
; [[Team Three|Team Three - We-ski!]] <br />
: Faye Wu, James White, Audren Cloitre, Stephanie Lin<br />
: [[Team Three/Journal|Journal]], [[Team Three/Assignments|Assignments]], [[Team Three/Final Paper|Final Paper]]<br />
<br />
; [[Team Six|Team Six - SLAMBA!!!]] <br />
: Melissa (Piper) Hunt, Xavier Jackson, Shawn Westerdale, Michael Olague<br />
: [[Team Six/Journal|Journal]], [[Team Six/Assignments|Assignments]], [[Team Six/Final Paper|Final Paper]]<br />
<br />
; [[Team Seven|Team Seven - The Mighty Patos!]]<br />
: Christian Segura, Javier Ramos, Rafael Crespo, Roberto Melendez<br />
: [[Team Seven/Journal|Journal]], [[Team Seven/Assignments|Assignments]], [[Team Seven/Final Paper|Final Paper]]<br />
<br />
; [[Team Nine|Vega and the Voltrons (Best team in da GAME)]]<br />
: William Thalheimer, Joel Santisteban, Aaron "Swag master flex" Prindle, Christopher Dessonville, Will Vega-Brown<br />
: [[Team Nine/Journal|Journal]], [[Team Nine/Assignments|Assignments]], [[Team Nine/Final Paper|Final Paper]]<br />
<br />
; [[Team Ten|Team Ten - WIRELESS]]<br />
: Arvin Shahbazi Moghaddam, Wojciech Musial, Tongji Li, Alex Teuffer<br />
: [[Team Ten/Journal|Journal]], [[Team Ten/Assignments|Assignments]], [[Team Ten/Final Paper|Final Paper]]<br />
<br />
; [[Team Eleven|Team Eleven]]<br />
: Kiarash Adl, William Souillard-Mandar, Tim Robertson, Kristen Anderson<br />
: [[Team Eleven/Journal|Journal]], [[Team Eleven/Assignments|Assignments]], [[Team Eleven/Final Paper|Final Paper]]<br />
<br />
; [[Team Thirteen|Team Thirteen - 41w]]<br />
: Dmitri Megretski, Rebecca Han, Kevin Ellis, Bayley Wang<br />
: [[Team Thirteen/Journal|Journal]], [[Team Thirteen/Assignments|Assignments]], [[Team Thirteen/Final Paper|Final Paper]]<br />
<br />
== Staff ==<br />
: Ellen Chen, Kimberlee Collins, Eric Timmons, Bhaskar Mookerji, Geza Kovacs, Sam Powers, Jessica Ruprecht, Arthur Petron, David Benhaim, Ed Olson.<br />
<br />
<br />
|}</div>Maslabhttps://maslab.mit.edu/2011/wiki/Course_calendarCourse calendar2010-11-24T03:02:09Z<p>Yichen: </p>
<hr />
<div>{| style="width:1010px" border="1" cellpadding="7" cellspacing="0"<br />
|-valign="top"<br />
! width="100px" style="background:#efefef;" | Sunday<br />
! width="160px" style="background:#efefef;" | Monday<br />
! width="170px" style="background:#efefef;" | Tuesday <br />
! width="160px" style="background:#efefef;" | Wednesday <br />
! width="160px" style="background:#efefef;" | Thursday <br />
! width="160px" style="background:#efefef;" | Friday <br />
! width="100px" style="background:#efefef;" | Saturday<br />
|-valign="top"<br />
| '''1/2'''<br />
{| style="width:100%" border="1"<br />
|style="background:#faf5ff" |<br />
STAFF: Ellen, Sam, Buro, <br><br />
Isaac, Arthur<br />
|}<br />
| '''1/3'''<br />
{| style="width:100%" border="1"<br />
| style="background:#f5fffa" |<br />
[[Lecture List|Lecture]] (32-155): <br><br />
Starting at noon <br><br />
*Intro, <br><br />
*Sensors, <br><br />
*Strategy/Mechanical<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 1<br />
|-<br />
|style="background:#faf5ff" |<br />
AM: Ellen, Buro <br><br />
<br />
PM: Ellen, Sam, Arthur <br><br />
<br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_1|Checkpoint 1]]<br />
|}<br />
| '''1/4'''<br />
{| style="width:100%" border="1"<br />
| style="background:#f5fffa" |<br />
[[Lecture List|Lecture]] (32-155): <br><br />
Starting at noon <br><br />
*Behavior, <br><br />
*Software Architecture/Threading<br><br><br />
*Edgerton Laser Cutter Training 9:30am <br><br />
*Edgerton Shop Training 3pm<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 2<br />
|-<br />
|style="background:#faf5ff" |<br />
AM: Ellen, Jessica, David, Geza <br><br />
<br />
PM: Ellen, Buro<br><br />
<br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_2|Checkpoint 2]] <br><br />
|}<br />
| '''1/5'''<br />
{| style="width:100%" border="1"<br />
| style="background:#f5fffa" |<br />
[[Lecture List|Lecture]] (32-155): <br> <br />
Starting at noon <br><br />
*Controls, <br><br />
*Vision <br><br><br />
*Edgerton Shop Training 3pm<br />
*Roller Tutorial (Sam) 3-5pm<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 3<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen, Buro<br><br />
<br />
PM:Eric, Geza <br><br />
<br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_3|Checkpoint 3]]<br />
|}<br />
<br />
<br />
| '''1/6'''<br />
{| style="width:100%" border="1"<br />
| style="background:#f5fffa" |<br />
[[Lecture List|Lecture]] (32-155): <br><br />
Starting at noon <br><br />
*Navigation,<br />
*Entrepreneurship Guest Lecture<br><br><br />
*H-bridge tutorial (Ellen) 3-5pm<br />
*"I hate typing on this $@&# eeePC!" tutorial (Eric) 5pm<br />
<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 6<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen, Jessica<br><br />
<br />
PM:Arthur, Geza <br><br />
<br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_4|Checkpoint 4]]<br />
|}<br />
| '''1/7'''<br />
{| style="width:100%" border="1"<br />
<!--| style="background:#f5faff" | --><br />
<!--[[Lecture List|Lecture]] (32-155): TBD--><br />
<!--|- --><br />
| style="background:#f5fffa" |<br />
C: Team 7<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Sam, Cory<br><br />
<br />
PM:Jessica, Eric<br><br />
<br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_5|Checkpoint 5]]<br />
|}<br />
| '''1/8'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
Lab Open noon-5pm<br />
* Hacked Sensor Tutorial (Adnan) at noon<br />
|-<br />
|style="background:#faf5ff" |<br />
WE:Eric, Adnan<br><br />
<br />
|}<br />
|-valign="top"<br />
| '''1/9'''<br />
{| border="1" style="width:100%"<br />
|-<br />
|style="background:#faf5ff" |<br />
WE:<br><br />
|}<br />
| '''1/10'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Assignments#Mock contest | Mock contest]]<br />
* S: Team 9<br />
* T: Team 10<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 11<br />
<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen, Eric<br><br />
<br />
PM:Sam, Cory<br><br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_6|Checkpoint 6]]<br />
<br />
|}<br />
| '''1/11'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Lecture List|Lecture]] (32-155): <br><br />
*1 pm Prof. Russ Tedrake <br><br />
*2:15 pm Prof. Seth Teller<br />
<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 13<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Jessica, Ellen, David<br><br />
<br />
PM:Buro, Geza<br><br />
<br />
|}<br />
| '''1/12'''<br />
{| border="1" style="width:100%"<br />
<!--| style="background:#f5fffa" | --><br />
<!--Lecture (32-155): --><br />
<!-- --><br />
<!--|- --><br />
| style="background:#f5faff" |<br />
C: Team 1<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen, Eric<br><br />
<br />
PM: Buro, Cory<br><br />
<br />
|}<br />
| '''1/13'''<br />
{| border="1" style="width:100%"<br />
<!--| style="background:#f5fffa" | --><br />
<!--Lecture (32-155): --><br />
<!-- --><br />
<!--|- --><br />
| style="background:#f5faff" |<br />
C: Team 2<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Eric, David <br><br />
<br />
PM:Arthur, Buro<br><br />
<br />
|}<br />
| '''1/14'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Assignments#Mock contest | Mock contest]]<br />
* S: Team 3<br />
* T: Team 6 (Team 1)<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 7<br />
|-<br />
|style="background:#faf5ff" |<br />
AM: Jessica, Sam <br><br />
<br />
PM:Geza, Ellen<br><br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_7|Checkpoint 7]]<br />
|}<br />
| '''1/15'''<br />
{| border="1" style="width:100%"<br />
|style="background:#faf5ff" |<br />
WE: Ellen<br><br />
<br />
|}<br />
|-valign="top"<br />
| '''1/16'''<br />
{| border="1" style="width:100%"<br />
|-<br />
|style="background:#faf5ff" |<br />
WE:<br><br />
|}<br />
| '''1/17'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5faff" |<br />
MLK<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 9<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Eric, Ellen <br><br />
PM:Sam, Cory<br><br />
|}<br />
| '''1/18'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5faff" |<br />
C: Team 10<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Jessica, Buro<br><br />
PM:Ellen, Arthur<br><br />
|}<br />
| '''1/19'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Assignments#Mock contest|Mock contest]]<br />
* S: Team 11<br />
* T: Team 13<br />
|-<br />
| style="background:#f5fffa" |<br />
Sponsor Dinner<br><br />
SS: Team 1 (Team 6)<br><br />
ST: Team 2<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 3<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen, Buro<br><br />
PM:All Staff<br><br />
|-<br />
| style="background:#f5fffa" |<br />
[[Assignments#Checkpoint_8|Checkpoint 8]]<br />
|}<br />
| '''1/20'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5faff" |<br />
C: Team 6<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Eric, Jessica, David<br><br />
PM:Geza, Arthur<br><br />
<br />
|}<br />
| '''1/21'''<br />
{| border="1" style="width:100%"<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 7<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Jessica, Geza<br><br />
PM:Sam, Cory<br><br />
<br />
|}<br />
| '''1/22'''<br />
{| border="1" style="width:100%"<br />
|style="background:#faf5ff" |<br />
WE:<br><br />
|}<br />
|-valign="top"<br />
| '''1/23'''<br />
{| border="1" style="width:100%"<br />
|style="background:#faf5ff" |<br />
WE:<br><br />
Field setup in 26-100 from 11am to midnight<br />
|}<br />
| '''1/24'''<br />
{| border="1" style="width:100%"<br />
<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 9<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Jessica, Geza<br><br />
PM:Sam, Cory <br><br />
|}<br />
| '''1/25'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Assignments#Seeding| Seeding]]<br />
* S: Team 10<br />
* T: Team 11<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 13<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen, Sam, David<br><br />
PM:Buro, Arthur<br><br />
<br />
|}<br />
| '''1/26'''<br />
{| border="1" style="width:100%"<br />
<br />
|-<br />
| style="background:#f5faff" |<br />
C: Team 1<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Jessica, Geza<br><br />
PM:Ellen, Eric<br><br />
|}<br />
| '''1/27'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Assignments#Impounding| Impounding]]<br><br><br />
|-<br />
| style="background:#f5faff" |<br />
C: Teams 2<br />
|-<br />
|style="background:#faf5ff" |<br />
AM:Ellen,Buro, David<br><br />
PM:All Staff<br><br />
|}<br />
| '''1/28'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
[[Assignments#Final Competition |Final Competition]]<br />
<br><br><br />
|-<br />
| style="background:#f5faff" |<br />
CT: Team 3<br /><br />
CT: Team 6<br />
|}<br />
| '''1/29'''<br />
{| border="1" style="width:100%"<br />
| style="background:#f5fffa" |<br />
Cleanup Day<br />
<br><br><br />
|-<br />
|style="background:#faf5ff" |<br />
12:00-6:00:<br />
* All Staff<br />
|-<br />
|style="background:#faf5ff" |<br />
6:00:<br />
* Staff Meeting<br />
|}<br />
|}<br />
<br />
==Green==<br />
These student activities are '''mandatory for all students'''. More information can be found in the Course Requirements.<br />
* Lecture: 12:00 noon - 4:00 pm, in room 32-155.<br />
* Mock Contest: 1:00 pm - 5:00 pm, in room 26-100.<br />
* Impounding: We take your robot, beginning at 4:45.<br />
* Sponsor Dinner: 6:30 - 8:30 pm, in the Grier room (34-401).<br />
* Cleanup Day: 12:30 - 6:00 pm, meet in the 6.002 room.<br />
* Final Competition: Open house at 4:00 pm, competition at 5:00 pm, in 26-100.<br />
* Checkpoints 2, 6, 7 and 8: by appointment between 12:00 and 5:00 pm.<br />
<br />
==Blue==<br />
If your team number appears for one of these student tasks, your team is responsible for that task on the day assigned (see Course Requirements for more info). If there is a problem with your team completing an assigned task, please arrange a swap with another team, and then email the staff with the update.<br />
* C: Cleanup. During the last 30 minutes lab is open. Your job is to clean the lab and shop at the direction of a staff member. Please find a staff member 30 minutes before lab closes in the 6.002 lab.<br />
* S: Mock contest setup. Help setup for the mock contest, beginning at 12:00 noon. Please find a staff member assigned to the mock contest (MC) at 12:00 noon in the 6.001 lab.<br />
* T: Mock contest teardown. Help teardown the mock contest, beginning at 5:00. Please find a staff member assigned to the mock contest (MC) at 5:00 in 26-100.<br />
* SS: Sponsor dinner setup. Help setup for the sponsor dinner, beginning at 4:00 pm. Please find a staff member assigned to the Sponsor Dinner (SD) in the 6.001 lab at 4:00 pm.<br />
* ST: Sponsor dinner teardown. Help teardown the sponsor dinner, beginning once the dinner is over (about 8:00 pm). Please find a staff member assigned to the Sponsor Dinner (SD) in the Grier room once the dinner is over.<br />
* CT: Contest teardown. Help teardown the contest, beginning once the contest is over (about 6:30 pm). Please find a staff member once the contest is over.<br />
<br />
==Purple==<br />
Lab staffing assignments are designated as follows:<br />
* AM: 1:00–5:45 on lecture days, 12:00–5:15 on non-lecture days.<br />
* PM: 5:15 - 10:00 on lecture days, 4:45 - 10:00 on non-lecture days.<br />
* WE: 12:00 - 5:00 on weekend.<br />
* MC: 12:00 - 6:00 setting up, orchestrating, and tearing down the mock contest.<br />
* SD: Sponsor dinner setup and tear-down.<br />
* A: Assignment orchestration from noon - 5:00.</div>Maslab