|
|
|||
|
Lec. session
|
|
Lec. Location:
|
|
|
Office Phone
|
|
Office #:
|
|
|
Office Fax
|
|
Office Hours:
|
M 11:00 am - 12::00
pm
W 10:30 am - 12:00 pm, W 1:30 pm - 2:00 pm |
|
Email Address
|
|
||
|
Mailing Address
|
1600 Holloway Avenue San Francisco, CA 94132 |
||
Course Web page
http://tlaloc.sfsu.edu/~yoon/csc890
| Prerequisites | Grade C or better in CS630. . |
| Text | Core Web3D by Aaron E. Walsh and Mikael Bourges-Sevenier, Prentice-Hall |
| Recommended Reader | 1. Java for 3D and VRML worlds by Rodger Lea, Kouichi Matsuda and Ken
Miyashita, New Riders publisher
2. Guide to 3D avatars by Sue Ki Wilcox, Wiley publisher 3. The Internet in 3D edited by Rae Earnshaw & John Vince, Academic Press |
|
|
|||||
|
|
|
|
Assignments |
|
|
|
(starting from 9/10) |
Introduction to Web3D | Text chapter 1 & 2, Foreword | |||
|
(starting from 9/17) |
Interactive 3D graphics overview | Text chapter 3 | Project 1 | Introduction I , Introduction II | |
|
(starting from 9/24) |
VRML | Text chapter 4, 5, 6 | VRML
VRML examples |
||
|
(starting from 10/1) |
VRML | Text chapter 7, 8, 9, 10 | VRML
2
Multiuser server , VRML examples |
||
|
(starting from 10/8) |
VRML, Web Server, XML | Text chapter 11, 12 | Project 2 | Web Server | |
|
(starting from 10/15) |
VRML, EAI | Text chapter 13, 14 | Project
1
due on 10/8 |
||
|
starting from 10/22) |
VRML | ||||
|
(starting from 10/29) |
X3D, XML | Text chapter 16, 17 | XML notes , X3D FAQ , | ||
|
(starting from 11/5) |
Midterm Report Class Presentation | Project
2
due on 11/5 |
|||
|
(starting from 11/12) |
MPEG4 | Text chapter 20, 21 | |||
|
(starting from 11/19) |
Other techniques (Viewpoint) | Viewpoint white papers | |||
|
(starting from 11/26) |
Image-based rendering techniques |
Ray Tracing program Rasterization program |
|||
|
(starting from 12/3) |
3D avatars | Guide to 3D avatars | Project 3 (Complete MU 3D game) due on 12/3 | ||
|
(starting from 12/10) |
Term
project
Class presentation |
||||
The mid-term and final are cumulative, since much of the later material in the course depends on the early material. All exams are closed book, closed note, no calculator. Makeup exams will not be given. Absence due to a serious illness will be an acceptable reason for missing an exam, and the final grade will be scaled accordingly.
Assignments
Programming assignments are graded on thorough testing, documentation, and style, as well as correctness. All work to be submitted for the class is to be done individually unless an assignment specifies otherwise.
Grading
The following is the relative weight of each part of the course work. At the end of the semester, you will have a score out of 100 percent. This score will be used in a class curve (relative ranking) to arrive at a letter grade.
| 2 Projects | 2 * 15% = 30% |
| Term Projects | 20% |
| 1 Midterms + 1 Final exam | 20% + 30% =50% |
Midterms will be held in class. The final is on Wednesday December 19, 1:30pm-4:00pm , in your regular classroom. No rescheduling will be allowed for travel-related reasons.
General Information and Class Policies
Class accounts:
(1) If you are a new student, you will need to get an account on the
AFS cluster (apollo.sfsu.edu). You will be able to
receive email and access the internet on this account. All students
enrolled in this course will be given access to an additional machine,
libra.
(2) You should log on to your account at least 2-3 times a week to check email, even if you are not working on a project that week. I send out information related to the class periodically via email, including changes in current assignments, deadlines etc.,and you are responsible for keeping up-to-date by checking your email regularly. All email to me should be directed to yoon@cs.sfsu.edu. Project submissions should also go to the same account.
(3) You should be the only person who has access to your account. Do not give out your password. Do not let a friend use your account,or use a friend's account. Either action may result in temporary suspension of your account privileges.
Attendance:
(4) You are responsible for all information given out in class. If you
are unable to attend a regular class period, make sure you find out from
a classmate about the lecture and handouts. (And it might be a good idea
to get your information
from a friend rather than an enemy.)
(5) If you are unable to attend a class period when a test is scheduled, you must contact the instructor before the test. If you are unable to take a test for medical reasons, you must have proof from a doctor, the health center etc. Otherwise, you will get a zero on that test.
Late projects:
(6) All projects are due at the announced deadlines. You may turn in late projects within 48 hours of the deadline, for 75% of the credit. There will be no negotiations (except for serious and compelling reasons, and they better be serious and compelling reasons).
(7) ``Libra was down'' is not considered to be a serious and compelling reason for missing the deadline. You will be given at least 2 weeks to work on each assignment. There is no excuse for waiting till the last minute.
Cheating:
(8) This is taken very seriously. Don't do it.
(9) All projects, unless otherwise specified, are individual projects. This means that you're expected to work on them on your own,and not in collaboration with other students. You may do preliminary planning with other students in the early stages of the project,or help a friend debug her/his project. However, if the code in your projects is found to be very similar, this is considered cheating, even if you worked together to produce the code.
(10) Submitting someone else's work as your own is considered cheating. Letting someone else submit your work as her/his own is also considered cheating, and will be treated equally.
(11) If you wrote your code on your own, you must be able to explain its details. If you are unable to explain the details of code that you turned in, I consider this a strong indication that you did not write the code on your own; in that case, I have the option of giving you a zero on that project, and reporting the incident to the department chair.
(12) Depending on the seriousness of the offense, students caught cheating
could be assigned an "F" in the course, or be expelled from school.