Below the HW list, there are details about how the HW will be graded. Make sure to review this!
...
The class reading assignments are part of each week's homework. These should be completed before class each Monday to prepare for the week's topics.
If you didn't complete an exercise in class, you should complete it on your own to prepare for the week's homework problems.
...
All homework assignments are due on -line GitHub by 11am on Thursdaynoon on 12:30 pm. Solutions will be posted to Canvas. |
|---|
| Due Date | assignment Assignment |
| Jan 25June 18 | HW01 |
| Feb 1June 21 (Fri) | HW02 |
| Feb 8June 25 | HW03 |
| Feb 15June 27 | HW04 |
| Feb 22July 2 (due by 6am) | HW05 |
| Feb 29July 10 (start early!) | HW06 |
| Mar 7 | Spring Break |
| Mar 14 | None |
| Mar 21 | HW07 |
| Mar 28 | HW08 |
| Apr 4 | HW09 |
| Apr 11 | HW10 |
| Apr 18 | HW11 |
| Apr 25 | HW12 |
| July 10 | HW07 |
| July 13 (by 3:15 2-May (Noon Thur) | Final Project |
General comments on Homework
...
Follow the weekly instructions carefully.
Start your homework early. At least read over the problems on Wednesday when they are posted.
Don't start coding a problem until you have a good understanding of how to approach it. Otherwise, you may write a different program than the expected one and this may add a lot of extra work.
Questions? See your TA/Instructor, and use the Piazza discussion group.
You may (and are encouraged to) discuss the programs (strategies, coding problems, etc) with your classmates, but you may not share/copy code solutions.
Your submitted source will be used for grading - comments will be returned to you electronically via GitHub.
You will pledge the electronic copy, and this pledge signifies that you are the sole author of the assigned source code. See the example below for the required comment heading to be included in your program files.
...
Compiling without errors, runs OK, and reasonable results: ~25%
If the result is exactly as expected ( no calculation errors, etc. ), the structure/output of the code is clear, and good programming habits are used, then we award the other ~75%. Conversely, poor structure/clarity, output preparation, programming habits, will count against this 75%. The output from your programs should be easily readable and descriptive. Make sure your design satisfies any explicit requirements on program structure. Use descriptive variable names in your code. Include comments in key areas of your code as necessary to explain your work. Refer to the style guide for some tips to make your code more readable.
Avoid compiler warnings: approximately -10% per question, per type of warning message (unused variables, type mismatch, etc…), with a max of three warning penalties. On a 10-point homework question, that means every warning is -1 point, up to -3 total.
...