| Logistics | |||||||||
| Grading Policy | |||||||||
| Syllabus Lecture Notes |
|||||||||
| Forum | |||||||||
| PAs: | |||||||||
|
|||||||||
| HWs: | |||||||||
|
- Course Grade Composition:
- 1 Final Exam: 30%
- 1 Midterm Exam: 20%
- 3 Homeworks: 15%
- 3 Programming Assignments: 30%
- Class Participation: 5%
Both the midterm and final exams are open-book, open-notes exams. The final exam is cumulative.
If your individual effort is lacking, a failing grade is a distinct possibility. Roughly, you'll get an E if you failed the exams and do not show sufficient efforts. Insanely great work gets an A+, excellent work an A, good work a B, and acceptable work a C.
- Policy on Collaboration
All works must be completed individually.
You are encouraged to discuss ideas and techniques broadly with other class members, but not the specifics of assigned problems. Sharing of code or intermediate designs is expressly prohibited. If you receive substantial help from others, you must acknowledge them in your work. If you use any published materials (books, papers, or materials found on the Web) in your solution, you must give full citation that help facilitate the locating of the original materials (for example, the URL of the Web site).
You must not discuss exam questions with others nor lookup solutions to homework and exam questions online. To pass off the implementation of an algorithm as that of another is also considered cheating. All write-ups, reviews, documentation, and other written material must be original and may not be derived from other sources.
Acts of cheating and plagiarizing will be reported to the Engineering Honor Council. Cheating is when you copy, with or without modification, someone else's work that is not meant to be publicly accessible. Plagiarizing is when you copy, with or without modification, someone else's work that is publicly available without acknowledging the original author. To incorporate publicly available code in your solution is considered cheating in this course. Please review CAEN's policy document on rights and responsibilities for guidelines concerning use of technology resources at U-M, as well as the Engineering Honor Code. As members of the university, you are required to adhere to these policies.
- Regrade and Late Days
You have five working days from when a piece of graded work is returned to ask for a regrade. Due to grade reporting schedule, request for regrade of the final assignments and exam must be submitted the same day it is returned. To ask for regrade, you must submit a written request explaining the technical reasons that would make a regrade necessary. A regrade means regrading your whole work and may result in overall lower grade.
You have four free late days, including weekends, to use on any of your homeworks or programming assignments. It is your responsibility to keep track of your own remaining free late days. Once the free late days are used up, late assignments will be assessed a penalty of 4% per 24 hours or fraction thereof. Since we provide the free late days, we will not grant extensions.
Start your assignments early, and plan to have them finished a few days ahead of the due date. Many unexpected problems arise during programming. In addition, the computer labs can become crowded and computers crash and networks fail. Extensions will not be granted even if these things happen. Plan for them to happen.