Announcements Archive

Final project grades and feedback from your TA are now available on Omnivore, and final letter grades are posted on WebSIS.

Have a great summer!

Don’t forget to submit your individual reflection for the project. It was due at 11am, but will be accepted for as long as the submission form is open.

The final group project is due tomorrow at 11am.

Tomorrow is the last 6.005 class of the semester. We will have a brief wrap-up and summary of the course.

Overall ps4 grades and grade reports are now available on Omnivore.

Your overall ps4 grade was calculated as:
40% × beta-autograde + 42% × final-autograde + 18% × manual-grade

To see your final autograde report, go to Didit, follow the link to your psets/ps4 page, and click “final” in the “Milestones” section.

Your manual grade was assigned by staff inspection of your specifications, tests, documentation, code, and your response to code reviews.

If you have questions, please see the FAQ about grading questions.

Quiz 2 grades are now available on Gradescope, and you will receive an email from Gradescope with a link.

Quiz 2 solutions are posted on the web site. Later this week, your official grade will be recorded on Omnivore.

As with all assignments, please bring grading issues or questions to instructor office hours. Gradescope has a “regrade request” feature, but we will not be using it.

The final group project is now on the course web site, and project teams and mentors are posted on Omnivore.

In today’s class, after we practice team version control with Git, you will meet with your team, create and clone your project repo, check in with your TA mentor, and start writing your team contract. The team contract is due tonight, and the first project milestone is due this Thursday night.

Starting Monday, you will be working on the final project in teams of three people. Please fill out the project signup form by this Friday, April 22, at 10pm.

You should fill out the form now, even if you don’t have a team of three: just choose the appropriate option on the form. You can resubmit another response if your plans change by Friday, and we will use your last submitted response. To find additional team members, use the Piazza teammates post!

If you do not fill out the form, you will not be assigned to a group. We will assume you have dropped the course. All members of a team must submit the form.

As always, if you have any questions, ask on Piazza!

Quiz 2 will be on Friday, April 22, 11am-12noon, in Walker 3rd floor gym. That’s the usual class time, but not the usual class location. The quiz is 50 minutes.

The quiz will cover readings 1-26, from the start of the semester through the out-of-order classes this past week. The quiz will focus on classes after quiz 1, but any and all concepts from readings 1-26 may appear on the quiz. Quizzes from previous semesters can be find in the quiz archive, although their content may differ a bit from the topics we’ve discussed this semester.

The quiz is on paper, so you will not need your laptop. It is closed-book, closed-notes, but you may bring a single 8.5×11” double-sided page of notes, readable without a magnifying glass. The notes must be created by you, not anybody else, since the process of creating a crib sheet is most of the learning benefit of it.

Review sessions will be held:

• on Wednesday during the first hour of class time, 11am-12noon;
• and in office hours on Thursday, 2-3pm and 4-5pm.

At the review sessions, TAs will provide selected exercises and problems from previous quizzes, and will be able to answer any questions you have as you work through them.

As always, you can visit any TA office hours to ask quiz review questions, or post on Piazza.

Beta grade reports and code reviews for ps4 are now available.

• To see your beta autograde report, go to Didit, follow the link to your psets/ps4 page, and click “beta” in the “Milestones” section.
• To see your code reviews, go to Caesar and click on “ps4-beta” under “submitted assignments.”

The ps4 final deadline is Tuesday at 10pm. Make sure you address all your code review comments from humans or marked #important by Checkstyle. If you need a slack day, remember to request it on Caesar before the deadline.

Please ask questions on Piazza and visit lab or office hours.

Code reviewing for ps4 opened this morning. Reviews are due Thursday at 10pm.

If you submitted ps4 beta last night, you can now go to Caesar to find your code reviewing assignment. If you requested an extension, you must wait until the morning after your extended deadline before starting code review.

As a reminder, the course web site has guidelines and instructions for code review and a FAQ about code review deadlines.

Also: the code from class 26 today is now on GitHub. See you on Friday for class on reading 24.

Overall ps3 grades and grade reports are now available on Omnivore.

Your overall ps3 grade was calculated as:
40% × beta-autograde + 40% × final-autograde + 20% × manual-grade

To see your final autograde report, go to Didit, follow the link to your psets/ps3 page, and click “final” in the “Milestones” section.

Your manual grade was assigned by staff inspection of your tests, specifications, implementations, and your response to code reviews.

If you have questions, please see the FAQ about grading questions.

Problem Set 4 is now available. The ps4 beta deadline is Tuesday, April 12, at 10pm.

As announced in class today, we are making a small change to the schedule:

Reading 24 is still due tomorrow night, but class time this Friday will be devoted to working on problem set 4. TAs will be available to answer your questions. There will not be a nanoquiz or any in-class exercises.

We will have three classes next week: 25 on Monday, 26 on Wednesday, and then class 24 (with nanoquiz) next Friday.

We hope this change gives you more time to work on ps4 beta during a busy CPW.

Beta grade reports and code reviews for ps3 are now available.

• To see your beta autograde report, go to Didit, follow the link to your psets/ps3 page, and click “beta” in the “Milestones” section.
• To see your code reviews, go to Caesar and click on “ps3-beta” under “submitted assignments.”

The ps3 final deadline is Tuesday at 10pm. Make sure you address all your code review comments from humans or marked #important by Checkstyle. If you need a slack day, remember to request it on Caesar before the deadline.

Please ask questions on Piazza and visit lab or office hours.

Code reviewing for ps3 is now open. Reviews are due Thursday at 10pm.

If you submitted ps3 beta last night, you can now go to Caesar to find your code reviewing assignment. If you requested an extension, you must wait until the morning after your extended deadline before starting code review.

As a reminder, the course web site has guidelines and instructions for code review and a FAQ about code review deadlines.

Overall ps2 grades and grade reports are now available on Omnivore.

Your overall ps2 grade was calculated as:
40% × beta-autograde + 43% × final-autograde + 17% × manual-grade

To see your final autograde report, go to Didit, follow the link to your psets/ps2 page, and click “final” in the “Milestones” section.

Your manual grade was assigned by staff inspection of your tests, implementations, and your response to code reviews.

If you have questions, please see the FAQ about grading questions.

Hope you’re having a great spring break! Lab hours resume tomorrow if you’re working on ps3 and reading 19.

Problem Set 3 is now available. The ps3 beta deadline is Tuesday, March 29, at 10pm.

Quiz 1 grades are now available on Gradescope. You will receive an email from Gradescope, and if you haven’t used it in another class, the email will explain how to log in.

Quiz 1 solutions are posted on the web site. Later this week, your official grade will be recorded on Omnivore.

As with all assignments, please bring grading issues or questions to instructor office hours. Gradescope has a “regrade request” feature, but we will not be using it.

First, a reminder: Quiz 1 is on Monday at 11am in Walker 3rd floor gym.

Beta grade reports and code reviews for ps2 are now available.

• To see your beta autograde report, go to Didit, follow the link to your psets/ps2 page, and click “beta” in the “Milestones” section.
• To see your code reviews, go to Caesar and click on “ps2-beta” under “submitted assignments.”

In autograding, your implementations were tested against staff tests, and your Graph tests were tested using correct and incorrect staff implementations.

If you’re stuck on a failed test, try following the “hints for failing at …” link to ClassOverflow. After you fix a bug that caused a failure, consider finding that test in your report, following the link, and sharing a hint about what you learned.

The ps2 final deadline is Tuesday at 10pm. Make sure you address all your code review comments from humans or marked #important by Checkstyle. If you need a slack day, remember to request it on Caesar before the deadline.

Please ask questions on Piazza and visit lab or office hours.

Code reviewing for ps2 is now open. Reviews are due Thursday at 10pm.

If you submitted ps2 beta last night, you can now go to Caesar to find your code reviewing assignment. If you requested an extension, you must wait until the morning after your extended deadline before starting code review.

As a reminder, the course web site has guidelines and instructions for code review and a FAQ about code review deadlines.

Quiz 1 will be on Monday, March 14, 11am-12noon, in Walker 3rd floor gym. That’s the usual class time, but not the usual class location. The quiz is 50 minutes, so class will end early on Monday.

The quiz will cover readings 1-16, from the start of the semester to Wednesday’s class on recursive data types. Any and all concepts from readings 1-16 may appear on the quiz. Quizzes from previous semesters can be find in the quiz archive, although their content may differ a bit from the topics we’ve discussed this semester.

The quiz is on paper, so you will not need your laptop. It is closed-book, closed-notes, but you may bring a single 8.5×11” double-sided page of notes, readable without a magnifying glass. The notes must be created by you, not anybody else, since the process of creating a crib sheet is most of the learning benefit of it.

Review sessions will be held:

• Thursday 11am-12noon in 3-270;
• Thursday 8-9pm in 32-044;
• and on Friday during class time.

At the review sessions, TAs will provide selected exercises and problems from previous quizzes, and will be able to answer any questions you have as you work through them.

As always, you can visit any TA office hours to ask quiz review questions, or post on Piazza.

Overall ps1 grades and grade reports are now available on Omnivore.

Your overall ps1 grade was calculated as:
40% × beta-autograde + 45% × final-autograde + 15% × manual-grade

To see your final autograde report, go to Didit, follow the link to your psets/ps1 page, and click “final” in the “Milestones” section.

Your manual grade was assigned by staff inspection of your tests, SocialNetwork code, and your response to code reviews.

If you have questions, please see the FAQ about grading questions.

TAs will run a tutorial session about abstract data types this Wednesday, March 9, 8-9pm, in 32-044.

We will review in-class exercises (including parts we didn’t have time to work on in class) and reading exercises, and try some past quiz questions on ADTs. Lab hours will still run concurrently, so LAs will be available to help with problem set questions.

Visit the course calendar to see all scheduled office, lab, and tutorial hours.

Problem Set 2 is now available. The ps2 beta deadline is Tuesday at 10pm.

Beta grade reports and code reviews for ps1 are now available. As before:

• To see your beta autograde report, go to Didit, follow the link to your psets/ps1 page, and click “beta” in the “Milestones” section.
• To see your code reviews, go to Caesar and click on “ps1-beta” under “submitted assignments.”

In autograding, your implementations were tested against staff tests, and your tests were tested using correct and incorrect staff implementations.

If you’re stuck on a failed test, try following the “hints for failing at …” link to ClassOverflow. After you fix a bug that caused a failure, consider finding that test in your report, following the link, and sharing a hint about what you learned.

The ps1 final deadline is Tuesday at 10pm. Make sure you address all your code review comments from humans or marked #important by Checkstyle. If you need a slack day, remember to request it on Caesar before the deadline.

Good luck! Please ask questions on Piazza and visit lab or office hours.

Overall ps0 grades and grade reports are now available on Omnivore.

Your overall ps0 grade was calculated as:
40% × beta-autograde + 45% × final-autograde + 15% × manual-grade
(if your final-autograde was lower than the beta, beta-autograde was used for that component unless otherwise noted)

To see your final autograde report, go to Didit, follow the link to your psets/ps0 page, and click “final” in the “Milestones” section.

Your manual grade was assigned by staff inspection of your personal art, personal art code, and your response to code reviews.

For clarifications about grading comments on ps0, please ask the staff member who made the comment. The graders’ usernames can be found in your grade report. Other questions about grading should be brought to instructor office hours.

If you have questions about readings/classes 6 or 7 on specifications, TAs will run tutorial sessions about specs on Monday and Wednesday of this upcoming week (Feb 22 and 24), 7-8pm, in 32-044.

We plan to review both in-class exercises and reading exercises, and may try some past quiz questions on specifications. Since ps1 is all about specs, the tutorial may be helpful to you for ps1. Lab hours will still run concurrently, so LAs will be available to help with problem set questions.

Visit the course calendar to see all scheduled office, lab, and tutorial hours.

Have a great weekend!

Problem Set 1 is now available. The ps1 beta deadline is Tuesday at 10pm.

We’ve released an updated version of Eclipseonut to fix a couple issues that have been discovered in class. Before class tomorrow, please update Eclipseonut:

1. Open Eclipse.
2. Go to the Help menu → Installation Details.
3. On the Installed Software tab, find Eclipseonut in the list.
4. Click to select it, then click the Update… button.

The new version number starts with 0.1.3. Please post on Piazza if you have any trouble updating. Thanks!

Beta grade reports and code reviews for ps0 are now available.

• To see your beta autograde report, go to Didit, follow the link to your psets/ps0 page, and click “beta” in the “Milestones” section.
• To see your code reviews, go to Caesar and click on “ps0-beta” under “submitted assignments.”

In autograding, your submission was tested both by the public tests that were shown to you and by hidden tests. If you failed any hidden tests, you’ll see the name of the test that failed and a stack trace of where it failed. The test case inputs or code will not be revealed to you, either by Didit or by 6.005 staff. The hidden tests are like bug reports from users in the field, where you get a rough idea of what the user was trying to do (the test name) and a stack trace of where the failure occurred. You need to figure out what’s wrong with your code from those clues.

If you’re stuck, the Didit report has “hints for failing at …” links that lead to ClassOverflow, a site where you might find hints written by classmates who also had that bug. After you fix a bug that caused a test to fail, consider finding that test in your report, following the link to ClassOverflow, and sharing a hint about what you learned.

You should revise ps0 for the final deadline on Tuesday at 10pm. You can take slack on this deadline using Caesar, just like the beta deadlines.

Your final version of ps0 should fix any bugs found by the hidden tests, and you must address each of your code review comments made by humans or marked #important by Checkstyle, as described in the code reviewing guidelines.

Your overall ps0 grade will be calculated as:
40% × beta-autograde + 45% × final-autograde + 15% × manual-grade

The manual-grade will be assigned by staff graders based on how you addressed code review comments and the quality of your code.

Good luck! Please ask questions on Piazza and visit lab or office hours.

Problem Set 0 code reviewing is open as of this morning to everyone who took 0 or 1 slack days on ps0 beta. Go to Caesar to find your reviewing assignments.

Please see the Code Reviewing page for guidelines and instructions. Remember that your classmates are people like you who are trying hard like you. Be nice.

Code reviews are due by 10pm today (unless you’ve used 2 slack days, in which case you do code review tomorrow).

If Eclipseonut was not working for you in class today, please check that your Eclipse and Java are up-to-date:

1. Eclipse: to check that you are using the correct version of Eclipse, go to Help → About Eclipse (Eclipse → About Eclipse on OS X). You should see “Version: Mars.1 Release (4.5.1)” in the dialog.

2. Java: to check that the correct version of Java is installed, run java -version in a terminal. You should have “1.8.0_71” or later.

   You must also check that Eclipse is using the correct version of Java: go to Help → Installation Details → Configuration tab. On about line 30, there should be a -vm flag, look for version 1.8.0_71 or later after -vm.

If you encountered technical issues in class today, use Git to push your work to Athena: in a terminal, cd to your Eclipse workspace directory, then cd ic03-testing, then Git add-commit-push. Visit lab or post on Piazza to resolve the issue for next class.

1. Due to the downtime last night and earlier today, where 6.005 sites and repos were offline due to still-unexplained AFS issues, some adjustments you should be aware of:

• Nanoquiz 2 was graded as best-2-out-of-3. Grades are on Omnivore.

• The deadline for ps0 problems 1-3 is 10pm tonight. Your code is not graded at this deadline: continue to revise and improve all of ps0 for the beta submission on Tuesday.

• The deadline for GitStream exercises is also 10pm tonight, since the Getting Started page was unavailable. If you haven’t done those exercises, please do.

2. If you were not able to collaborate using Eclipseonut in class today, please visit lab hours over the weekend and get help from the LAs. Eclipseonut will be required for all in-class exercises, starting Monday.

Thanks for joining us on the wild ride that is 6.005, and enjoy the snow!

Problem Set 0 is now available.

For help getting started with Java, Eclipse, and Git: visit office hours (2-3pm and 4-5pm in the 32-G7 lounge) and lab hours (7pm to 10pm in 32-044) today and tomorrow. TAs and LAs will be there to help you install and set up the tools you need for 6.005.

You must have all the tools set up and ready before class at 11am on Friday. See Part I (problems 0 to 3) of ps0.

ps0 beta is due next Tuesday, February 9, at 10pm. ps0 final will be due the following Tuesday. See the General Information page for a description of beta and final problem set deadlines.

If you need help with course material or programming in Java, please see the calendar of office and lab hours.

For almost all questions, Piazza is the place to ask. Once again, welcome to 6.005!

Welcome to 6.005!

In class today you completed reading exercises in reading 1 and took a first nanoquiz. Your grades for the reading exercises and nanoquiz are now on Omnivore.

Reading 2 is online.

Reading exercises are due 10pm the evening before class, so reading 2 exercises are due at 10pm tomorrow.

In class on Friday we will take a nanoquiz on reading 2. Nanoquiz grades are posted at or soon after the end of class, at which point the 7 × 24-hour makeup period begins. See nanoquiz grading and makeup for details.

If you have questions, please ask on Piazza.

You’re getting this message because you preregistered for 6.005. Welcome! A few announcements:

1. In order to join the class properly, you must fill out this signup form. Please fill it out now. 6.005 is oversubscribed, so you must fill out this form before the end of the first class meeting on Wednesday, or else you won’t be able to take the course for credit.

2. 6.01 is a required prerequisite for this course. If you haven’t taken 6.01 or 6.S04, you won’t be able to take 6.005 for credit, only as a listener.

3. You will need to bring a laptop to every 6.005 class meeting, including the first meeting on Wednesday, February 3. If you don’t have a laptop, IS&T can lend you one.

See you next Wednesday!