You are not logged in.

Note that this link will take you to an external site (https://shimmer.mit.edu) to authenticate, and then you will be redirected back to this page.

Our goal in assigning a final grade for 6.101 is to balance learning opportunities with the need for assessment. Our strategy is to assign these grades based on demonstrated performance on both labs and exams, which exercise and test different (but complementary) aspects of the subject matter.

## 1) Policy on "Curving" Grades§

We strive to assign grades according to MIT's definitions of what the various letter grades mean. Note that all of these definitions, and hence all of our grading policies, are based on your performance in the subject, not on how you compare against your classmates. We do not curve grades for any class component, nor for overall grades, based on aggregate statistics, and we do not have any limits on the number of students who can receive each letter grade; if we believe that everyone in the class has demonstrated an "A" level of understanding, then everyone in the class will receive an A!

## 2) Labs§

You will be responsible for several laboratory assignments during the semester, each of which consists of a combination of conceptual questions and a substantial programming task. These assignments are intended primarily as a teaching and learning tool, but they are also used to assess your progress with the course material.

Labs will typically release on Friday afternoons, with the bulk of the lab assignment coming due on the following Friday. Labs may have a portion come due on Wednesday, before the associated midpoint recitation.

For each lab, you will receive a .zip file containing a code skeleton and a test harness. You are welcome to work offline until you are satisfied and then to submit your code to our server to be tested for correctness and efficiency. We may run additional tests on our server beyond the ones you are given, so it is in your interest to try to make sure your solution works in a general sense, rather than writing specific code to pass the test cases locally.

In general, your score on each lab will be based on a combination of the conceptual questions answered via the lab's page on the web site, as well as performance against test cases run on the server (which may depend on the correctness and efficiency of your code). In some cases, your score may also depend on the style or complexity of your code, and may need to pass a basic threshold (for good style, or maximum complexity) before the code itself will be scored when submitted to the server.

### 2.1) Lateness§

Our policies around lateness are designed to balance several goals, including encouraging healthy life choices (for example, sleeping at reasonable times without worrying about losing points), providing flexibility for when things get busy or unexpected events occur, and providing a regular structure to help you keep up with the class and avoid falling behind.

To this end, lab exercises can be submitted late for partial credit within a limited window. Your score is based on your most recent submission as of the "cutoff" time (normally 11:59pm the Sunday night following the lab's deadline). Portions of the lab that are complete at the cutoff time and were also complete in your most recent submission before the deadline will receive full credit; and additional portions of the lab that are complete in your most recent submission as of the cutoff time will receive 75% credit. Submissions made after cutoff time will not receive credit.

### 2.2) Extensions§

To help you manage other obligations and unexpected events, we'll automatically forgive some of the lateness penalties from late submissions for each student. At the end of the semester, we will remove the lateness penalties from the three labs that most benefit each student. This does not move any of the deadlines associated with those labs, but it does mean that work submitted over the weekend for those labs will not receive a reduced score because of lateness.

This built-in flexibility is intended to help you manage events that we expect will come up over the course of a typical semester for many students; they are intended to cover lateness that arose from sports, music, interviews, projects, bad days, busy weeks, computer problems, minor illnesses, or any other reason. You do not have to ask for this flexibility to be applied to any particular lab; we will apply it to the maximally beneficial labs for each student at the end of the semester.

If you are experiencing serious personal or medical difficulties that prevent you from completing the work in 6.101 on time, please talk with a Dean at Student Support Services. With their support, we can consider additional extensions or alternative arrangements, but generally only for serious situations that are impacting you for more than one week; we expect the built-in flexibility to handle other cases. Without written support from Student Support Services, we cannot consider any exceptions to the rules outlined on this page.

## 3) Exams§

We will also have one two-hour midterm exam, and one three-hour final exam. The midterm will be held on a Wednesday evening during the semester, and the final exam will be held during finals week. We will offer midterm conflict times for students who cannot attend the regular exam time due to a conflict with another scheduled MIT-related obligation (other classes or extracurriculars). The MIT Registrar will schedule the conflict final exam.

Exams will be given on paper, and they will consist of a variety of questions involving material from the recitations and labs. Proctors will be available to answer administrative and clarification questions during exams, but you should not expect help from staff on solving the problems.

Assignments (both exams and labs) are graded in a two-stage process: first, each assignment is assigned some raw number of "points," and then these points are converted to a real number in the range [0, 10] representing a grade on a continuous scale depicted below:

Note that, while this scale looks similar to a typical 90-80-70-60 grading scale, your score on any assignment is not a raw percentage divided by 10; rather, the scaling is based on our assessment of performance according to MIT's letter-grade definitions. The fact that we grade based on MIT's definitions of letter grades, coupled with the fact that every assignment is different, also means that the transformation from raw points to this score will generally be different on a per-assignment basis (i.e., the "boundaries" above will generally be different for the midterm exam, the final exam, and the lab component of the grade).