You will usually be required to turn in output (results from running your code) along with the commands or code you have written in MATLAB or Maple. 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.
Collect any printout from public printers as soon as possible and document when and where any printouts were unable to be found.
Submitting someone else's work as your own is academic misconduct. Do your work yourself using only the code and instruction we provide. Do not search the internet or view your friends work from current or previous semesters. Submitting work that was written (in full or partially) by someone other than yourself (or us) is Academic Misconduct. Academic Misconduct includes (but is not limited to):
- viewing, discussing, copying, rewriting, etc. previous semester's solutions
- viewing, discussing, copying, rewriting, etc. other students' printouts
DO NOT "CHECK" YOUR ANSWERS WITH YOUR FRIENDS OR CLASSMATES BEFORE SUBMITTING YOUR WORK. THIS IS ACADEMIC MISCONDUCT.
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 academic 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 the Course Coordinator
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, elegant and user-friendly. Students get the most out of their home work when they start on the homeworks early and have conversations about the homeworks with their instructors and teaching assistants before completing their work. This is not unlike the communication required on the job between an employee and their supervisor or a business and their customer. We do not intend to tell students every single detail that may be needed to complete a homework for full credit. It is necessary for students to draw upon their common sense and previous knowledge to complete most homeworks in the course. Gaining a deep understanding of the homeworks and solution techniques will be required to get full credit on the homework sets.
To download the file (or open it in a new window), use the right mouse button to click on the link. Note: Occasionally, we are made aware of typos and other issues that require us to update the homework document. Be sure to check for updates during your work on homework problems to make sure that you have the latest information regarding each homework.
Make sure you have read and understand the course policies regarding homework problems.
Information about grading is below.
| Week | File(s) | Released | Due Date/Time/Form | Solution Files | Graded By |
|---|---|---|---|---|---|
| 1 | Homework 1 | 1/23/12 | Script (homework1.m) and published (homework1.html) are due in Homework1 dropbox by 9:00am on Thursday 2/2/12 |
homework1.m html/homework1.html |
301 & 302: Po-Chun Chang |
| 2 | Homework 2 | 2/3/12 | Script (homework2.m), function definition files and published files (html/homework2.html and html/*.png) are due in Homework2 dropbox by 9:00am on Thursday 2/17/12 |
homework2.m rollFive.m timber.m heatPlate.m html/homework2.html |
301 & 302: Gautam Prakriya |
| 3 | Homework 3 | 2/16/12 | Script (homework3.m), function definition files and published files (html/homework3.html and html/*.png) are due in Homework3 dropbox by 9:00am on Thursday 2/23/12 |
homework3.m html/homework3.html |
301 & 302: Po-Chun Chang |
| 4 | Homework 4 | 2/28/12 | Script (homework4.m), function definition files and published files (html/homework4.html and html/*.png) are due in Homework4 dropbox by 9:00am on Thursday 3/15/12 |
moveBug3D.m homework4.m html/homework4.html homework4extra1.m html/homework4extra1.html homework4extra2.m html/homework4extra2.html |
301 & 302: Gautam Prakriya |
| 5 | Homework 5 | 3/16/12 | Script (homework5.m), function definition files and published files (html/homework4.html and html/*.png) are due in Homework5 dropbox by 9:00am on Thursday 3/29/12 |
homework5soln.m html/homework5soln.html |
301 & 302: Po-Chun Chang |
| 6 | Homework 6 | 3/30/12 | Maple Worksheet (homework6.mw), and pdf files (homework6.pdf) are due in Homework6 dropbox by 9:00am on Thursday 4/26/12 |
homework6.mw homework6.pdf |
301 & 302: Gautam Prakriya |
| 7 | Homework 7 | 4/27/12 | Maple Worksheet (homework7.mw), and pdf files (homework7.pdf) are due in Homework7 dropbox by 9:00am on Thursday 5/10/12 |
homework7.mw homework7.pdf |
301 & 302: Po-Chun Chang |
It is our desire to help you become better and more sophisticated producers of problem solutions. In that light, we will not be specifying every grading point that we will look for in your submitted solutions. Customers and bosses will not do this and will still expect excellent work to be produced. In general, we will look for completeness, correctness, technique, explanation (labels and comments) for each part of your solution and any parts of the question that were not solved.
Excellent solutions are correct and complete, well organized, and easy to read and follow. It is easy to identify the problem being solved and to understand all steps that were taken to solve the problem. One of the goals of the course is to teach you how to use computer programming tools, concepts, and algorithms to solve problems. Be sure to understand the algorithm and technique and show your work in the program language and form you are taught.
Imagine yourself as the consumer of your information and answer these questions in your work: What would you need or want to know?; Who wrote this program or solution?; When did they write it?; What is the problem is being solved? (Tip: Be sure to restate the problem at the start of each problem and label each step in your solution.); Is the solution information correct and complete?; Are there instructions that indicate for which input the solution applies if not all inputs would work?; Are the steps to the final solution easy and logical for others to read and follow, by being clearly outlined and labeled?; Is your solution efficient for solving the given homework? If not, describe where it could be more efficient or why it is not.; Are there appropriate messages to indicate any discrepancies or errors your solution produced or would in certain cases?; Could someone else use your solution and or make small modifications to solve a similar but different problem?
Questions about the grading of a homework problem should first be asked of the TA responsible for grading that particular problem for your paper. Please see them during their individual lab, their office hours, or make an appointment. If there are any unresolved discrepancies, the student or TA may contact the course coordinator to resolve the issue.