Labs

From 6.034 Wiki

(Difference between revisions)
Jump to: navigation, search
(Anticipated lab release schedule)
(Anticipated lab release schedule)
Line 39: Line 39:
|lab 6|| Neural nets & SVMs || 11/6 || 11/23 (after Quiz 3)
|lab 6|| Neural nets & SVMs || 11/6 || 11/23 (after Quiz 3)
|-
|-
-
|lab 7|| Adaboost & Bayes || TBD || TBD (after Thanksgiving) <!--11/9 || 11/24-->
+
|lab 7|| Adaboost & Bayes || 11/20 || 12/4 <!--11/9 || 11/24-->
|}
|}

Revision as of 18:25, 12 November 2015

Contents

Currently released labs

  • Lab 0 -- due Tuesday, September 15 by 10:00pm
  • Lab 1 -- due Thursday, September 24 by 10:00pm
  • Lab 2 -- due Thursday, September 24 by 10:00pm
  • Lab 3 -- due Thursday, November 5 by 10:00pm
  • Lab 4 -- due Tuesday, October 27 by 10:00pm
  • Lab 5 -- due Thursday, October 15 by 10:00pm
  • Lab 6 -- due Monday, November 23 by 10:00pm


Anticipated lab release schedule

Labs are due by 10pm on the due date. Labs are anticipated to be released by 11:59 pm on the release date.

Lab Subject Released Due
lab 0 Getting started 9/9 9/15
lab 1 Rule-based systems 9/14 9/24
lab 2 Search 9/16 9/24
lab 3 Games 9/28 11/5
lab 4 Constraint satisfaction problems 10/9 10/27
lab 5 Nearest neighbors & ID trees 10/2 10/15
lab 6 Neural nets & SVMs 11/6 11/23 (after Quiz 3)
lab 7 Adaboost & Bayes 11/20 12/4

The online grader

You will be submitting all of your labs to an online grader. Every lab comes with a file, tester.py, that contains the machinery to test your code and to submit it when you're done.

In order for this to work, you need to securely download a "key" that identifies who you are to the grader.

Make sure you have an MIT certificate, and go to https://ai6034.mit.edu/labs . This will give you a file called key.py. Keep this file secure; for example, don't put it in a publicly-readable Athena directory.

The only thing the grader cares about is whether you pass the tests. It does not care if your code is pretty or well-commented. However, commenting your code can still be important: if you want a TA to help you with your lab, they will be able to give you more help if your code is understandable.

The grader also submits the code to your lab, so that it can be reviewed later by a human. It should go without saying that you should not try to fool or work around the grader, and that the code you submit must be the code you tested. See our grading and collaboration policy, which also explains how your problem set grade is calculated.

Viewing your grades

You can view your lab grades and all of your previous submissions here.

Note that each lab grade is the maximum score out of all of your submissions for that lab. This means that if you re-submit a lab and the command line output shows a lower grade, your grade for the lab will not actually decrease.

Personal tools