Prof. Jonathan Shewchuk
Office: 529 Soda Hall
Akihiro Matsukawa, email@example.com
Bryan Mau, firstname.lastname@example.org
Lu Cheng, email@example.com
Daniel Wang, firstname.lastname@example.org
Yun Seong Park, email@example.com
Mona Kumari Gupta, firstname.lastname@example.org
Bharathkumar Gunasekaran, email@example.com
Harrison Wallace, firstname.lastname@example.org
Rohan Dilip Salantry, email@example.com
Jeff Chang, firstname.lastname@example.org
Lectures are Mondays, Wednesdays, and Fridays from 5:30 pm to 6:30 pm in 155 Dwinelle Hall. The class web page is at http://www.cs.berkeley.edu/~jrs/61b.
Please read this document carefully. It contains answers to most of the questions that students ask during the first few weeks of class. The subjects include: how to contact the staff, prerequisites, textbooks, labs, grading, late penalties, and policies on academic misconduct.
Please check the class web page at the beginning of the semester and regularly throughout. A list of discussion sections, labs, and the TAs who run them is linked from the web page. A tentative syllabus, which includes lecture topics, exam dates, and homework due dates, is also available there. Several online handouts are available. Finally, your reading assignments are listed there. Please keep up with them. There will not be reminders in class.
If you have a general question about something not covered herein, the best option is to post a message on the CS 61B Piazza discussion board. The Piazza board is required reading, whether you post questions to it or not. The TAs and I will post announcements, clarifications, hints, and other information there. If you don't read it, you may be the last to find out about review sessions and major changes to assignments and due dates. We (the instructor and TAs) check the board regularly, and other students will be able to help you too. Other students will also be able to benefit from the answers.
If you don't want to make your question public, or if your question would expose part of the answer to a homework assignment, you may send email to email@example.com. Your email will be forwarded to the instructor and all the TAs. You are always welcome to come to our office hours, posted on our doors and linked from the web page. If the office hours are not convenient, you may make an appointment with any of us by email. There are about 50 of you to every one of us, so please reserve email for the questions you can't get answered in office hours, in discussion sections, or through the Piazza board.
We will be using the Java programming language in this course. Knowledge of Java is not required for this course.
If you have already taken a data structures course in any programming language (e.g., C), you may not need to take CS 61B. If you know Java too, you might be able to skip CS 61B entirely, and if you don't, you might only need to take CS 47B or CS 9G. If you feel that this course may be repeating prior experience, please see Brian Harvey in 781 Soda Hall.
If you are not familiar with the Unix operating system and basic tools, either because you did not take CS 61A, or you got through CS 61A without understanding Unix, it is important that you learn. Some student groups, including CSUA, teach help sessions on Unix.
Sierra and Bates give an introduction to programming in Java. We will be using the Sierra book from the beginning, so purchase it soon. It is an excellent book, and Amazon sells it pretty cheaply. Their book is not meant to be a complete reference to all of the concepts in Java. If you are an experienced C hacker, I also recommend David Flanagan, Java in a Nutshell. The chapter entitled How Java Differs from C can bring a C programmer up to speed in Java remarkably quickly. (That's how I learned Java.)
Goodrich and Tamassia give an introduction to data structures. Although I required this book in the past, I am now listing it as “optional” because it is expensive and some students do fine reading just my lecture notes. But I still recommend buying and reading it, as it discusses data structures in more detail and from a different point of view than I do.
You should also buy the class reader, available at Vick Copy at 1879 Euclid, near Hearst. The bulk of the reader is old CS 61B exams, which will not be provided online (though the solutions are). By far the best way to study for the exams is to try the old ones. The remainder of the reader is information on using the compiler, debugger, and editor.
Electronic copies of all class handouts will also appear on the web page. There may be up to four types of files. Raw ASCII text (readme files and other filenames without an extension) should be printed using the enscript command. PostScript files (filenames ending in .ps) can be viewed using Ghostview (gv), and can be printed using the lpr command. PDF files (filenames ending in .pdf) can be viewed and printed using acroread (Acrobat Reader). Do not use enscript on a .ps or .pdf file! You'll just print reams of garbage. HTML files (filenames ending in .html) can be viewed and printed from Firefox, Mozilla, Netscape, Microsoft Explorer, Chrome, etc.
Because of limited space in the labs, you are only allowed to attend the lab in which you are officially enrolled through TeleBears. If you are not enrolled in any lab (e.g. you're on a waiting list or you're a concurrent enrollment student), attend a lab that has room to accommodate you. (You might have to try several labs to find one whose TA has room for you, so don't wait until the last lab of the week.) For discussion sections, we are not strict, although you are encouraged to attend the section for which you are registered. Your Lab TA will be your “primary” TA—he or she will check off your lab assignments, return your midterms, and help with grading corrections. However, you should feel free to attend any of the staff office hours (not just your own TA's) and ask any of us for help.
Laboratory sections are mandatory. Each week you will solve an assignment in the lab, and have points checked off by your TA. Discussions sections are not mandatory, but many ideas will be discussed in section that don't come up in lecture, and a few of these ideas will appear in the exams and homeworks. Discussion sections are also your best opportunity to ask questions and learn interactively. Midterms will be returned in section.
Account forms will be given out in lab during the first lab, so it is important that you attend. If you miss your first lab, see a TA as soon as you can. It is important that you login to your account and change your password as soon as possible; it takes a day or so after you login for the first time before the system will enable your ability to submit homeworks.
The Soda labs are open from 7:00 am to 6:30 pm Monday through Friday. Outside these hours (and on weekends and holidays), the doors to the building and the elevators are locked, and you will need a keycard to enter. If you are a Berkeley student, your student ID card serves as a keycard, but you must apply to have it enabled at 387 Soda or 391 Cory. If you are a concurrent enrollment student, you must pay $20 for a keycard ($5 non-refundable fee + $15 refundable deposit).
To be admitted to the class, you must be waiting for a lab/discussion section in which a space opens up. If you see a lab section with an open space at a time you can attend, switch to it as fast as you can, even if it's not the time you would prefer. Until then, find and attend a lab whose TA thinks there is enough room to accommodate you. To find a lab that has space, see the online class schedule for laboratory enrollment levels.
If you are something other than a regular Berkeley undergraduate, you need me to approve your concurrent enrollment application online. Unfortunately, that will only happen if the entire waiting list of Berkeley students clears out before the enrollment deadline. This is extremely unlikely, but if you want to take a shot, find and attend a lab that has room to accommodate you, and send me an email to let me know your application is pending.
In addition to exams, there are three types of assignments: homeworks, labs, and projects. Homeworks (roughly one per week) are short programs. Homeworks must be done individually. They are due before lecture on Fridays, and will be graded by one of the class readers. Homeworks are worth a total of 20 points out of the 200, and each homework is equally weighted. Your worst homework grade will be dropped. For example, if there are 11 homeworks during the semester, each of the 10 best is worth 2 points of your final grade.
Labs are short programming assignments that must be done during your scheduled lab period. Labs are done in teams of two. Grading of labs is done by having certain steps checked off by your TA or a lab assistant. Labs are worth 10 points of your final grade, and each lab is equally weighted. Since I expect some of you to have conflicts during the semester, we will drop your lowest two lab grades.
The remaining 70 points of your final grade will come from the programming projects. There will be three of these during the semester. The first and last projects will be worth 20 points; the second will be worth 30 points. You will do the first project individually, and the second and third projects in teams of two or three students each.
The projects are a great deal of work, and cannot be put off until the last moment. If you start working on a project a few days before its due date, you will not be finished by the deadline. Not even close.
Your final letter grade will be determined by the following chart.
There is no curve. Your grade will depend only on how you do, and not on how well everyone else does. CS 61B is not a competition.
Our experience is that grades on homeworks and projects are higher than on exams, so you should assume this will be the case for your own grades and not be surprised if your exam grades are lower than your final grade, while your homeworks and projects are higher.
All assignments will be turned in electronically. Your grades will be recorded online and can be viewed using the glookup program.
If you believe we have misgraded a midterm exam question, return it to me (or your lab TA) with a written note on a separate piece of paper explaining the problem. Staple this paper to the front of the exam. (Not the back! I mean it!) The entire exam may be regraded, so be sure to check the solutions to confirm that your final grade will go up after regrading. All requests for regrades must be made within two weeks after you receive the graded exam. By University policy, final exams may not be regraded.
A course grade of Incomplete will be granted only for dire medical or personal emergencies that cause you to miss the final, and only if your work up to that point has been satisfactory.
We do allow the projects to be turned in late, but there is a penalty. If your project is N hours late, we'll reduce your earned score by ⌈N/2⌉ percent. While this gives you some leeway for putting the final touches on a project, don't stretch the deadlines too far. A project that is one day late will lose 12% of your earned score. After five days, even a perfect solution won't earn a passing grade.
We encourage you to help each other learn the material by discussing the work before you do each assignment. Explaining the meaning of a question or offering advice on what a compiler error message means are interactions that we encourage. On the other hand, you should never have another student's solution or code in your possession, either electronically or on paper. We call this the No Code Rule. If you are not sure whether a particular interaction is appropriate, talk to your TA or the instructor.
If you receive a significant idea from someone in the class, explicitly acknowledge that person in your solution. Not only is this a good scholarly conduct, it also protects you from accusations of theft of your colleagues' ideas. You never lose anything by giving credit generously. (Unless it's credit for writing your code for you.)
Presenting another person's work as your own constitutes cheating, whether that person is a friend, an unknown student in this or another class, or an anonymous programmer on the web who happens to have solved the problem you've been asked to solve. Everything you turn in must be your own doing, and it is your responsibility to make it clear to the graders that it really is your own work. The following activities are specifically forbidden in all graded course work:
Cheating will be policed by advanced cheating-detection software. If you share code with another team, you will be caught, even if you take steps to hide your cheating.
In my experience, nobody begins the semester with the intention of cheating. Students who cheat do so because they fall behind gradually and then panic. Some students get into this situation because they are afraid of an unpleasant conversation with a professor if they admit to not understanding something. I would much rather deal with your misunderstanding early than deal with its consequences later. Even if you are convinced that you are the only person in the class that doesn't understand the material, and that it is entirely your fault for having fallen behind, please overcome your feeling of guilt and ask for help as soon as you need it. Remember that the other students in the class are working under similar constraints—they are taking multiple classes and are often holding down outside employment.