hw14 - % % Name : <Michael Butler> % GT Email :...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Name : <Michael Butler> % GT Email : <mbutler31@gatech.edu> % Homework : hw14 % Course : CS1371 % Instructor : Marsicano, Smith % Lecture Time : MWF <2:35> % TA's Name : <Emilio Salazar> % Section : <C03> % Collaboration: < "I worked on this homework with Melanie Ostis, using % only course materials."> % % % % Files provided with this homework: % - hw14.m % - C4.wav % - fft.pdf % - chord1.wav % - chord2.wav % - Piano Notes.jpg % - electric_guitar.jpg % - electric_guitar.wav % - homer.jpg % - homer.wav % - C5.wav % - D4.wav % - ABCs_sound.m % - ABCs_hw14_pretest.p % % Files to submit: % - hw14.m % - ABCs_sound.m % - chordGen.m % - parseInput.m % - soundPlot.m % - transposeSound.m % - playSong.m % % Instructions: % 1) Follow the directions for each problem very carefully or you will % lose points. % 2) Make sure you name functions exactly as described in the problems or % you will not receive credit. % 3) Read the announcements! Any clarifications and/or updates will be % announced on T-Square. Check the T-Square announcements at least once % a day. % 4) You should not use any of the following functions in any file that % you submit to T-Square: % a) clear % b) clc % c) solve % d) input % e) disp % f) close all % g) sound % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
% %========================================================================== % BE COURTEOUS TO OTHERS %-------------------------------------------------------------------------- % % This homework deals with sound. Sound can be a fun topic but it can also % be annoying for those around you. While you are working on this homework % please be courteous of others; turn down the volume on your computer or % wear headphones, especially if you come to help desk for help. % %========================================================================== % COMMENTING %-------------------------------------------------------------------------- % % Whenever you program, it is always a good idea to comment your code. % Commenting helps you keep track of what you are attempting to code, and % it helps others in understanding why you wrote various lines of code. % Since the AutoGrader does not give partial credit for attempting a % problem, we have added a commenting system to give some incentive to at % least attempt each problem. From now on, when you write a solution to a % problem, you should comment your code and explain what you were % attempting to code. Some good places to comment would be sections of your % code that directly relate with your algorithm. However, don't comment % every line of code. Instead comment the lines of code that are either % difficult to understand or are important to solving the problem. % % Commenting will purely be for extra-credit purposes, so if you don't want
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/21/2010 for the course CS 1371 taught by Professor Stallworth during the Spring '08 term at Georgia Institute of Technology.

Page1 / 7

hw14 - % % Name : &lt;Michael Butler&gt; % GT Email :...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online