CompSci 344
Spring 2015
Computer Graphics

Help is Available

Our goal is simple: to help you learn — both inside and outside the classroom. If you have questions, we want to answer them. We hold office hours just for the purpose of helping you, either one-on-one or in small groups. No matter how busy we may look, during office hours, you have priority over everything else. If you have a problem or question, come by and we can talk about it — do not put it off.

UTA Office Hours

You can bring code on your laptop or have it accessible (e.g., via Dropbox or USB drive) so the UTA can use another computer.

Hours will be held in The Link on Lower Level 1 of Perkins Library. They will be held near the cluster of chairs between Group Study 7 and Classroom 4 (see this map of the Link) or in one of the study rooms there. Check the discussion board to find out where the TA is sitting.

  Sunday Monday Tuesday Wednesday Thursday
5-6pm Ang
Allen CLASS   CLASS
6-7pm Ang Allen   Ang  
7-8pm Allen   David Ang David
8-9pm Allen   David
  David

If you cannot make our office hours, please use email to set up an appointment.

Posting to the Discussion Board

If you have any questions about the course, post your questions here because it is seen by all the course staff as well as all the students. The discussion board will be monitored regularly and responses posted to questions that have not previously been answered.

You should also regularly read and contribute to the course discussion board as it is a useful place for posting questions that are likely to be of interest to the rest of the class. You are encouraged to post responses to questions as well as ask them. Before posting a question, please make sure that you have read all previous messages and that your question has not yet been discussed.

In order to get the fastest possible response, it is important that you are as clear as possible when describing your problem. To this end, include exact error messages or steps you followed. Finally, please include evidence of trying to solve the problem yourself before posting.

When posting code, be very careful not to post so much as to give away your solution to your classmates. Indeed, such posts may be considered cheating!

Post as little code as possible in order to describe your problem. In many cases, you may be able to post only the single line that is causing the problem. In cases where it is necessary to post more, you may want to replace some parts with comments representing pseudocode if possible. Never post complete functions. If you are in doubt, post a private message to the course staff.