Labs

From 6.034 Wiki

(Difference between revisions)
Jump to: navigation, search
(Currently released labs)
(Currently released labs: hide old labs)
(24 intermediate revisions not shown.)
Line 1: Line 1:
== Currently released labs ==
== Currently released labs ==
 +
 +
None yet
 +
 +
<!--
 +
unreleased labs go here:
* [[Lab 0]] -- due Tuesday, September 15 by '''10:00pm'''
* [[Lab 0]] -- due Tuesday, September 15 by '''10:00pm'''
* [[Lab 1]] -- due Thursday, September 24 by '''10:00pm'''
* [[Lab 1]] -- due Thursday, September 24 by '''10:00pm'''
* [[Lab 2]] -- due Thursday, September 24 by '''10:00pm'''
* [[Lab 2]] -- due Thursday, September 24 by '''10:00pm'''
-
* [[Lab 3]] -- due Thursday, October 29 by '''10:00pm'''
+
* [[Lab 3]] -- due Thursday, November 5 by '''10:00pm'''
-
<!--* [[Lab 4]] -- due Tuesday, October 27 by '''10:00pm'''-->
+
* [[Lab 4]] -- due Tuesday, October 27 by '''10:00pm'''
-
* [[Lab 5]] -- due Thursday, <font style='color:#a00'>October 15</font> by '''10:00pm'''
+
* [[Lab 5]] -- due Thursday, October 15 by '''10:00pm'''
 +
* [[Lab 6]] -- due Monday, November 23 by '''10:00pm'''
 +
* [[Lab 7]] -- due Friday, December 4 by '''10:00pm'''
-
<!--
+
 
-
unreleased labs go here:
+
Optional:
-
* [[Lab 6]] -- due Thursday, November 12 by '''10:00pm'''
+
* [[Lab Bayes|Bayes Lab]]
-
* [[Lab 7]] -- due Tuesday, November 24 by '''10:00pm'''
+
useful formatting tags:
useful formatting tags:
Line 19: Line 25:
Labs are due by '''10pm''' on the due date.
Labs are due by '''10pm''' on the due date.
 +
 +
Schedule TBD (check back at the beginning of the semester).
 +
 +
<!--
Labs are anticipated to be released by '''11:59 pm''' on the release date.
Labs are anticipated to be released by '''11:59 pm''' on the release date.
Line 31: Line 41:
|lab 2|| Search || 9/16 || 9/24
|lab 2|| Search || 9/16 || 9/24
|-
|-
-
|lab 3|| Games || 9/28 || 10/29
+
|lab 3|| Games || 9/28 || 11/5
|-
|-
-
|lab 4|| Constraint satisfaction problems || 10/9 || 10/15
+
|lab 4|| Constraint satisfaction problems || 10/9 || 10/27
|-
|-
|lab 5|| Nearest neighbors & ID trees || 10/2 || 10/15
|lab 5|| Nearest neighbors & ID trees || 10/2 || 10/15
|-
|-
-
|lab 6|| Neural nets & SVMs || 10/22 || 11/12
+
|lab 6|| Neural nets & SVMs || 11/6 || 11/23
|-
|-
-
|lab 7|| Adaboost & Bayes || 11/9 || 11/24
+
|lab 7|| Adaboost || 11/20 || 12/4 (prev: 11/9 || 11/24)
|}
|}
 +
-->
== The online grader ==
== The online grader ==
Line 49: Line 60:
Make sure you have an [http://ca.mit.edu/ MIT certificate], and go to https://ai6034.mit.edu/labs . This will give you a file called <tt>key.py</tt>. Keep this file secure; for example, don't put it in a publicly-readable Athena directory.
Make sure you have an [http://ca.mit.edu/ MIT certificate], and go to https://ai6034.mit.edu/labs . This will give you a file called <tt>key.py</tt>. 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, he will be able to give you more help if your code is understandable.
+
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.
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.

Revision as of 20:16, 28 July 2016

Contents

Currently released labs

None yet


Anticipated lab release schedule

Labs are due by 10pm on the due date.

Schedule TBD (check back at the beginning of the semester).


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