Difference between revisions of "220b-winter-2008/hw0"

From CCRMA Wiki
Jump to: navigation, search
(Homework #0: Computational (An)aesthetics)
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Homework #0: Computational (An)aesthetics =
 
= Homework #0: Computational (An)aesthetics =
 +
 +
Due date: 2009.1.16 11:59:59pm (or thereabout), Wednesday.
  
 
=== Reading ===
 
=== Reading ===
 
* first, read/peruse [http://en.wikipedia.org/wiki/Cellular_automata CA article] and [http://ccrma.stanford.edu/courses/220b-winter-2008/readings/cslifeuniverseeverything.pdf this paper]
 
* first, read/peruse [http://en.wikipedia.org/wiki/Cellular_automata CA article] and [http://ccrma.stanford.edu/courses/220b-winter-2008/readings/cslifeuniverseeverything.pdf this paper]
** no need to worry about the details for now, just get a sense of what it's about, and think about the ideas in the paper
+
** no need to worry about the details for now, it's more important to get a sense of the ideas of cellular automata and the paper
 
** in fact, try spending no more than 30 minutes total on the wikipedia article and paper combined
 
** in fact, try spending no more than 30 minutes total on the wikipedia article and paper combined
  
Line 9: Line 11:
 
=== Specification (part 1 of 2): Response ===
 
=== Specification (part 1 of 2): Response ===
 
* respond to the reading assignment in '''one''' of the following ways:
 
* respond to the reading assignment in '''one''' of the following ways:
*** '''either''' a chuck program (of any desired length) that makes sound  
+
** '''either''' a chuck program (of any length) that makes sound  
*** '''or''' a brief written/textual response (can be as short as a paragraph, or as long as uh two paragraphs, or more)
+
** '''or''' a brief written/textual response (can be as short as a paragraph, or as long as uh two paragraphs, or more)
*** '''or''' a drawing / image, or something else graphical
+
** '''or''' a drawing / image, or something else graphical
*** '''or''' a combination of above
+
** '''or''' a combination of above
* this can be to something directly in the paper, or indirectly from the ideas
+
* this can be a response to something in the paper, or indirectly from the ideas in CA/paper/life/universe/everything
  
  
 
=== Specification (part 2 of 2): ChucKu's ===
 
=== Specification (part 2 of 2): ChucKu's ===
* construct two chucku's, according to the following specifications
+
* construct two chucku's, according to the following specifications:
** like a [http://en.wikipedia.org/wiki/Haiku haiku], a ''chucku'' should contain exactly 3 lines of code
+
** like a [http://en.wikipedia.org/wiki/Haiku haiku], a ''chucku'' should contain exactly 3 lines of code (each less than 80 characters)
 
** each chucku should generate sound
 
** each chucku should generate sound
 
** 5/7/5 pattern optional, but try to make the code "pretty"
 
** 5/7/5 pattern optional, but try to make the code "pretty"
Line 24: Line 26:
 
** the chucku's should be standalone (i.e., no external audio or chuck files)
 
** the chucku's should be standalone (i.e., no external audio or chuck files)
 
** (thanks to Chris + kijjaz for the idea)
 
** (thanks to Chris + kijjaz for the idea)
 +
 +
 +
=== Note ===
 +
* Have fun with it!!!
  
  
Line 32: Line 38:
 
* 1) your responses to the reading, as .ck or .txt or .jpg files
 
* 1) your responses to the reading, as .ck or .txt or .jpg files
 
* 2) a separate .ck file for each chucku
 
* 2) a separate .ck file for each chucku
* 3) an audio recording of one or more of the programs (hw0.wav)
+
* 3) an audio recording of one or more of the programs (hw0.wav) - '''UPDATE:''' do not worry about the homework factory for this assignment: just have the files in the right places.
 
* 4) a short README text ('''readme.txt''') file that:
 
* 4) a short README text ('''readme.txt''') file that:
** explains your ideas in constructing each program
+
** conveys your ideas/comments in constructing each program  
 
** contains instructions on running your programs
 
** contains instructions on running your programs
** any comments about each program / musical statement
+
** describes any difficulties you encountered in the process
** describe any difficulties you encountered in the process
+
 
+
 
+
Thanks!!!
+

Latest revision as of 12:20, 6 January 2009

Homework #0: Computational (An)aesthetics

Due date: 2009.1.16 11:59:59pm (or thereabout), Wednesday.

Reading

  • first, read/peruse CA article and this paper
    • no need to worry about the details for now, it's more important to get a sense of the ideas of cellular automata and the paper
    • in fact, try spending no more than 30 minutes total on the wikipedia article and paper combined


Specification (part 1 of 2): Response

  • respond to the reading assignment in one of the following ways:
    • either a chuck program (of any length) that makes sound
    • or a brief written/textual response (can be as short as a paragraph, or as long as uh two paragraphs, or more)
    • or a drawing / image, or something else graphical
    • or a combination of above
  • this can be a response to something in the paper, or indirectly from the ideas in CA/paper/life/universe/everything


Specification (part 2 of 2): ChucKu's

  • construct two chucku's, according to the following specifications:
    • like a haiku, a chucku should contain exactly 3 lines of code (each less than 80 characters)
    • each chucku should generate sound
    • 5/7/5 pattern optional, but try to make the code "pretty"
    • check out one line chuck crazy to see similarly compact examples
    • the chucku's should be standalone (i.e., no external audio or chuck files)
    • (thanks to Chris + kijjaz for the idea)


Note

  • Have fun with it!!!


Deliverables

turn in all files by putting them in your Library/Web/220b/hw0/ directory.

  • 1) your responses to the reading, as .ck or .txt or .jpg files
  • 2) a separate .ck file for each chucku
  • 3) an audio recording of one or more of the programs (hw0.wav) - UPDATE: do not worry about the homework factory for this assignment: just have the files in the right places.
  • 4) a short README text (readme.txt) file that:
    • conveys your ideas/comments in constructing each program
    • contains instructions on running your programs
    • describes any difficulties you encountered in the process