CS 189 at UC Berkeley
We will use Piazza as the 'one-stop shop' throughout the semester: for a Q&A forum and for official announcements. Enrollment in Piazza is mandatory. If you have questions about anything related to the course, please post them on Piazza rather than emailing the instructor or TAs. Please do not post anything resembling a solution to a homework problem before it's due. If in doubt, you should make your post private (visible to instructors only). We always welcome any feedback on what we could be doing better. See the Piazza Etiquette section for more on using Piazza. To join the class on Piazza, follow this link piazza.com/berkeley/spring2018/compsci189289a.
All homework will be submitted through Gradescope, and all homework and exam grades will be given back through Gradescope. To join the class on Gradescope, go to gradescope.com and enter this code:
To complete self-grades, look for the self-grade form in that week's solutions file. After filling out the form, click 'download JSON' and submit that JSON to Gradescope. When filling out self-grade form, use the following guidelines:
- 0 = Didn't attempt or very very wrong,
- 2 = Got started and made some progress, but went off in the wrong direction or with no clear direction,
- 5 = Right direction and got half-way there,
- 8 = Mostly right but a minor thing missing or wrong,
- 10 = 100% correct.
At the end of the semester, all self-grades are re-calibrated. Note that everyone in the class will introduce noise when self-grading, and we'll have this distribution;we don't expect perfect self-grades. if you are not deliberately mis-grading, then you will be fine.
- 0: Least Squares Framework
- 1: Features, Regularization, Hyperparameters and Cross-Validation
- 2: Maximum-likelihood, Interpretation of Ordinary Least Squares, MAP interpretation of regularization, and the bias/variance tradeoff understanding of overfitting.
- 3: Weighted least squares and non-white noise, total least-squares and eigenmethods for optimization
- 4: Total least squares, Principal component analysis
- 5: canonical correlation analysis, nonlinear least squares, and gradient descent
- 6: Neural nets and stochastic gradient descent
- 7: Regression approaches to classification: generative models like LDA/QDA and discriminative models including neural nets and logistic regression
- 8: Choosing loss functions, hinge-loss and SVMs
- 9: k-Means, Expectation Maximization
- 10: Spring Break
- 11: Decision trees, boosting, bagging, and ensemble methods
- 12: Convolutional neural nets and regularization revisited
- 13: Unsupervised Learning: Nearest Neighbors
- 14: Sparsity and Decision Trees
- 15: Clustering and Generative Adversarial Networks
- 16: Supervised feature discovery by metric learning and contrastive loss
All materials can be found on the front page.
There is no textbook for this class. Instead, there is a set of fairly comprehensive lecture notes. Make sure you revisit the notes after lecture. Each note may be covered in one or more lectures.
Release Schedule: Discussion worksheets for the Tuesday discussions are released the day before at 10 p.m. Discussion solutions may be published Tuesday evening. We will do our best but cannot guarantee discussion solutions.
The discussion sections may cover new material and will give you additional practice solving problems. You can attend any discussion section you like.
Release Schedule: Every Friday at 10 p.m. (with some exceptions in case of HW extensions), homework for the coming week is released. Homework is then due on Gradescope the following Friday at 10 p.m.; the solutions for that homework will be released 2 hours after the deadline. You are expected to self-grade your homework and submit your self-grades by the following Tuesday. Reader-graded subsets of the homework are returned to you, graded, approximately one week after the deadline.
All homeworks are graded for accuracy and it is highly recommended that you do them. You are expected to show your work and justify all of your answers. Your lowest homework score will be dropped, but this drop should be reserved for emergencies. See the self_grade form (instructions on form).
Ethical behavior is an important part of being an engineer. It is a part of our responsibility to act ethically and honestly, and moreover, ethical behavior is what helps you learn best. Cheating is fundamentally dishonest and antisocial behavior. We have a zero-tolerance policy for cheating. First-time offenses will result in negative points for the corresponding assignment and a meeting with the professors and/or head TAs. Second-time offenses will see more serious consequences, possibly a failing grade and definitely a referral to the Center for Student Conduct.
Please note that online communication mediums outside of Piazza should not be used to discuss assignment content. In general, use Piazza to discuss content. The only limited exceptions to this are online communication mediums between you and the collaborating individuals explicitly listed on your homework assignment. Looking at online solutions from previous semesters or other students is forbidden, as is sharing of your solutions with others. Furthermore, students all have an affirmative duty to report possible cases of cheating or unauthorized communication to the course staff, immediately. Acknowledgement of and failure to report cheating implicates the bystander since this is academic misconduct. Cheating hurts us all and engineering ethics requires us to point out wrongdoing when we are aware of it.
Submit cheating incident reports via this form.
You are encouraged to work on homework problems in study groups of two to four people (collaboration at HW party is an exception to this limitation); however, you must always write up the solutions on your own. You are not permitted to look at the final written solution even for members of your own study group. Similarly, you may use books or online resources (not solutions from previous terms, etc.) to help solve homework problems, but you must always credit all such sources in your writeup and you must never copy material verbatim. We believe that most students can distinguish between helping other students and cheating. Explaining the meaning of a question, discussing a way of approaching a solution, or collaboratively exploring how to solve a problem within your group is an interaction that we strongly encourage. But you should write your homework solution strictly by yourself so that your hands and eyes can help you internalize this material. You must explicitly acknowledge everyone whom you have worked with or who has given you any significant ideas about the homework. Not only is this good scholarly conduct, it also protects you from accusations of being a jerk or free-rider regarding your colleagues' ideas.
Warning: Your attention is drawn to the Department's Policy on Academic Dishonesty. In particular, you should be aware that copying or sharing solutions, in whole or in part, from other students in the class or any other source without acknowledgment constitutes cheating. Any student found to be cheating risks automatically failing the class and being referred to the Office of Student Conduct.
However, we are very fair. No student will be accused of cheating without a human being looking over their case. And nobody will be sent to Student Conduct without at least the head TA and professor concurring that this is warranted and makes sense. Algorithms help us focus our attention, but decisions are made by compassionate human beings.
- Homework: 30%
- Midterm: 30%
- Final: 40%
- Homework: 30%
- Midterm: 25%
- Project: 10%
- Final: 35%
We will encourage more student participation on Piazza rather than answering right away, that is, we will wait until other students step up and answer questions.
Of course, we will still provide clarifications on logistics, typos, subtle points, etc.
We want to make sure that you are helping each other out, and having instructors give away the answers isn't the most beneficial for your education either.
In order to make Piazza a better resource for everyone, we've outlined some guidelines for you to follow when posting your questions. Questions which follow these guidelines will have a higher chance of being answered!
1. Ask HW questions only in the designated HW posts.
We've created individual posts for each problem from homework. Please ask questions, discuss problems, or help out in those posts only. Before asking a question, read through (or search) the whole thread to see if your question has been answered.
2. Don't post answers in Piazza.
Please don't give away the answer on Piazza. You can explain things in a way that still lets other students figure out the essence of the problem on their own, but don't spoil the problem. For example, don't point to a useful YouTube link that works out essentially what the problem is asking about.
That is not cool.
Post such spoilers after the HW is due. That is totally fine. If you are not sure, post privately to instructors and then we'll let you know.
3. Try to make posts public.
While not violating Rule 2, try to make your questions public, because others might have the same question and we don't need to answer them multiple times.
4. Piazza is not Office Hours. 5 minute-test.
If you think your questions may take more than 5 minutes to answer, please come to office hours or homework parties instead.
5. Neither Piazza nor TAs are for pre-grading.
Please do not post questions of the form:
- "Is this the correct solution to HW X problem Y?"
- "Would this receive full credit on HW X problem Y?"
- "Is this the right level of detail for hw X problem Y?"
Please do not use Piazza as a medium to ask instructors to check your homework in advance. We simply cannot check every student's homework through Piazza.
Feel free to ask questions of clarification, or ask questions about the course content to achieve a deeper understanding, but at a certain point, you must apply your knowledge, give it your best shot, and submit your answers with confidence.
6. Post a screen shot of any resource referenced.
Your question should be self-contained. The TAs (and other responders) should not have to scan through PDFs to even figure out what the question is. Ask yourself: am I referring to some lecture /HW solution/discussion solution/past exam?
If the answer is yes, post a screen shot of the relevant part. This can include your handwritten notes from the relevant lecture.
7. Post all your work.
Don't post one line saying:
At step n, I get XYZ, and I'm now confused.
This forces the TAs to guess:
What happened in steps 1, 2, ..., n - 1?
Most likely, the TAs will guess wrong, and we run into a mess of followup questions trying to figure out what steps 1, 2, ..., n - 1 were.
Starting out, we have: ....
Then, I do ..., and I get ...
Next, I do ..., and I get ...
Next, I do ..., and I get ...
Now, I get $&%&#(, and this makes no sense.
Then, the TA can respond:
The mistake is at step 3, you're not allowed to apply ABC to XYZ because ...