Q: What are the prerequisites for the course?

A: Students are expected to have good programming skills. Knowledge of Python/Java is especially important since you will be writing lots of Spark code. In addition to programming basic knowledge of probability/statistics and linear algebra is required as well.

Q: How do I submit my assignment?

A: All students should submit their assignments electronically via GradeScope. Simply sign up on the gradescope website and use the course code V84RPB. Please use your UW NetID if possible. No handwritten work will be accepted. Math formulas must be typeset using LATEX or other word processing software that supports mathematical symbols (e.g., Google Docs, Microsoft Word).

All students will be given two no-questions-asked late periods, but only one late period can be used per homework and cannot be used for project deliverables. A late-period lasts 48 hours from the original deadline (so if an assignment is due on Thursday at 11:59 pm, the late period goes to the Saturday at 11:59pm Pacific Time). Homework that is submitted beyond the late period will not be graded and receive zero credit.

For the non-coding component of the homework, you should upload a PDF rather than submitting as images. We will use Gradescope for the submission of code as well. Please make sure to tag each part correctly on Gradescope so it is easier for us to grade. There will be a small point deduction for each mistagged page and for each question that includes code. Put all the code for a single question into a single file and upload it. Only files in text format (e.g. .txt, .py, .java) will be accepted. There will be no credit for coding questions without submitted code on Gradescope, or for submitting it after the deadline , so please remember to submit your code.

Q: How do I submit a regrade request?

We take great care to ensure that grading is fair and consistent. Since we will always use the same grading procedure, any grades you receive are unlikely to change significantly. However, if you feel that your work deserves a regrade, please submit a request on GradeScope within one week of receiving your grade.

Before requesting a regrade, please prepare a clear and concise argument for your stance by doing the following:

• Re-read relevant sections of papers, the notes, and the text (where applicable).
• Read carefully the comments we provide on your work and consider their meaning.

And then submit your regrade request via GradeScope. We reserve the right to regrade the entirety of any homework for which any regrade is requested.

Q: Who makes the decision for a regrade request?

Every time you submit a regrade request for a problem, an email gets sent to both Prof. Althoff and the TA who graded your problem. Submitting multiple regrade requests on the same problem set will result in multiple emails being sent. All TAs will be able to see your request, but the original grader of the problem will have the final say in determining your grade, because after reading 100 solutions to the same problem, they become the expert in which answers are right and which ones are wrong. (In particularly ambiguous cases, the original grader will usually consult with other TAs before replying to your request, but they will still make the final decision.)

The head TA does not technically have the power to override the original grader. However, they can make strong recommendations to the original grader, if they disagree with their decision.

Q: What actions will be taken after a regrade request?

Regrade requests will only be honored in cases where the TA made a clear error in grading your problem set.

If a TA gives back points to someone who submitted a regrade request, the TA must give back points to all people who had a similar deduction, even people who did not submit a regrade request. If a TA violates this policy, you should email the head TA.

If you are not sure whether your regrade request is justified or not, come to office hours and speak to a TA.

Q: What are some good and bad regrade requests?

Examples of good regrade requests include

• The TA said I left Problem 4 blank, but I have Problem 4 right here, and they just didn't see it.
• The TA said I was missing a step, but I have the step on line 30 of page 2 of my assignment.
• The TA said this solution was wrong, and I realize it is not the same as the one in the solution set, but here is a clear and informal explanation of why my alternate solution is correct. I have also attached a statement addressing any concerns the TA may have raised in a comment.

Examples of bad regrade requests include

• I think this rubric is unfair.
• I deserved to get "minor error (-1 points)" instead of "major error (-4 points)."
• I know I said X, but what I really meant was Y. (We can only grade what's on the page!)
• I gave several distinct answers to the problem, and one of them was correct! (Even if another was wrong).
• If I change one line in my code, I get the correct answer, so please give me more points.
• I gave a correct answer to a different problem from the one on the problem set.
• Any request that asserts your solution is correct without giving new information that helps the TA interpret your solution. If your regrade request just says "My solution is correct, please take another look at it," the answer will probably be "I looked at it the first time, and I disagree with you, so you are getting no points back." Regrade requests result from communication failures (either the TA has failed to properly explain to you why your answer is wrong, or you have failed to clearly communicate your solution and why it is correct). So if there is no new information, the TA is unlikely to change their mind.

Q: How do I register for EdDiscussion?

A: Navigate to https://edstem.org/us/courses/4942/discussion/. Please use your UW email address for registering (YourNetID@uw.edu).