CSC 197B - First Year Seminar: Algorithmic Art (Fall 2006)

Time and Location:

TTh 2-3:50 pm, Julian 260

Professor:

Brian Howard (bhoward@depauw.edu)

Office:

Julian 266 (658-4120)

Office Hours:

TTh 4-5, WF 2-4, anytime my door is open, or by appointment

Course Home Page:

http://asimov.csc.depauw.edu/moodle/course/view.php?id=4

Texts:

• David Cope, "Virtual Music", MIT Press, 2004, ISBN: 0262532611
• Pamela McCorduck, "Aaron's Code: Meta-Art, Artificial Intelligence, and the Work of Harold Cohen", W. H. Freeman & Co., 1990, ISBN: 0716721732
• Mark Guzdial, "Introduction to Computing and Programming in Python, A Multimedia Approach", Prentice Hall, 2005, ISBN: 0131176552 (also available by subscription as an online text from SafariX)

Course Description:

This seminar will explore techniques for creating and manipulating pictures and sounds through computer programming. While doing this, we will examine some of the implications of using a computer in the creative process: Who is the creator? Is it really art? What is the connection between structure, randomness, and aesthetics? Students will learn the basics of programming in a modern, high-level language, as well as a variety of methods of representing, generating, and modifying digital media such as bitmap images, vector drawings, audio wave files, and MIDI sequences. Classes will consist of a mixture of discussions, lectures, demonstrations, and hands-on lab experience.

Generally, the class sessions will follow this plan:

• Tuesday: Demos of mini-projects, programming lecture, in-class exercise and discussion, assignment of programming homework
• Thursday: Reading discussion, review of programming homework, assignment of mini-project, lab time to work on mini-project and weekly reflection

Grading:

The grade for this course will be based on the following:

• Programming assignments and quizzes: in order to learn to program in Python, there will be weekly homework problems and occasional quizzes (20%)
• Midterm exam: Thursday, October 5, covering the fundamentals of Python (15%)
• Writing assignments: two significant papers, plus weekly reflections (25%)
• Participation: contribute to discussions and demo sessions, and serve as one week's discussion leader (20%)
• Final project and portfolio of work (20%)

The grading scale used for this class will be the following: A (93-100), A- (90-92), B+ (87-89), B (83-86), B- (80-82), C+ (77-79), C (73-76), C- (70-72), D+ (67-69), D (63-66), D- (60-62), F(0-59). I reserve the right to alter this grading scale at any time. The last day to withdraw from class is Friday, October 13^th.

Policy Statements:

• You are expected to attend all class sessions. However, I expect you to take your own education seriously, so I do not keep formal attendance records. If you miss a class, you are responsible for catching up with the material that was covered and any announcements that were made.
• Assignments are due at the start of class on the assigned date. Late submissions will be accepted until the next class time at a penalty of half the grade. Extensions will be considered only by prior arrangement.
• Cheating, plagiarism, submission of the work of others, etc., violates the DePauw policy on academic integrity and may result in penalties ranging from a lowered grade to course failure or expulsion. The policy and discussion of each student's obligations and rights are in the Student Handbook.
• With respect to this course, no collaboration is permitted on exams or quizzes. You may discuss homework problems and programming assignments with anyone you want (in fact, you are encouraged to do so), but you should not copy another student's work nor permit your work to be copied. The key idea is that you should understand all of the work you turn in, and you should be able to replicate it on your own. If you do not feel that you can replicate the work independently, then it is not fair (to yourself or to others) to submit it as your own work. If at any time you are uncertain what constitutes "appropriate" collaboration, it is your responsibility to clarify it with me.
• During class time, your computer should be used for note-taking, classroom interaction, and in-class exercises. You are not permitted to read e-mail, browse the web, play games, etc. while class is in session (unless the current activity calls for it...).
• Regrade requests will be entertained for up to one week after the assignment or exam is returned to the student. To request a regrade, please write out on a separate sheet of paper your request and attach it to the assignment or exam, and give it to me. A simple request for more points without a justification is not sufficient! Keep in mind that the entire assignment or exam may be regraded, so carefully consider your requests!
• Please feel free to offer me feedback (positive and negative) about my performance or anything else related to the class. This feedback will have no effect on your grade in the class.
• Reading assignments will be given in class. In addition to readings from the course texts, additional materials may be provided, either as handouts or as links on the web. You are expected to be prepared to discuss each day's reading when you arrive to class.
• All information about the class, whether given in this handout or in class, is subject to change.

Calendar:

Week	Tuesday	Thursday	Readings (tentative)
1		Aug. 24	Guzdial ch. 1
2	Aug. 29	31	Guzdial ch. 2; McCorduck pts. 1-3
3	Sep. 5	7	Guzdial ch. 3; McCorduck pts. 1-3
4	Sep. 12	14	Guzdial ch. 4; McCorduck pts. 4-6
5	Sep. 19	21	Guzdial ch. 5; McCorduck pts. 4-6
6	Sep. 26	28	Guzdial chs. 6-8
7	Oct. 3	5: Midterm	Guzdial ch. 9
8	Oct. 10	12	Cope ch. 1; Aaron paper due
Fall Break
9	Oct. 24	26	Guzdial chs. 10-11; Cope chs. 2-3
10	Oct. 31	Nov. 2	Guzdial ch. 12; Cope TBD
11	Nov. 7	9	Guzdial ch. 13-14; Cope TBD
12	Nov. 14	16	Guzdial ch. 15; Cope TBD
13	Nov. 21	Thanksgiving Break	Guzdial ch. 16; prepare for debate
14	Nov. 28	30	Debate
15	Dec. 5	7	Wrap-up; Debate paper due
Finals Week: turn in final project and portfolio of mini-projects