Course Hours:
 

	Day & Hour		Location
Lecture	Sunday	12:00-13:45	Levin 8
Tirgul	Wednesday	16:00-17:45	Sprinzak room 116

Course Recommended books:

Computer Graphics: Principles and Practice, Foley, van Dam, Feiner, Hughes (2nd edition).
OpenGL programming Guide, Mason Woo, Jackie Neider, Tom Davis, Dave Shreiner.
Curves and Surfaces for CAGD: A practical guide, Gerald Farin, 3rd edition.
Radiosity & Global Illumination, Francois X. Sillion, Claude Puech.

Submission Guidelines:
 

Register, Submit and Get grade

We use the Systems server to register, submit and get grade : HTTPDYN Server .
Stay tuned to the course newsgroup( local.course.cg), as we may publish important information there.
Every correction that we give through the news group is considered to be mandatory.

Programming Guidelines::

     You may use either C or C++.
     Your programs should compile and link with no warnings.
     Your executable name should be exN, where N is the number of the exercise.
     Exercises should be submitted on linux only.

     We expect your programs to be written in good programming style and to be readable
     and understandable. For that purpose, follow  the guidelines below (which we assume reflect your
     natural programming anyway ...):

     Documentation:
          Document your code !
          In the head of each file write it's name and a short description of the file's content.
          Before declaring or implementing functions / methods describe it's purpose.
          Document your code whenever you think it's not understandable enough.
          Make your documentation short and clear.
     Modularity:
          Don't write too long functions;  Divide large blocks of code to several functions, to make things more readable.
          Design your program before you begin coding it.
          Avoid code repetition
     Naming conventions:
          Use meaningful names for functions and variables, even if you have to use long names.
          Be consistent with your naming conventions. e.g., if you start functions with capital letter, keep it so with all your functions.
          Note: the conventions of OpenGL, GLU and GLUT are to prefix their functions, types and macros with  gl / GL / glu / glut .
          Therefore do not use these prefixes for the names you give in your code.

Files To Submit:

     You should submit exercises on the computer using the HTTPDYN server.

     You need to submit a tar file containing the following files:

     Only if stated in the exercise definition: a README file as specified in the exercise definition. The file should begins with your login name(s).

     Submit a Makefile , that  generates executable named exN from the submitted sources using the command make (where 'N' is number of
     submitted exercise). NOTE: Make sure the Makefile works correctly from any directory it is in along with the source files.
     Submit all the source files of your program. Do not include no files that are not part of the solution (core files, temporary files, etc). Do not include files that can
     be generated from the sources (e.g. *.o, files, or executables).

     Tar File:
         Create a tar file called exN.tar (where N is the number of the exercise, e.g. ex1.tar for exercise no. 1) that contains the files you should submit, and then submit only the
         tar file. See man tar for more information.

Submitting a Printout:

    You should submit a printout to the cg box located at Ross -2.

Late Submissions :

If you submit your exercise after the deadline given, you will loose 3 points for every day. We don't count Fridays and Saturdays.