Policies: CPSC 314, Computer Graphics, May 05
Prerequisites |
Content |
Grading |
Grace Days |
Severe Illness or Other Problems |
Plagiarism
Prerequisites
- CPSC 216 (Program Design and Data Structures)
- MATH 200 (Calculus III)
- MATH 221/223 (Matrix Algebra/Linear Algebra)
- C/C++ programming skills
Content
Topics to be covered include most or all of the following: the basics
of 2D and 3D rendering; the rendering pipeline; scan conversion;
colour models; geometry data structures; geometric transformations;
perspective projection; hidden surface removal; lighting and
illumination; texture mapping; texture filtering; complex shading
algorithms; ray-tracing; animation.
Grading
Evaluation criteria
- 45% programming projects (9% P1, 9% P2, 9% P3, 18% P4)
- 25% final
- 15% midterms (15% midterm 1)
- 15% written assignments (5% H1, 5% H2, 5% H3)
The course grading scheme may be modified at the discretion of the
instructor. Midterm and final exam scores may be scaled at the
discretion of the instructor.
Project Grading: There will be face-to-face grading for each
project, where the student will sign up for a slot to demo the project
to the grader in the lab. You may be asked to explain the algorithms
used in your project to the grader. If you cannot explain an
algorithm, you will not receive credit for completing that part of the
assignment.
Regrading:
If you would like to request an assignment or exam from the professor,
you must submit a detailed written explanation of why you think the
grader was incorrect for the particular problem that you are
disputing. The professor will regrade the entire assignment or exam,
not just the particular problem in question, so your total grade may
end up higher or lower.
Attendance: Attendance in all lectures and your registered lab
section is expected. You are responsible for all material presented
there. Most material for both the lectures and the labs will be made
available online. However, there is no guarantee that everything
covered in lecture and labs will be in the posted material.
Grading Percentages:
Percentage (%) | Letter Grade |
90-100 | A+ |
85-89 | A |
80-84 | A- |
76-79 | B+ |
72-75 | B |
68-71 | B- |
64-67 | C+ |
60-63 | C |
55-59 | C- |
50-54 | D |
0-49 | F |
Grace Days
Late policy:
It is important that assigned work be completed on time, because
subsequent assignments depend on your comprehension of earlier work.
To allow for unforeseeable circumstances, you will be allowed three
days of grace during the quarter, which can be used on any assignment
or project with no explanation required. Use these as you wish to help
manage your time, but use them wisely. It is strongly
recommended that you do not use all your grace days early in the term.
You can use all three on one assignment, or spread the days across
multiple assignments.
Beyond your three grace days, late assignments will cause you to be
penalized by 25% of the possible mark for that assignment per 24-hour
day that it is late. Late demos will be subject to the availability of
the grader. No late work
will be accepted after solutions have been handed out.
Exceptions to this late policy will be made only with advance approval
from the instructor; or medical, emotional, or other problems
documented in writing as below.
Severe Illness or Other Problems
See the UBC Policy on Academic Concession.
Documentation of Severe Illness or Other Problems: It is
the responsibility of the student to provide adequate documentation of
the situation and to inform the instructor in a timely manner so that
the necessary appropriate action can be taken. Often written
assignments and programming projects will be granted no-penalty
extensions, but all cases are subject to the instructor's discretion.
Usually it is expected that the student will provide a written
explantion of the situation to the instructor within three days of
returning to the University after any absence or period of illness or
other problem. In no case will documents be considered more than seven
days after a student has returned to the University. The form for illness (or other problems) must be
submitted along with supporting documentation (i.e. a doctor's note in
cases of illness); talking to or emailing the instructor is not an
acceptable substitute for submitting the required form and supporting
documentation.
One of the following courses of
action will be taken after receipt of appropriate documentation of the
situation.
- At the discretion of the instructor (for example, when
solutions have not yet been distributed), the student will be allowed
to turn in an assignment or project late without the
late penalty.
-
At the discretion of the instructor (for example, after solutions have
been distributed), the student will be excused from completing that
assignment and graded only on the completed work.
-
If the missed work is a significant portion of the term mark, then a standing
of AEGROTAT may be awarded, as provided for by the University's policies.
A student will always be able to elect this option if the missed work is
a final exam.
-
In rare cases, where there is clear justification, a deferred examination
may be given to the student if the missed work is a final examination,
subject to approval by the Office of the Dean of Science.
Students will be consulted before a course of action is chosen, but the
final decision will be that of the instructor except as noted above.
Missing the Final Exam:
See the Academic
Concession FAQ for the UBC Faculty of Science for the examination
deferral request policy.
See also the advice from the UBC International Student Handbook listing legitimate vs. inadequate reasons for missing a final.
Religious Holidays:
Students who are scheduled to attend classes or write examinations on
the holy days of their religion must notify the instructor in writing
two weeks in advance of the religious holiday they wish to observe.
The instructor will provide opportunity for students to make up the
missed work or examination without penalty. See the Calendar entry on
Religious
Holidays
Plagiarism and Cheating
Read the Computer Science Department's
Guidelines and Practives
Regarding Collaboration and UBC Policy #69 on Student Discipline.
Consult the University's policies and procedures regarding
academic offenses for more information on plagiarism and the
penalties sanctioned by the University.
Collaboration
Collaboration between students is not permitted in CPSC 314 except in
explicitly declared joint final projects. As explained in the CS
collaboration guidelines, general discussion of programming
projects and written problem sets is allowed. However, source code may
not be shared: all forms of reuse, such as electronic copying of a
current or former student's source files, typing in source from a
printout, or typing in source read from another student's screen, will
constitute an act of plagiarism in the context of CPSC 314.
Citation
You are expected to cite all sources of inspiration (Internet or book
or human) in your writeups. Acknowledging your sources of information
in writing is the best way to avoid grey areas of possible academic
misconduct. You do not need to cite anything covered in lecture or in
the assigned readings, or discussions with the instructor or TAs. You
should cite all other sources in writing: either at the end of the
README documenting your program for programming projects, or in a list
at the bottom of an assignment turned in on paper. In the case of
written assignments, any people with whom you have had extended
discussions should be listed at the bottom of the paper that you turn
in. Casual discussions of a few minutes do not need to be documented,
but study groups do.
The Web is full of fantastic resources for students: detailed
tutorials with well-annotated source code; archives of mailing lists
and newsgroups that contain programming questions and answers; and
explanations of how to avoid, fix, or work around common (or uncommon)
errors. You are welcome to use these resources responsibly, as long as
you cite the sources. For example: if you looked at code fragments
from the Web or from other books, list the Web sites or book titles in
the References section of your README. Looking on the Web for ideas
and information is permitted and encouraged. Even looking at sample
graphics code is permitted, but simply copying that code and handing
it in as your own is not. You will be asked to explain algorithms
during the face-to-face grading slots, if you are not able to do so
you will not receive credit for that part of the assignment.
Due Diligence
In the context of CPSC 314, every student is held responsible to ensure that:
-
his or her files (which contain material the use of which, by another student,
would constitute an act of plagiarism as herein defined) are inaccessible
to other students,
-
current or out-of-date hardcopy of her or his files (which contain material
the use of which, by another student, would constitute an act of plagiarism
as herein defined) is inaccessible to other students, and
-
communication with other students does not include information the use
of which, by another student, would constitute an act of plagiarism as
herein defined.
Failure to comply with any of these responsibilities, either knowingly
or through negligence, will also be considered an act of plagiarism
indistinguishable from that of the other student(s) and subject to the
same penalties.
Plagiarism on Exams
All instances of plagiarism on exams will be referred to the Chair of the
Undergraduate Affairs Committee and the Dean of the Faculty of Science.
Cheating
Cheating includes, but is not limited to: falsifying any material
subject to academic evaluation; having in an examination any materials
other than those permitted by the examiner; and using unauthorized
means to complete an examination (e.g. receiving unauthorized
assistance from a fellow student); giving somebody else money to
complete course assignments instead of doing them yourself.
Penalties
The first offence within the context of CPSC 314
(across all years, terms, etc.) shall cause the student to receive
a mark of 0 for all assignments, and the Chair of the
Undergraduate Affairs Committee will receive a report detailing the
particulars of the case. Further disciplinary action may be undertaken
by the department, faculty, or university. A second offence within
the context of CPSC 314 (across all years, terms, etc.) shall cause
the student to receive a grade of 0 for the course, the student
will not be permitted to enroll in further offerings of CPSC 314,
and the Chair of the Undergraduate Affairs Committee will receive a
report detailing the particulars of the case. Further disciplinary
action may be undertaken by the department, faculty, or university.
Students not enrolled in CPSC 314 who are involved in a
314-related plagiarism incident will not be permitted to enroll in
future offerings of CPSC 314, and the Chair of the Undergraduate
Affairs Committee will receive a report detailing the particulars of
the case. Further disciplinary action may be undertaken by the
department, faculty, or university.
Although the instructor
reserves the right to exercise leniency as she sees fit, the
instructor usually considers cheating to be an insult to all other
course participants, and aggressively prosecutes cheaters in order to
create a level playing field where individual efforts are rewarded
appropriately.
Tamara Munzner
Last modified: Mon May 16 23:06:23 PDT 2005