There are no make-up opportunities for missed quizzes. There are many quiz events throughout the semester. Try not to miss any quizzes but if you must miss a quiz, focus and prepare for the next quiz or exam. It is very unlikely that a missed quiz will be the difference from one letter grade to the next in the final grade.
As you take a quiz, keep in mind the following:
Individual lab quizzes are proctored (password protected) and timed quizzes. You must complete your quiz submission before the 30 minutes time limit is up to get credit for the quiz. Individual lab quizzes focus on the material from the current week. Questions focus on concepts covered in the current week's team lab. Individual lab quizzes must be taken in the individual lab room B540 Engr during scheduled individual lab times under the supervision of a CS 310 TA or Instructor. The 30 minutes starts when you hit the "Start Quiz" button, so open Maple or Matlab and any notes or other work you may wish to have available before starting the quiz. Save each answer as you complete each problem. Do not close the quiz window until you have completed the quiz, as you may not be able to restart the quiz. Collaboration is not allowed on individual lab quizzes. Ask any questions before starting the quiz.
If you know that you will be unable to attend your individual lab, you may attend any of the other scheduled individual labs. Check the individual lab schedule via Learn@UW, Most semesters, the actual schedule differs from that of the timetable. You do not need any special permission to attend a different individual lab; however, students who are officially registered for an individual lab have first priority for the computers during that lab time.
This is common sense for all but 1% of our students, but it is stated here for the remaining 1%. Thank you for your compliance. Answering cell phones or text messaging or other types of electronic communication during Individual Lab Quizzes is strictly prohibited. While you are taking an Individual Lab quiz, you must turn off your cell phone or other communication devices and complete the quiz individually. Using such a device during a quiz may be considered Academic Misconduct and may lead to a further investigation and penalties.
If you are working in the Individual Lab and not taking a quiz, you may leave the room to answer cell phone calls. At no time, should you talk on the phone from a workstation in the individual lab. It is imperative that B540 remain quiet while other students complete their work. Also, if other students are waiting for computer terminals, then you must log out so that another student can use the computer while you talk on your phone. You do not have priority to return to that computer when your call is done (unless you're enrolled in that session). Please be responsible and respectful of other students need to use the computers.
One of the objectives of the team labs is to give you experience working in groups to solve problems. For this reason, team lab attendance is part of your overall course grade. Team lab attendance is taken during the team lab. Students who arrive more than 5 minutes late (or leave more than 5 minutes early) will have to attend a different Team Lab to receive attendance credit for that Team Lab. Each week, when you arrive at your team lab, one teammate will login to Learn@UW and open the current week's Team Lab and either Maple or Matlab as required for that team lab topic.
The only way to get attendance credit for team lab is to attend team lab and work with a team to solve the given problems. Any attempts to misrepresent your attendance at team lab will result in a zero for the entire team lab attendance portion of your grade and potentially other penalties if University Academic Misconduct rules are violated (see the Academic Misconduct Guide for Students).
If you know that you will be unable to attend your team lab during a particular week, you may (with prior approval and if space permits) attend one of the other team labs that week to receive attendance credit for that week's lab. Contact the instructor of the team lab you wish to attend to find out if space is available and to receive further information.
This is common sense for all but 1% of our students, but it is stated here for the remaining 1%. Thank you for your compliance. Answering cell phones or text messaging or other types of electronic communication during Team Labs is strictly prohibited.
In Team Labs, it is disruptive to your learning and to the learning of your team mates. Please turn off all electronic devices prior to the start of each Team Lab and leave them off for the duration of the lab. Answering a phone or reading or sending a text message or other communication during lab will result in a loss of some credit for the lab.
This is common sense for all but 1% of our students, but it is stated here for phones or text messaging or other types of electronic communication during Exams is strictly prohibited.
In Exams, it may be considered Academic Misconduct. Please turn off all electronic devices prior to the start of Exam and leave them off for the duration of the exam event. Answering a phone or reading or sending a text message or other communication during an exam may result in an Academic Misconduct investigation and further penalties.
As engineers and other professionals it is vitally important that you be able to express and present your solutions in ways that are accurate, complete, efficient and elegant and user-friendly.
The best way to get help on your homework is to compose (write down) your question first and then contact an Instructor or TA during individual lab times or scheduled office hours. Office hours are scheduled on Monday Tuesday, Wednesday, and Thursday evenings. These are the times that each TA has set aside to assist students individually. If you're getting help in an office away from B540 Engineering, bring hardcopies (printouts) of your work for the instructor or TA to review. This is necessary as you will not have an account on the individual instructor's computer. Also, it allows us to help more students during the allotted time period since we do not need to spend time waiting for programs to launch, files to open and navigating to a particular line.
Note: Since homework assignments are due at the beginning of individual labs (on Thursdays), the most busy days of any homework cycle is the Tuesday and Wednesday immediately before the due date. Please be advised that students who are almost finished with their homework and have single specific questions will have priority over students who are just starting or don't know where to start. Start your homework problem sets early to avoid the rush the nights before the assignments are due. Even if you don't expect to have questions, complete your homework early to have ample time to work on the presentation of your solution. This will also allow you to avoid the long printer queues and other equipment failures that are often the result of high demand of the resources in the last few hours. In other words, START EARLY!
Many students find it convenient to ask questions regarding their homework via email. Pedagogically, there are a couple of problems with this approach. Rarely will an instructor simply answer a question or debug your code. Why? because our real goal is to teach you how to learn, not just to teach a particular fact. As instructors, we want to help students learn how to find the answers for themselves and learn how to debug their own work. In this course, the answer itself is rarely as important as the process you use to determine or discover it. Email has proven to be very inefficient and ineffective in this process as it requires a great deal of time to compose responses to lengthy questions and often requires many exchanges for us to ask the questions that must be asked for us to lead you to your own solution. A conversation in person is much more effective and efficient as it allows us to learn exactly what your current understanding is and thus guide you from that point. That is why... We request that you refrain from asking homework questions via email. Instead, please start your homework early and ask questions during individual lab or office hours if you get stuck.
However, if you believe that there is an error in the problem or notice something that would be of interest to all students in the course, please do not hesitate to report it via the Errata form or just email the Course Coordinator as soon as possible so that it may be resolved. Also, be sure that you include your name in your email so that we may known to whom we are conversing should we require more information about the issue.
Homework is due at the beginning of the individual lab you are registered for. Late homework is not accepted.
Collaboration (in pairs only) is allowed (see the Collaboration Policy below for complete details). If students collaborate, they submit one copy of their homework solution with the names and team lab numbers of both collaborators. Failure to include names and team lab numbers of the students who completed that solution may result in lost points.
Code (and the output produced by it) must be printed out from Maple or Matlab. Hand-written code may be given almost full credit if it otherwise meets the homework grading criteria and is legible. Check your printouts carefully to make sure that everything is printed as desired (e.g. no lines of code were cut off by the edge of the paper).
You will usually be required to turn in output along with the commands or code you have written in Maple or Matlab. Any output that you turn in must come from your code. Turning in output that was not produced by your code is academic misconduct.
You should turn in the output for your code even if you know it is incorrect or produces an error message. When the homework is graded, it is the commands and results that are graded for correctness. Output that contains incorrect information or error messages help the graders understand your code so that they can assign partial credit and give you useful feedback.
Although work on assignments can be done collaboratively with one other person, you are forewarned that excessive collaboration may cause you to do poorly on exams and thus in the course. This is because most students do well on homework assignments as they have relatively unlimited resources to find the answer elsewhere even if they can't solve the problem themselves. This is not the case on exams; and students score poorly on exams if they have not learned how to solve the problems themselves. The assignments are intended to give you the practice necessary to understand the course material. We will expect that you understand all aspects of each assignment, and we will be testing your knowledge of the assignments on the exams.
You are allowed at most one collaborator on each assignment and you must list your collaborator on the cover sheet for that assignment. Students are not to work with (or "get help from") more than one other student, and this student must be their collaborator.
This policy is not a license to copy and submit someone else's work. Submitting someone else's work as your own is academic misconduct. This includes (but is not limited to):
Such cheating and plagiarism will result in a zero on the assignment and potentially other penalties if University Academic Misconduct rules are violated (see the Academic Misconduct Guide for Students).
Every semester there are students who have to face the consequences of violating the course policies. These consequences have included lowered scores, lowered final grades, failing grades, and letters to the Dean's Office as well as in their permanent files. It is your responsibility to make sure that you understand and follow the course policies for CS 310 as well as University rules regarding academic misconduct (see the Academic Misconduct Guide for Students).
If you have any questions about the course policies, please do not hesitate to contact any of the instructors or TAs for CS 310.