CS 4451A: Computer Graphics, Fall 2005

	Date	Topic	Tests/Projects	Slides	Assigned reading	Additional Resources
01	Aug 23, Tu	Subdivision curves,		Intro, Subdivide,	Bezier, EDR
02	Aug 25, Th	Vectors, Acceleration	P0 due	Vectors,		MathHelp, Ingram,
03	Aug 30, Tu	Containment, area		Area
04	Sep 1, Th	Distance, Intersection	P1a due	Intersect2D, Deviation,
05	Sep 6, Tu	OpenGL, Transforms		GL, Transforms,	openGL,
06	Sep 8, Th	Motions + Jim Hejl (EA)	P1b due
07	Sep 13, Tu	Driving control, simulation		IO,
08	Sep 15, Th		P1c due
09	Sep 20, Tu	-- REVIEW --
10	Sep 22, Th	-- MIDTERM 1 -- answers
11	Sep 27, Tu	Collision prediction		Collisions, Intersect3D Intersect	Prediction,
12	Sep 29, Th	Dynamics			Cignioni.pdf
13	Oct 4, Tu	T-mesh construction, traversal	P1d due	Meshes,	CornerTable
14	Oct 6, Th	CAD in IronCAD
15	Oct 11, Tu	T-mesh Normals, Curvature, smoothing	P1e due		Sharpen&Bend.pdf	Subdivision, Taubin
16	Oct 13, Th	Free-form deformations				Twister,
17	Oct 20, Th	Morphing	P1f due			Agrels, Pips
18	Oct 25, Tu	-- Project 1 presentations --
19	Oct 27, Th	-- REVIEW --
20	Nov 1, Tu	-- MIDTERM 2 --	P2a due
21	Nov 3, Th	Light, Color, Reflection		Light, Color, Lightfield,
22	Nov 8, Tu	Photorealism, IBR	P2b due	Raytracing, Radiosity Panorama
23	Nov 10, Th	Rasterization, Perspective		Raster Perspective,	Perspective,
24	Nov 15, Tu	OpenGL acceleration	P2c due	openGL, GL
25	Nov 17, Th	GPU, textures, shadows, occlusion		Shadows, Visibility	Shadows, ShieldTester
26	Nov 22, Tu	Transparency, Booleans	P2d due	CSG,		Stencil Buffers
27	Nov 29, Tu	Nonphotorealistic rendering		Silhouettes	Hidden,	Duke
28	Dec 1, Th	Perception, Visualization	P2e due	Perception
29	Dec 6, Tu	-- REVIEW -- Level Sets		Level Sets
30	Dec 8, Th	-- Project 2 presentations --
	Dec 13	-- FINAL 2:50 to 5:40 --

Plagiarizing is “to steal and pass off (the ideas or words of another) as one's own : use (another's production) without crediting the source” [Webster]. If caught plagiarizing, you will be dealt with according to the GT Academic Honor Code. Unless specifically identified as group work; quizzes, tests, take-home-tests, homework, etc. are to be completed alone.
If you find that the solution to a homework or to a problem that you must solve in a project is published in a book, article, webpage, etc., you may use it as an inspiration, provided that you clearly identify the source (providing a complete URL or bib reference) and that you rewritee it in your own words, providing detailed explanations showing that you understand the overall approach and the details of every step. In fact, you are encouraged to improve on that solution and to briefly document your improvement.
When working on a software project, you ("you" standing for a single student for individual projects or for the team for team projects) may use utilities and libraries developed by others for all the non-essential parts of your program, provided that you clearly identify their source in the header of your program. Examples of such utilities include graphics libraries, matrix multiplication, and linear solvers. The essential parts of the program (which relate to the material taught in class) must be entirely coded by you and must include clear comments.
If you find source code or high level algorithmic descriptions that implement the desired functions, you may use them as inspiration, provided that you clearly identify the source of inspiration both in your source file and on the project report and that you rewrite and comment the code in your own style, to clearly demonstrate that you understand its structure and details. Finally, I encourage you to discuss the projects with other students in the class and to freely share ideas and resources. You may also ask colleagues or the TA to help fix a bug in your code. But you may not use or copy their code.

Quadratic B-spine	Cubic Bspline	Jarek	Four point

Quadratic (green) and cubic (red) Bsplines	Four points (blue) and Jarek (magenta)