| Instructor:
Lawrence S. Kroll, Ph.D.
Class meets: Thurs 7:00 - 9:45pm in TH 409
Office hours: Thurs 6:00 - 7:00pm and 9:45 - 10:15pm in SCI 255 and by appointment.
Office phone: (415) 338-2539.
E-Mail to kroll@sfsu.edu
(Email to kroll should be sufficient from most machines.)
WWW Home Page: http://online.sfsu.edu/~kroll |
|
| Required: CSC
630 Class Handbook
Author: Lawrence S. Kroll
Publisher: SFSU bookstore
Suggested Text:OPENGL PROGRAMMING GUIDE
Authors: OpenGL ARB, Woo, Neider, and Davis
Publisher: Addison Wesley (available from Amazon.com)
Suggested Text: Interactive Computer Graphics, 4th edition
Author: Edward Angel
Publisher: Addison Wesley
Suggested Text: OPENGL REFERENCE MANUAL latest edition
Authors: OpenGL ARB, Kempf, and Frazier
Publisher: Addison Wesley
Reference Text: OpenGL SuperBible: Comprehensive Tutorial & Reference
Authors: Wright and Sweet
Publisher: Waite Group Press
|
|
| Prerequisite:
A grade of C or better in CSC 313 and Math 325 (Linear Algebra) |
 |
| Catalog
Description:
This course covers computer graphics systems design and display hardware
architecture.
An overview is given of device independent graphics systems, two- and
three-dimensional viewing pipelines, hidden line and surface removal
algorithms, raster graphics techniques and color space models.
Web page design and Flash exercises give an introduction to animation
and multimedia.
Programming with the OpenGL library affords
the class a chance to design advanced animation programs in three-dimensions. |
|
| Programming
Projects:
We program extensively in C, C++, HTML, and Flash Actionscript.
You can use the UNIX, Windows, Mac, and Linux operating systems.
The PROGRAMMING PROJECTS are an important part of this course and comprise about
1/2 of your grade.
Late project penalty: 3 points will be deducted for each lecture (week) late.
No extra credit will be given for late projects.
To pass this course you must do the assigned projects.
Under no circumstances
will a grade of I (incomplete) be given.
Other students may not write your programs or any portions
of them for you.
The only exception is the team project in which you code in a selected
group.
Project assignments offered on the Internet will be reported to the Administration.
Disability Policy: Students with disabilities who need reasonable accommodations are encouraged to contact the instructor.
|
|
Extra
Credit:
I am looking for errors in my Class Reader code and bad links in my web
pages.
If you can find such errors, e-mail me the exact problems, and I’ll
award you extra credit.
|
|
Grading:
Projects are scored in 2 parts. The submitted project itself is
graded according to a listed specification.
In addition, there
are demo points which are more subjective (i.e., the instructor may give
additional points to the projects which demonstrate better).
Your grade is based on your total points using a standard curve:
Programming projects 45%
In Class Participation Extra Credit 10%
Examinations 45%
100%
|
|
Missed
Exam Policy:
Generally, there will be no make-up exams and no incomplete grades
given.
If you miss an exam, you must notify the instructor before the exam
or, if physically impossible, soon after.
If any of the scheduled exam dates are in conflict with your religious
observances,
you must notify your instructor, in writing, during the first two weeks
of the semester.
If you have an acceptable, documented excuse, you may be given a make-up
exam
or be given the average score of other exams at the discretion of the
instructor.
|
|
Class
on the Web :
This class uses the Web Classroom Application called iLearn
to show course assignments,
grades, announcements, the schedule, and as an online discussion group.
You should be automatically enrolled in course CSC 630.
https://ilearn.sfsu.edu/login/index.php
|
|
Please :
As a courtesy to all, please turn off your cell phones.
If your cell phone
interrupts the class, you will lose credit!
|
|
| Program
Format:
Your projects are to be submitted in professional form.
All OGL projects should be submited in a multisession CD, labeled outside with your name and
the course number.
Begin each program with a heading that includes your name, course number,
project description, date.
Include the source code and enough graphic output to convince me that
your program works.
I appreciate color graphic output as well as an executable on
disk. Let me see the magnificence of your work. If you are using
libra, verify that I have permission to execute your project and read
your directory.
If you are
unable to provide hardcopy graphics that show the magnificence of your
work, post your graphics on a web page and send me the URL.
On a file
type a one or two paragraph informal discussion of what you thought
of the problem, how hard it was for you, etc.
I appreciate hardcopy color graphic output (on the CD) of your GUIs as
well as the executable.
Include
a short discussion and evaluation sheet with every project.
See
Basic Style and Documentation Guidelines in the notes.
Start
your program with a .h file holding data types, global variables, functions,
& helpful comments.
Every
function should begin with a comment detailing its purpose.
Separate your functions before and after with at least two blank lines
and a comment line that stands out
to separate it from code.
(*____________________________________________*)
If your English
is not good, have a friend review your discussion and comments.
Text
for menus should go on a separate file called menu.txt.
This is handy for quick translation to other languages.
Overwrite
advanced code you want credit for with a marker so I notice
it.
|
|
| |
|
