CS 791 Project

The goal of the project is to conduct a significant exploration of a single topic in the field of non-photorealistic computer graphics, geometry, and ornament. Most likely, this exploration will take the form of an implementation of an algorithm or technique. It may be possible to produce a paper or carry out an experiment as a project in this course, though these will be held to a higher standard. The project is not required to contain any new research, though new research is certainly encouraged.

You are welcome to work in pairs for the final project. Pairs will be expected to do more work than students working alone, but definitely not twice as much work; maybe more like 1.25-1.5 times as much. Thus there is some benefit to teaming up.

The proposal (19 March)

The first element of the project is the proposal. The proposal should outline the scope and goals of the project, and give a clear idea of what will be done.

There is no fixed page limit for the proposal; it should be exactly as long as is necessary. If you want to shoot for a target, two or three pages seems like a reasonable size. Be sure to include images and a bibliography if necessary. Body fonts should be between ten and twelve points in size, and text should be set single-spaced in one column. Use one inch margins all around.

The content of the proposal is not entirely fixed. You should use whatever organization you feel will best motivate the subject and communicate your goals. But here are some main points that you should be sure to cover (adapted from Tim Brecht's CS856 project guidelines):

The problem statement or idea
What problem is being studied or addressed?
Why is this problem interesting? Why is it deep? Who cares about this problem, and who will benefit from a solution?
What is it you are going to do? How will you or anyone else be able to tell if you've attained your goals? These don't have to follow the format of the objective list in CS488/688. But you should try to give a concrete set of properties that your final product will have.
Approach or techniques used
How are you going to do this? What algorithms or techniques will apply? What hardware and software will you use? How do you plan to evaluate that your project is performing as expected?
You won't be expected to complete all of these milestones; you should think about writing a proposal for which you can meet all the short term ones and some of the medium term ones. The purpose of this section is more to show that you've thought through the implications of this work and have ideas about what directions your project could take in the future.

You can start working on your project as soon as you've submitted your proposal, or even before. Only in the most extreme cases will it be necessary to change to a completely different topic. It's much more likely that I'll simply offer a few minor adjustments or pointers to relevant work, and that the work you've done until that point will still be applicable.

In-class presentation (30 March – 1 April)

There is no preset format for your presentation. The general goal is to introduce and motivate the problem area, describe the scope and aims of your project, show current results, and discuss future work. Here are some additional collected notes:

The write-up (21 April)

Your final project submission should be in the form of a paper write-up. Use the same formatting guidelines that were given for the proposal, or analogous HTML formatting. Again, there is no predetermined length for your paper; it should be exactly long enough to contain everything you need to say. As a guideline, I'll recommend a 5–10 page paper, including images. Of course, part of your mark will come from the quality of your write-up, so try to find a suitable level of detail.

You should organize your paper in whatever format best communicates its ideas. Here are some suggestions for main points to discuss:

Craig S. Kaplan Last updated: