|
Matt Bishop Office: 2209 Watershed Sciences Phone: +1 (530) 752-8060 Email: mabishop@ucdavis.edu |
Version of March 28, 2022 at 1:34PM
This handout describes some general thoughts and techniques for doing homework, as well as what is required, how to submit it, how late homework is handled, and other administrative matters.
All homework is due at 11:55PM on the due date, unless noted otherwise on the assignment. These will be graded and comments returned to you as quickly as possible; we’ll try for three class periods, but can’t guarantee it. For written homework, you must turn in an ASCII, a PostScript, or a PDF version of your answers (you can use any text processor you like to generate these). Please do not submit Microsoft Word files; since the readers may grade these on UNIX-based and Linux systems, they will not be able to read those files. If you submit PostScript, please be sure the file will print on our department printers (use ghostscript(1) or gs(1) to check this; if it displays the file properly, the file should print correctly). If your file is a PostScript file, please choose a name that ends in “.ps”. If it is an ASCII file, please choose a name that ends in “.txt”. If your file is a PDF file, please choose a name that ends in “.pdf”.
Please turn in your work electronically through Smartsite. Do not use the handin program! If you need to turn in something on paper (for example, a diagram that you can’t draw using your text processing program), please hand it to the professor or TA before the assignment is due, and put a note in what you submit electronically that you have done this. That way, the grader will know to look for something written, rather than mark you off for that problem.
When you are asked to analyze something, or explain something, please be complete, and show your work (including any commands you give, and their output, to show how you did the problem). Otherwise, even if you get the right answer, you will get ZERO (that’s 0, zip, nada, rien, nothing) points. Think your answer through and do a rough draft. Students (and professionals, actually) often overlook this, but it is vital. Write clearly and cogently. If the question asks for an opinion, state your opinion clearly, justify it, and don’t ramble. Answers that start, “My opinion is yes …” and conclude with “… on the other hand it could equally well be no” won’t get much credit.
We do not mind being asked for help; indeed, we welcome it because it helps us know what you are finding difficult or confusing, and sometimes a few words about the problem in class will clarify the assignment immensely for everyone. Your questions may also point out ambiguities that we didn’t think of, so the more questions you ask, the better for everyone!
We do mind being asked for help before you have tried to think the problem through. The classic objectionable question (this really happened) occurred on a programming assignment in which the class was given a buggy program. The assignment said the program did not work, and the homework was to debug it and make it work. Within 10 minutes of the end of the class during which the assignment was given out, the instructor got this request for help: “The program doesn’t run. What do I do now?”
So, before asking for help (except for questions about what the problem is asking), please be sure that you have:
When you come to us, or send us a note, asking for help, please describe whatever you have done to solve the problem, because the first question we will ask you is “What have you tried to solve the problem?” This isn’t because we think you’re wasting our time; it’s because understanding how you have tried to solve the problem will help us figure out exactly what your difficulty is and what we can do to help you. Remember, we will do everything we can to avoid solving the problem for you; when we give you help, our goal is to help you solve the problem yourself.
We must emphasize the importance of taking time to think through, outline, and draft your answer, thoroughly. More points are lost through unclear organization, or superficial answers, than anything else. So do think both your answer and your expression of the answer through, and—as always—try to find the simplest way to solve the problem (within the limits given in the assignment, of course)!
Do not leave assignments for the last minute. The assignments are non-trivial and will require significant time before you write your answers for submission. When we decide on the due dates, we assume you will spend significant amounts of time solving (at least some) of the problems. If you choose not to do this, you will have difficulty finishing the assignments on time.
Your grades will be posted to Canvas when the homework assignment is graded. We will also post comments on why you gained, or lost, points.
Extra credit in this course will be tallied separately from regular scores. If you end up on a borderline between two grades at the end of the course, extra credit will count in your favor. However, failure to do extra credit will never be counted against you, because grades are assigned on the basis of regular scores. You should do extra credit if you find it interesting and think that it might teach you something. Remember, though, it is not wise to skimp on the regular assignment in order to do extra credit!
Unless the assignment says otherwise, we won’t accept them. Canvas will decline to accept submissions after that time, so you won’t even be able to submit late homeworks.
Requests for exceptions will be handled on a case-by-case basis. Please feel free to ask.
If you feel that there is an error in grading, please come see me or the TA and explain what you believe the grading error was. We’ll look over it (and possibly talk with you about it). However, don’t dally; any such request must be made within one week of when the grades were made available. After that, we won’t change your grade.
|
ECS 150, Operating Systems Version of March 28, 2022 at 1:34PM
|
You can also obtain a PDF version of this.
|