CS 284: CAGD, Fall 2009: Course Projects
Project Scope
-
Ideally, each project consists of three parts:
- some programming to implement some new capability,
- a good interface to make this capability usable
by others in a larger context,
- some demonstration of this new capability with some neat/useful final result.
-
Keep the projects small and well focussed!
There are only about 5 weeks left after the formal project proposal;
so this does not allow to construct large and elaborate systems.
Some of
the ideas proposed to me may be too ambitious for a complete implementation; but
you
can do an essential part for any one of them, and demonstrate that you
have mastered the basic concept.
-
Ideally projects should concern issues that are relevant to CS284:
1-, 2-, or 3-dimensional spline
manifolds or subdivision structures, or smooth implicit surfaces or point clouds.
It could comprise tools to design, edit, optimize, or decorate such surfaces.
It could be a variant or some enhancement of some published scheme.
It could be some converter between two different
shape representations.
I would like to see some demonstrable program that shows that you got
something to work based on
what you learned during this course.
Phase 1: Submit two (possibly vague) project ideas -- Due Date: Monday 10/19/2009
Hand in or e-mail: a descriptive sentence/paragraph for each one, for a discussion
with me and to get some feedback.
Phase 2: Definite Project Proposal -- Due Date: Monday 10/26/2009
E-mail me: a 0.5 to 1.0 page description of your chosen project.
Specify:
-
What you plan to accomplish.
-
The approach you will take.
-
The deliverables and demos you hope to provide.
-
Milestones: What you plan to have done before November 16.
Phase 3: Formal Project Proposal Presentation -- Monday 11/02/2009
This should be a short (5 minutes), formal, audio-visual presentation,
-- like for a "Venture Capitalist Rally" or for a "NSF Research Review
Panel."
Key point is to convince your peers that your project makes sense in
an academic R&D environment.
Clearly define:
-
The goal of the project
-
The approach you will take
-
The deliverables and demos resulting
-
Why this is a "good" project:
-
how useful it might be, or
-
just how "cool" it is going to be, or
-
what you hope to learn with this project ...
(a little "selling" job).
Phase 4: Written Progress Report -- Monday 11/16/2009
A 1-page written report, telling me what you have accomplished so
far and what the likely results will be that you can present in two weeks.
- In bullet form, state what you have already gotten to work.
- Also say what you have learned so far, and what change of plans this may have forced on you.
- Give your best estimate what you think you will have working in two weeks, and by the end of the semester.
Phase 5: Formal Project Presentation -- Monday 12/07 and Wednesday 12/09/2009
A 12 minutes formal, audio-visual presentation, discussing progress and
main results of your project.
-
Start with a brief reminder of the goal of the project and of the things
you promised to deliver.
-
Show the progress you have made towards that goal, and what remains to
be completed.
-
Illustrate something of general importance that you have learned, or a
difficulty that you had to overcome.
-
Show off the results that you are most proud of !
Phase 6: Final Project Demonstration -- By appointment, Thursday 12/10/2009 or Friday 12/11/2009
Arrange for a 30 minute time slot do demonstrate your project and discuss it with me.
Available time spans are :
Thursday 12/10 from 10:00am to noon, and from 2pm to 3:30pm.
Friday 12/10 from 9:30am to 11:00am, and from 3pm to 5:00pm.
-
Hand-in your project reports (4 to 10 pages) to me before
12/11/2009, midnight.
-
Transfer your code to me before
12/11/2009, midnight.
--> Back to current lecture
Page Editor: Carlo H. Séquin