|
|
Not all of the material is in the textbook, WWW, or online lecture notes. If, for some reason, you must miss a lecture, arrange with a fellow student to take notes for you. If that is not possible, then stop by and talk to the teacher.
|
|
|
|
|
|
It is not possible to "memorize" your way through this course. It is an engineering course, and you train to solve problems based on learned skills and fundamental understanding.
|
|
|
|
|
|
The probability that you pass the final exam increases with your active participation in the labs. A large part of the final exam is built on the labs. We do not teach two courses: a separate "lab" course and a separate "theory" course. We teach only one course in which the labs are an integral part.
|
|
|
|
|
|
Labs
|
|
|
====
|
|
|
|
|
|
The information needed to conduct the labs is available on the course homepage. The lab guidelines is the document that describes the general lab procedure. Please read it carefully and thoroughly!
|
|
|
|
|
|
Please note that our schedule is tight and there are dependencies between your and other students' work, it is very important that you adhere to the given dates! If you notice any problems to comply with the schedule, approach us immediately so that we can find a solution together.
|
|
|
|
|
|
We strive to give you feedback for your submission as soon as possible. However, you must not await our feedback as a signal to continue working. Seek for help as soon as problems show up to meet all deadlines. We prioritize lab support over submission feedback.
|
|
|
|
|
|
If your implementation or your review do not fulfill the requirements to pass the lab, you must correct or redo the respective part of the lab. In this case, we expect you to resubmit your lab solution within one week after you receive the feedback for your lab from us. |
|
|
\ No newline at end of file |