CS4300 Computer Graphics Fall 2011: Submitting Assignments

Programming assignments are due by 9pm on the day indicated on the assignment. The course schedule also lists due dates. Please let me know of any discrepancy between the due date specified on the assignment and that listed in the schedule. Printed documents, like the plans for your 2D project must be turned in at the start of class on the due date.

The mode of submission for each assignment will be specified as part of the assignment. For example, you may be required to email a zipfile or tarball of your submission to the course staff.

You must always submit something by the due date and time. If what you have at that time is not yet complete, submit it anyway, and state clearly what you have and have not completed.

If you are unable to complete an assignment by the due date for a reason beyond your control (e.g. illness), you may request an extension. If such an extension is requested and granted prior to the original due date, the extended date will be treated as the due date for you.

If you submit an incomplete assignment, you may submit a revision or update at a later date, but no later than 1) the due date of the next assignment or 2) the last day of class, whichever comes first. Such late submissions may be eligible for partial credit at the discretion of the course staff on a case-by-case basis.

Turning In Assignments

Unless otherwise specified, follow these instructions to turn in each homework assignment.

1. Make a directory D named “e_name_HWn” where
   • e_name is your @neu.edu email address with “.” converted to “_”, and
   • n is the number of this homework assignment.
   For example, if the instructor were to hand in HW1, D would be “h_fell_HW1”. Put all files and subdirectories related to your assignment below D.
2. Make a plain-text (ASCII) file D/README.txt, with the following contents:
   • a description of how to compile your code, if necessary
   • a description of how to execute your code, if necessary
   • a list of any known bugs or incomplete aspects of your assignment
   • a list of any extra-credit you have added
3. Using either a pkzip-compatible (e.g. zip on *nix) archiver or tar | gz, make a single-file archive of the directory tree under D, including D itself. The file should be named either D.zip or D.tar.gz, accordingly.
4. In a separate temporary directory, test uncompressing your submission. Verify that the top-level directory D is contained in your archive. If the assignment included writing code, ensure that your instructions for both compilation and execution work on one of the standard computing environments within CCIS (see the platforms page for how we define this).
5. Email your archive to . Be aware that large attachments (greater than 25MB) will not go through.

Academic Honesty

The Northeastern University academic integrity policy applies to your work in this course.

Unless otherwise specified, you must work alone on each assignment. You may discuss the assignment with others, but you must acknowledge in writing any such substantive discussion (other than with the course staff).

With the exception of the supported programming environments and APIs specifically listed on the platforms page, you must explicitly specify any “third-party” code that you use in a README file included with your homework submission. Third-party code includes, but is not limited to, source and/or binary code that you may have found on the internet, in a book or other printed reference (other than the course text), or from any other person or location. Digital content not created by yourself, including image (e.g. JPEG) and 3D model files (e.g. VRML), is also considered third-party code. These definitions also apply to third-party code which you have modified.

Any third-party code you submit which is not documented as such will be considered plagiarism. It is not hard for us to find out whether the code you have submitted was taken from the internet.

Third-party code (and any modifications you have made to it) will not be considered for grading. Thus, if the assignment is, for example, to write code to rasterize a line segment, and you submit only code you found on the internet to do such, you will receive a grade of 0 for the assignment. Worse, if you do not document that you have used this third-party code, you will be cited for violation of the academic integrity policy.

What is the use of third-party code? You will never be required as part of an assignment to implement any feature which is not reasonable to write on your own. But for implementing extra credit features (though the extra credit will be based only on the code you wrote, not the third-party code), or for your own use, you may find it helpful to have the option. Loading video files and VRML models are two reasonable cases where third-party code may be useful.

If you are unsure whether your use of third-party code follows the above rules, contact the course staff for clarification before handing in your assignment.