Labs

From 6.034 Wiki

(Difference between revisions)
Jump to: navigation, search
(Currently released labs)
(lab5-ish)
(45 intermediate revisions not shown.)
Line 1: Line 1:
== Currently released labs ==
== Currently released labs ==
 +
''Note that Lab 4 is due before Lab 3.''
 +
* [[Lab 0]] -- due Thursday, September 11 (by 11:59pm)
 +
* [[Lab 1]] -- due Wednesday, September 24 (by 11:59pm)
 +
* [[Lab 2]] -- due Thursday, October 2 (by 11:59pm)
 +
* [[Lab 4]] -- due Thursday, October <span style="color:#c00;">16</span> (by 11:59pm)
 +
* [[Lab 3]] -- due Thursday, October <span style="color:#c00;">30</span> (by 11:59pm)
 +
* [[Lab 5]] -- Cancelled, but made accessible by request.
-
* [[Lab 0]] -- due Friday, September 17
+
<!--
-
* [[Lab 1]] -- due Friday, September 24
+
unreleased labs go here
-
* [[Lab 2]] -- due Friday, October 8
+
* [[Lab 3]] -- due Thursday, October 17 (by 11:59pm)
-
* [[Lab 3]] -- due Friday, October 22
+
* [[Lab 4]] -- due Saturday, November 16 (by 11:59pm)
-
* Lab 4 -- due Friday, November 5
+
* [[Lab 5]] -- due Thursday, November 21 (by 11:59pm)
-
* Lab 5 -- due Friday, December 3
+
 
 +
 
 +
-->
== The online grader ==
== The online grader ==
Line 13: Line 22:
In order for this to work, you need to securely download a "key" that identifies who you are to the grader.
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 [http://ca.mit.edu/ MIT certificate], and go to https://ai6034.mit.edu:444/fall10/tester/ . 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, he 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.
 +
 +
== Viewing your grades ==
 +
You can view your lab grades and all of your previous submissions [https://ai6034.mit.edu/labs/view_stats 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.

Revision as of 00:43, 20 November 2014

Currently released labs

Note that Lab 4 is due before Lab 3.

  • Lab 0 -- due Thursday, September 11 (by 11:59pm)
  • Lab 1 -- due Wednesday, September 24 (by 11:59pm)
  • Lab 2 -- due Thursday, October 2 (by 11:59pm)
  • Lab 4 -- due Thursday, October 16 (by 11:59pm)
  • Lab 3 -- due Thursday, October 30 (by 11:59pm)
  • Lab 5 -- Cancelled, but made accessible by request.


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, he 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