Final Project

Introduction

This fall, we've surveyed a number of topics in computer graphics to give you a broad introduction to the field. Now, we're giving you the reins. Pick your favorite topic, do some reading and research, and make a cool demo!

In your final project, you will implement your choice of rendering, modeling, or image-based techniques discussed in class (and which you have not already implemented in a previous lab or project) and show them off in an interesting way. We will evaluate your project based on technical and creative merits.

Project Groups

If you'd like to search for teammates beyond your usual circles, we encourage you comment on the Finding Final Project Groups pinned thread on Ed. Put up ideas and projects you are interested in, then get in touch with others who share those interests!

You may complete your final project in a group of 1 only under exceptional circumstances, and only with the permission of the course instructor.

Mentor TAs

Each group will be assigned a mentor TA shortly after project proposals are submitted. This TA will be your go-to resource when working on your final project, and you should reach out to them when you have any questions or concerns.

Deliverables

Project Proposal

The form asks you to provide the following information:

• The name of your group,
• The names and CS logins of all your group members,
• An idea of what you expect your final project will look like (feel free to include multiple ideas--we will help you choose which one(s) might be best for you),
• Any specific technical features you intend to implement, and
• A public Github repository link for your final project (this can be empty, for the time being).
  • If you must make your repository private for some reason, be sure to give the course staff view access.

Note: the only "submission" of code for your final project will be in the form of this Github repository link.

Design Check

The objective of this meeting is to ensure that you and your team understand what's involved in implementing your ideas. You don't need to submit your project plan anywhere, but it should be written down. It must include:

• A high-level overview of the flow of your final program
  • How will all the pieces fit together?
• Division of labor and a rough plan of action
  • Who will do what, and when?
  • Where will you start?
  • What if you do not finish everything you set out to do?*
• A description of how each feature will be implemented + any resources that you think might come in handy (e.g. papers, tutorials, algorithms, data)

Project Status Update

Remember that the deadline is only a week away at this point!

Final Presentation

Final presentations will take place on Thursday, 12/15, during lecture time (and slightly beyond, as we have a lot of students this year). We'll watch a compilation of all the pre-recorded video presentations; it'll be a great way to celebrate the hard work you and your classmates have put in this semester!

Reminder: you do not need to submit any code at this point, provided that it's still accessible at the Github repository link you submitted in your project proposal. Make sure your repository's README documents how to use your program and any known bugs!

Technical Requirements

Overall, we want your final projects to be cohesive and in-depth, but we don't have many strict requirements for what you must incorporate into your projects.

That said, if your group wishes to focus on one or two particular features and implement them to a higher degree of complexity, that's also fine! Discuss with your mentor TA or one of the HTAs to see whether your idea meets our technical requirements.

New Technical Features

Here's a list of technical features your group might want to implement:

This list is not exhaustive. It may not even overlap with what your group is interested in. Ultimately, your group can choose to do nearly anything in the realm of computer graphics (both 2D or 3D projects), as long as we've approved your project proposal.

• Ambient occlusion (e.g. screen-space ambient occlusion (SSAO))
• Anti-aliasing (e.g. fast approximate antialiasing (FXAA))
• Bump- or displacement-mapping, with the ability to toggle it on/off
• Camera or object motion along a path defined by a piecewise Bezier curve, (e.g. to render a ride on a roller coaster)
• Collision detection (with bounding boxes/spheres, or at the polygon level), possibly including rotational physics
• Depth of field
• Deferred lighting
• Environment maps (e.g. cube maps / skyboxes)
• Fractals: objects (e.g. plants) or terrain
• GPU raytracing
• High-dynamic range (HDR) rendering, perhaps with bloom
• Lindenmayer systems (L-systems)
• Non-photorealistic or stylized rendering (e.g. cel-shading)
• Piecewise Bezier surfaces
• Procedurally-generated art, environments, and/or geometry
• Shadow mapping, with the ability to toggle it on/off
• Shadow volumes, with the ability to toggle it on/off
• Volumetric Rendering
• Wave-function collapse for constrained geometry generation

For additional inspiration, you can find past SIGGRAPH papers at this link, compiled by year and by category. You can also view final projects from past years on this YouTube playlist. Some projects from older offerings of the course (i.e. before Daniel was the instructor) can be found here and here.

More Specific Technical Requirements

Real-Time Applications

If your project is a real-time application, it should run at a minimum of 24 frames per second (fps).

If this is unattainable for your project, but you would still like to present it in video form, we suggest using ffmpeg to create a video from image stills (such as those you might grab from a framebuffer).

Use of Existing Code / Third-Party Libraries

We allow and encourage you to re-use code you wrote for the earlier assignments in this semester, even including our support code.

You are also permitted to look at code from books and online sources, but you may not copy others' code and call it your own.

You may use third-party libraries if you wish, however, this should be cleared with your mentor TA first. Keep in mind that your use of a third-party library does not decrease the amount of work we expect you to do. Any third-party libraries you use must be cited in your Github repository's README.

Grading

Your grade for this project will be determined by several factors.

Technical Excellence

How well did you accomplish what you set out to do? Is your implementation stable (i.e. bug free and does not crash)? Does your project represent a significant, yet reasonable extension on the topics covered in the labs and assignments? We also expect that you will do something non-trivial. Your mentor TA will be able to guide you here.

Artistic and Aesthetic Quality

Does your demo look and feel cohesive? You don't have to create a full-fledged environment, but we also won't be impressed with a single shape in the center of the screen. We also encourage things like nice 3D models, nice textures (consider taking digital photographs and converting them to textures), thoughtful choice of colors and materials, careful positioning of camera and lights, significant user interaction, etc.

Presentation

Does it look like your presentation was thrown together at the last minute? Is your presentation sensible and well-organized? Were you able to effectively explain your implementation within the presentation time limit?

Where Do I Start?

There are many ways you can start the final project. For example, you might want to start from one of our assignments' stencils, if you think it might be useful for the features you want to implement.

Here's a guideline for final projects in general:

• Always begin by doing some research.
  • For inspiration, refer to the list and resources above.
  • When in doubt, ask Daniel or the TAs.
• Discuss ideas for potential projects with your team
  • Ideally, your final project is something that you should all have a say and interest in.

End

Whether you're reading this just as you're getting started with your final project, or having completed it, we hope you have/had fun!

Please let us know if you find any mistakes, inconsistencies, or confusing language in this or any other CS 1230 document by filling out our anonymous feedback form.