Complete Announcements - 6.001

Resources for the material.

May 3, 2006: Clarification for Project 4

  • It appears that many of you are struggling with finding a way to use the ERUMPO-LUMINARIUM method to implement UNDULUM-ARMO. Don't worry about this. If you have to implement UNDULUM-ARMO more directly, that's fine.
  • May 2, 2006: Intro to EECS II

  • Prof. Sodini this morning briefly described the new subject in Course VI to be piloted this fall. You can find a flyer about this course here.

    April 27, 2006: Quiz 2 statistics

  • Here are statistics for Quiz 2:
  • ROUGH grade guidelines are:
  • April 24, 2006: Revised due date

    April 20, 2006: Quiz 2 review sessions

    April 20, 2006: Quiz 2 details

    April 18, 2006: Exam solutions

    April 12, 2006: Lecture on April 20th cancelled

    April 9, 2006: Project 4 typo

    April 9, 2006: Project 4 released

    April 1, 2006: Minor correction in project

    March 31, 2006: Course VI Freshman Open House

    March 21, 2006: Quiz 1 statistics

  • Here are statistics for Quiz 1:
  • ROUGH grade guidelines are:
  • March 17, 2006: Project 3 released

  • Project 3 has been released on the projects page.
  • March 14, 2006: Project 2 clarification In project 2 question 3, the procedure nback is specified as:

    A more correct version of the second statement is:

    March 3, 2006: Quiz 1 review sessions

  • Review sessions for quiz 1 will be held by the Lab Assistants as follows:

  • Also note that there is a web site with Lab information at scripts.mit.edu/~6.001/ including pointers to old quizzes.

    March 2, 2006: Quiz 1 coverage

  • Quiz will cover material up to and including Lecture 6 (Higher Order Procedures). It will not cover the use of map, filter or foldr however.

    February 26, 2006: Quiz 1 details

  • The first quiz for 6.001 will be held on March 7th, from 7:30PM to 9:30PM. You may bring one sheet (8.5 by 11 inches) of notes to the exam, otherwise it is closed book.
  • If you have a conflict with this time, there is a conflict exam scheduled for March 7th from 3 to 5, in 24-121. If you need to take the conflict exam, you must contact Donna Kaufman (dkauf@mit.edu) to let her know.

    February 24, 2006: Project 2 released

  • Project 2 has been released on the projects page.
  • February 21, 2006: Project 1 clarification

  • A few students have been confused about part 6 of the project. In this part a good-bag is a bar that has 10 smarties when the bag is generated at random using the parameters n and p. Thus, for example, you would generate m random bags of n smarties (using p) and test to see whether any one bag has at least 10 orange smarties (which would make it a good bag).
  • February 20, 2006: Saving your project

  • When you are ready to save your project submission, in order to submit onto the online system, you should save your definitions window or interactions window in DrScheme using the option of "Save Definition/Interaction As Text". Doing so prevents DrScheme from saving the buffer as binary files. If you submit a binary file, the online submission system will not accept your file.

    February 20, 2006: Project 1 clarification

  • Some students have asked about problem 4 on project 1. The problem asks for a "recursive procedure". We wanted to clarify that it's absolutely fine if you've written a procedure that leads to an iterative algorithm.

    Here's a little more about the recursive/iterative distinction (lecture 3 talks about this):

    We call any procedure that makes a call to itself a *recursive procedure*. Both fact and ifact-helper (see the lecture) are "recursive procedures" as they both make calls to themselves. For example, if we have

    (define ifact-h (lambda (product count n)
       (if (> count n) product
           (ifact-h (* product count) (+ count 1) n))))
    
    then this is a recursive procedure, because ifact-h includes a call to itself in the body of the procedure.

    We make a distinction, however, between recursive and iterative *algorithms*. fact (in lecture 3) gives a recursive algorithm. ifact gives an iterative algorithm.

    Basically, in scheme, recursive *procedures* are extremely common: in many cases, you'll see an iterative algorithm implemented with a recursive procedure.

  • February 17, 2006: Project 1 correction

  • There is a minor error in the released project (which has been replaced). An earlier release of the project had a typo in two of the test cases. The last two test cases for atleast-b-smarties now read as the following:
    (atleast-b-smarties 10 5 0.6)
    (atleast-b-smarties 15 5 0.3)
    The old version of the project had the following cases, which are incorrect
    (atleast-b-smarties 10 0.6 5)
    (atleast-b-smarties 15 0.3 5)
  • February 10, 2006: Project 1 released

  • Project 1 has been released on the projects page.

  • Return to 6.001 Home Page
    Last modified: Tue Feb 3 18:55:45 EST 2004