Assignments that do not meet the program specifications EXACTLY will not be graded!
Any assignments that are returned to students because they do not meet the assignment specifications will be penalized with late points.

Assignment results will be assessed visually. I am not looking for any specific file output.

1 point per day (max of 5 points, out of 10) will be deducted from late assignments.
The deadline for turning in all assignments is December 7.
You will be given a grade of 0 if an assignment is not turned in by this date.

The programming assignments should be submitted on the class Bb Learn page before 11:59 PM on the due date to be considered on-time.

All assignments will be run in the Unix Command Line Interface (CLI) on tux and will generate geometry files in the ASCII Open Inventor format.
Examples of Open Inventor files can be found here.
Inventor (*.iv) files can be viewed with an open-source CAD system called FreeCAD. Go here to download a version of this sofware for your computer.
You must ensure that your Inventor files can be displayed in FreeCAD.

All assignments should include source code files, a README file, and a makefile (if you're writing in a compiled language) or a script (if you're writing in an interpreted language).

• Assignment 1 (Arbitrary-degree Bezier curves) - Due October 6
  
• Assignment 2 (Catmull-Rom splines with tension) - Due October 13
  
• Assignment 3 (Bicubic Bezier patches) - Due October 23
  
• Assignment 4 (Surface of revolution) - Due October 31
  
• Assignment 5 (2D polygon union) - Due November 10
  
• Assignment 6 (Superellipsoids) - Due November 17
  
• Assignment 7 (Hierarchical models) - Due December 1
  
• Extra Credit Assignment (CSG evaluation) - Due December 5
  

You must be the sole original author of all assignments and examination solutions in their entirety, unless the instructor explicitly instructs you otherwise in written directions on an assignment or exam. Collaborative work is a violation of academic honesty in this course. You are not to examine or use code belonging to someone else, nor may you let anyone else examine or copy your code.

Students found in violation of the Academic Honesty policy will receive an 'F' in the class.
In the case of plagiarism, all parties involved will be equally penalized.

The description of the department's Academic Integrity Policy can be found here. If a student violates this policy, an Alleged Academic Misconduct Report will be filed with the university.

It is your responsibility to avoid violating the university's policy. If you are unclear as to what the policy means in a particular situation, ask the instructor for clarification before you hand anything in.

See the examples below for clarification of this policy.

Examples

• Using code provided in lecture: include comments that cite the source.
• Using code provided in the class textbook: include comments that cite the source.
• Code developed jointly with instructor or teaching assistants assigned to this course.
• Discussing algorithms or possible approaches to writing your program, WITHOUT discussing particulars of the code.
• Discussing how to resolve errors, WITHOUT discussing particulars of the code.

• You borrow a printed or electronic copy of a friend's assignment, and use it for "inspiration".
• You give a printed or electronic copy of your assignment to somebody else.
• You "find" a copy of somebody's program in the trash, on a lab machine, on their hard drive, on the web, etc., and use it for "inspiration".
• You pay a "tutor" who writes the assignment for you.
• You download code from the Web, and turn in some or all of it as your own assignment.
• You use generative tools to create portions of your assignments.
• You and a friend together write one assignment, then create separate modifications to be handed in.
• You and a friend write certain portions of the assignment individually, but collaborate on other portions of the assignment.
• You work in a group that works out the detailed structure of the assignment and you turn it into a specific program.

Your source code for all programming assignments will be run through a plagiarism detection system. This program uses compiler techniques, which are invariant of syntax and style. If you are sharing/borrowing code with other classmates (from this or previous years), you will get caught.

Each graduate student will read a technical conference paper related to geometric modeling or geometry processing and submit a Powerpoint presentation that describes/summarizes the paper.
Suggested conferences are the SIGGRAPH Conference, SIGGRAPH Asia Conference, Eurographics Conference, Shape Modeling International Conference, Solid and Physical Modeling Conference and the Symposium on Geometry Processing. The paper must be from the main SIGGRAPH or SIGGRAPH Asia Conference, not just from any ACM SIGGRAPH-sponsored conference, symposium or workshop.
The presentation should include:

• at least 10 slides
• images
• the citation information for the paper, i.e. where and when was the paper published, and by whom. Included on the title slide.

If you are not on a drexel.edu computer you will have to access the papers through the Drexel Library, or by connecting to the Drexel network via VPN.
Please no "Games Papers".

Here is a good example of what I expect.

Email me the full citation of the paper that you will review by October 20th.
The deadline for submitting the Powerpoint presentation is November 24th.
The same policy as programming assignments applies for late presentations.