Computer Science 426
Computer Graphics
Final Projects
Written Proposals (due 8AM on Monday, December 13):
Each team of students should submit a one-page written project proposal.
The proposals should include enough detail to convince a reader that you've
found a good problem, you understand how hard it is, you've mapped out
a plan for how to attack it, and you have an idea about which experiments
you might run to test the success of your implementation. Please
do not be vague in your written descriptions. Following is a brief
outline you might follow ...
-
Goal
-
Previous Work
-
What related work has been done?
-
Approach
-
What approach are we going to try?
-
Why do we think it will work well?
-
Methodology
-
What steps (task list) are required?
-
Which of these steps is particularly hard?
-
What to do if the hard steps don't work out?
-
Metrics
-
How will we know when we are done?
-
How will we know whether we have succeeded?
-
Summary
-
What will we learn by doing this project?
A "mentor" will be assigned to each team (either Tom, Wagner, or
Rob). During class on Monday, December 13, the mentors will go over
the project proposal of each team and advise the team about their best
plan of attack.
Project Proposal Presentations (during class on December 15 and 17):
Each team of students will give a 5 minute talk to present his/her course
project proposal to the class (with overhead transparencies, slides, videos,
and/or other props). You should be sure to convince us that: 1) you
are addressing an important problem, 2) you understand various approaches
to the problem, 3) you have found an interesting approach to attack the
problem, 4) you have a SPECIFIC, DETAILED plan, and 5) you will know when
you are done. Five minutes is a very short amount of time. So, please come
with a presentation that is concise and to-the-point. You probably
want to use around 3-5 slides following the outline above.
Final Written Reports (due at 5PM on Tuesday, January 11):
Each team of students should submit a six- to ten-page written final report.
The written report should contain descriptions of the goals and execution
of your project. You should include a review of related work.
You should write detailed descriptions of the approach you've chosen, the
implementation hurdles you've encountered, the features you've implemented,
and any results you've generated. Please do not be vague in your
written descriptions. Following is a brief outline you might follow
...
-
Introduction
-
Goal
-
What did we try to do?
-
Who would benefit?
-
Previous Work
-
What related work have other people done?
-
When do previous approaches fail/succeed?
-
Approach
-
What approach did we try?
-
Under what circumstances do we think it should work well?
-
Why do we think it should work well under those circumstances?
-
Methodology
-
What pieces had to be implemented to execute my approach?
-
For each piece ...
-
Were there several possible implementations?
-
If there were several possibilities, what were the advantages/disadvantages
of each?
-
Which implementation(s) did we do? Why?
-
What did we implement? <== Include detailed descriptions
-
What didn't we implement? Why not?
-
Results
-
How did we measure success?
-
What experiments did we execute?
-
Provide quantitative results.
-
What do my results indicate?
-
Discussion
-
Overall, is the approach we took promising?
-
What different approach or variant of this approach is better?
-
What follow-up work should be done next?
-
What did we learn by doing this project?
-
Conclusion
Demo Day (2PM on Thursday, January 20 in MECA):
Each team of students will give a short `poster session' describing his/her
class project. Your goal should be to demonstrate and describe for
the class in 10-15 minutes what you have done and why it is interesting.
In addition to running a live demo on one of the computers , you should
describe the guts of your project, possibly using 4-8 `slides' on a poster.
The slides should clearly present the goals, challenges, previous work,
approach, implementation, and results of your project.
Some Ideas for Final Projects:
-
Rendering
-
Modeling
-
Polyhedral mesh editor supporting boolean operations
-
Polyhedral mesh fixup (check out CADfix)
-
Progressive mesh system (check out Hugues
Hoppe's web page)
-
Tensor product spline surface editor
-
Marching cubes construction of iso-surfaces from volumetic data
-
Procedural modeling system based on fractals, etc. (check out the Stanford
348C course projects)
-
Animation
Links to Final Projects from Previous Years:
1998
Modeling
and Rendering Architecture from Photographs
Rob Kalnins, Hidekazu Oki
1998
Ice
Queen
Mao Chen, Zaijin Guan, Zhiyan Liu, Xiaohu Qie
1998
1996
Something
Wonderful
George Karakostas, Kostas Tsioutsiouliklis, Tassos Viglas
1996
JAW ray tracer
Jing Li, Aaron Lee, Wagner Correa
1996
1995
Landscape
Designer
Dirk Balfanz, Igor Guskov, Sanjeev Kumar, Rudro Samanta.
1995
Links to Other Resources