ASSIGNMENTS

Submitting Assignments:

Homework Assignments. You need not submit homework assignments to Moodle - I will have access to your submissions on Gradescope. As of now, there is one assignment that will not be autograded (HW12: Logical Inference). If I don't get it on the Gradescope platform by the end of the semester, you must complete and submit as a document to Moodle, but I will try to automate it.

Programming Assignments. All project and program assignments need to be submitted via Moodle. In the event of a Moodle failure, email your submission to me before the deadline. You should upload all the source files required by the assignment. You should also include any other files required to run your solution, but not the unmodified files that were provided to you. The top of every source file submitted should include your name and a description of what the file does or what you added/modified.

Project Assignments. The paper should also be submitted via Moodle. I prefer that you submit it in MS Word format.

Deadline and late policy:

All assignments are due on the stated date by 11:59 that night. Assignments arriving even one minute late are considered late. Since we are using the Berkeley course platform, all assignments are autograded, so I anticipate little to no delay between the time you turn in your assignment and the time it is graded. Therefore, unless there is a very valid reason for turning in something late, late submissions will not be accepted.

Grading:

As I said, I will be using the Berkeley autograder. You can use this too, so you know how well you are doing. On the homework assignments, you should know right away if you got a question correct or not. If you get an incorrect answer, try to understand why, because it is likely that similar questions will be on exams.

You can also run the provided autograder on your code. You should know right away if you are getting the correct output or not. On programs, I reserve the right to deduct points for poor program style or commenting - or add points for particularly good solutions. Partial credit is always possible so if you run out of time, submit what you have. If you want to do well, start well in advance of the deadline. The programs will take a good chunk of time, a lot of it just trying to understand what you are expected to do and what has been provided for you.

Papers will be graded using the department's standardized grading criteria: Standardized written assessment

Collaboration policy:

Programming is a creative process and no two programmers will solve the same problem in the same way. You are encouraged to discuss how to design a solution to a given problem with your classmates. But when it comes time to convert your design into code, you must write the code yourself. Be sure not to leave copies of your code where others might be able to access it (such as in the recycling bin of a lab computer). You may adapt code from the CSCI 446 course materials and the website, provided you cite what code you used in your program's comments.

Under no circumstances should you copy another person's code. Copying code from another student can result in an F in the course. Students often mistakenly believe simple transformations can disguise a copied program. In actuality, copied programs often reveal themselves quite easily during grading. We can also use sophisticated software such as MOSS to detect plagiarized code.

Page last updated: November 19, 2021