Todo

General

Course-Specific Academic Conduct Expectations

What's allowed

• working directly with team members and discussing solutions in detail with them
• researching on the web to find tutorials for WebGL/Three.js and graphics
• discussing the merits of a proposed solution with instructor or TAs
• using code provided by the instructor
• discussing general approaches for assignments with other students. if you do have any significant discussion with other students outside your team about a specific assignment:
  • one-hour context switch rule: do not take any written notes, and then do something else for an hour before you go back to work on your own. Some folks call this the "Gilligan's Island" rule - but you can do whatever you want during that hour break, it doesn't have to be watching mindless TV!
  • attribution: acknowledge your discussion by including a list of their names in what you hand in: either as comments at the top of the code, or in a README file.

• doing assignments with a large group of other people and handing in the joint work as your own
• getting or giving code to anybody else not in your team electronically (email, IM/chat)
• getting or giving code to anybody else not in your team on paper
• typing in code you see on another student's screen in the lab
• using code somebody else wrote in a previous term
• paying somebody money to do the assignments
• looking at somebody else's paper during an exam
• looking at unauthorized materials during an exam

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, or discussions with your team members. 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 non-team 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 outside the four-person team limit 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.

If you have any questions at all about a grey area, don't hestitate to ask the instructor.