Weekly Homework Sheet Q2 5

If you want, you can create it on an existing worksheet instead, by clicking Existing Worksheet and providing the Location. Click OK. In our example, a new worksheet with an empty PivotTable is created.

Weekly Homework Sheet Q2 5

Quizzes are given during class to assess your understanding of the material recently presented andused in the homework.The written answers will include commands, output from commands, or similar information.The one page quizzes contain 7 questions worth 2 points each for a maximum of 13 points.

The Final Exam is given the last day of classes during the five week sessionto evaluate your comprehension of the material.The exam contains 41 multiple choice questions that are answered on a Scantron sheet for grading byUniversity Testing Services.The maximum grade is 40 points so you can miss one question with no penalty.

Homework, quizzes, and the final exam are weighted according to the number of points. Quizzes and tests are curved, homework is not. For example, you will see both Q2 (quiz #2) and a Q2-curved(quiz #2, curved) versions. Quizzes are returned in class. Final examsare not returned, but you can schedule time with the instructor toreview them. There is no extra credit and final grades are not rounded.

Fri, 17 Dec 2010: Oops. Bug in my implementation of rooms for homework 6. You only ever notice it if an AutonomousPerson moves into a room with no exits. The check for an empty list of exits when picking an exit at random from a room is broken. Method randomExit() in Room should read: def randomExit ():Option[Exit] = if (theExits.isEmpty()) Option.none() else Option.some(theExits.nth(Util.random(theExits.length())))

Mon, 13 Dec 2010: I've uploaded the homework 5 grades on Blackboard. Please have a look at your full set of grades and let me know if anything doesn't agree with your records. In particular, if you received a 0 (usually indicating no submission) for a homework that you're sure you submitted, please inquire. There are a couple of homeworksthat I have received out of band and that are in Nick's hands,so those grades should be updated in the coming days.

Fri, 10 Dec 2010: The submission siteis open for homeworks 6.As I mentioned multiple times, I will accept submissions until Dec 17. Please name your submission adventure.zip, and don't forget to include a text file called README.txt describing your team, your extensions, and the classes you modified and how. Please please don't put it in a Word file (or anything else annoyingly proprietary.)

Thu, 02 Dec 2010: Homework 6 is out. I will accept submissions for this homework until Friday, December 17th, the day after the exam. (Extra day because the homework came out a day after the days I said I would make it available. Only fair.) Source code for the homework is in the Homeworks section of the web site, as usual. Look at it, and familiarize yourself with the code. There's a lot in there for you to look at.

Mon, 08 Nov 2010: A few of you have requested a sample solution for the last question of homework 3, where I asked you to add a stream() operation to atlases that returns a stream of the rooms in the atlases. Here is a sample solution, where I add stream() to the implementation of atlases from homework 2, as opposed to a binary-search-tree implementation. The subtlety for this question was to realize that I wasn't asking you to make atlases themselves support the stream operations, but rather require you to invoke stream() on an atlas to get a stream out of it. That's an alternative way to provide a stream interface that has some advantages. (Of course, there are ways of answering the question correctly and still have atlases directly support the stream operations... Think about it if you want.) The way I implemented it, I added two new (private) classes to the implementation to support the stream operations.

Fri, 29 Oct 2010: In an uncharacteristic display of efficiency and proactiveness, the university cleaning crew quite literally garbage collected the box of homeworks 1 & 2 I left outside my office overnight. Meaning that if you have not picked up your homework 1 or 2 and would like to do so, you'll have to drop me an email...

Thu, 28 Oct 2010: Made a couple more corrections on homework 3 following feedback frompeople trying to test their Atlas implementation with thetester from homework 2. (Which you should do too.) Basically added theroomInFocus() method back in the ADT. Also changed theStream trait from Question 3 to match what we saw inclass. Sorry I didn't see the discrepancy earlier:

Tue, 26 Oct 2010: Here is an updated version of the sheet I read this morning in classsummarizing thetopics we've covered in class, to help you review for themidterm. You will be responsible for anything down in class or writtenin the notes for all lectures up to and include those on Friday Oct 22.

Mon, 25 Oct 2010: I've had a few questions on homework 3 at office hours earlier, theanswer to which may be helpful to everyone. The main one if that forQuestion 2, I'm asking you to change the representation of atlases youimplemented in homework 2. There, you had to use the representation ofatlases that came out of the specification, thus, three concreteimplementation classes corresponding to the three creators. For this homework, youcan ditch those three concrete classes, and replaced them by somethingelse. What that something else is is completely up to you, as you longas it implements something like a binary search tree. You still needto have those three creators for Atlas, of course, since thecreators are part of the signature I'm asking you to implement, butthose creators will need to instantiate and/or do something with yournew concrete implementation e classes. You may also benefit from having helper methodsin your concrete implementation classes (I had two in my implementation).

For question 3, I've added a sample solution to Atlas fromhomework 2 to the Homeworkssections of the website that you can use if you get stuck on question2. I've also tossed in solutions to OString andRoom, even though most of you got those right.

Sat, 16 Oct 2010: Homework 3 is out. Due Wednesday 27 Oct, at 22h00. Helper files are provided in the Homeworks section of the web site. I will add a solution to homework 2 that you can use when you get to Question 2 and 3, but you can use yours too. Testers will come later.

Thu, 14 Oct 2010: Lecture notes from last week's lecture on information hiding are now available. They may come in handy if you want to hide helper functions in your homework and forgot how I did it in class and could not reconstruct it.

Tue, 12 Oct 2010: The midterm will be Friday, October 29th, in class (9h50-11h30). Closed books and closed notes, but I will let you have access to a single-sided 8.5x11 cheat sheet that you can fill with whatever you want.

Wed, 06 Oct 2010: Some of you have spotted the inconsistency in addExit() for question 2 of homework 2. The signature is correct, it's the specification that's wrong! I've updated the homework to the correct specification, so please make sure you read the new version.

Wed, 06 Oct 2010: I've added a copy of my sample solution Direction.scala for homework1 to the Homeworks section of the web site, if you want to use it for homework2. Feel free to use yours, though -- as long is passed all the tests.

Sun, 03 Oct 2010: Homework 2 is out. Because it came out two days late, it will be due two days later than originally planned, so Thursday 14 Oct, at 22h00. I will give you a pristine copy of Direction.scala implementing the code from homework 1, as well as some testing code in the coming days.

Wed, 29 Sep 2010: Submission instructions have been emailed to your husky.neu.edu accounts, including a unique token that you can use to set your initial password. Once you have your password, you can submit homeworks. The submission system can be found at riccardo/cs3500/. Please get in touch with me if there are problems. You can submit multiple times, and we will generally only look at the last thing you submitted by the submission deadline. Note that the submission system will gsend you back an email confirmation of submission, including the file(s) you submitted. Please look at them to make sure that what you submitted was what you thought you submitted. In particular, submittiing .class files instead of .scala files is a common error that will probably get you zero.

Mon, 27 Sep 2010: Okay, automatic extension for homework 1 until Wednesday, September 29, 2010 -- so one extra day -- just so I can get my act together and work out the kinks out of the submission system.

Sun, 26 Sep 2010: A common question: do you have to provide any code for Q2 of homework 1? Answer: NO. The only thing I want you to do for Q2 is to give the equations you need to add to the specification to account for the new creators and operations. Also: I'm still in the process of figuring out submission instructions. Stay tuned...