Change Contents of the Bubble
Welcome to CS1315. Click on the python to add comments.

Looking for the book? They have it at the Engineer's Bookstore at 748 Marietta St NW. Here is there website: http://www.engrbookstore.com/ - Monica

Hotspots: Slides and Code • TA Corner • Comments? • Announcements • FAQ • Static Webspace
View this PageEdit this Page (locked)Uploads to this PageHistory of this PageHomeRecent ChangesSearchHelp Guide

First Edition Errors

In the "making it work tip" on page 30, the word "along" should be separated into "a long." Suzannah Gill
Check – thanks, Suzannah! Mark Guzdial
On page 10, last paragraph on the page, The sentence beginning with, "Sure, it knows how to compare numbers..." should have a question mark at the end instead of a backslash. Also, on page 28, The last sentence in the paragraph beginning with "We can assign names..." refers to an unlisted section ("which comes up in Section??"). Karin Bowman
Oops! Both of those are errors that arise in the kind of typesetting tool I'm using (LaTeX). Thanks, Karin! Mark Guzdial
Page 54 CH 3
Last sentance of page...The colon is imp...(you should recall reading...in Section ?? on ??)
LAB 2
error of missing colon on the editited 2nd example1, with the r, for windows users
Mireille Murad
Thanks, Mireille! Check! Mark Guzdial
P. 44–"(0,0,0)...is black, and (0,0,0) is white. Should white be (255,255,255)? Jennifer Blake
That one's embarassing :-) Thanks, Jennifer! Mark Guzdial
On page 41 there are two errors. The first one is in the first full paragraph on the page. The opening sentence is, "You can get a similar individual using the JES...." Is there supposed to be a word between "individual" and "using?" The second mistake is in the third paragraph. The sentence is, "The lack of human vision what makes it possible to digitize..." I think that the word "is" needs to go between "vision" and "what." Baillie Homire
Must've been sleepy on that page – thanks, Baillie! Mark Guzdial
on page 10, I think the value for the binary numbers should be 82, not 74 as it is written. (It depends on how you read it; I read it as 82, but if you assume the least significant bit is at the top, then it's 74. So, the error is not identifying which end is "big" and which end is "little". Blair MacIntyre)
Barb made a nice new figure that we'll put in there to spell it all out. Thanks! Mark Guzdial
Page 47, it says you can compare colors using "<" and ">", but these operations are not properly defined in JES, so you shouldn't do this. Blair MacIntyre
Agreed – it's not clear what < and > mean with colors. Thank you! Mark Guzdial
Page 49 near the bottom, the results for makeLighter should have changed Michael Shaw
Right – I wonder what I did there? I'll fix it. Thanks! Mark Guzdial
Page 50, 2nd Common Bugs box, should it be: >>>writePictureTo(picture,"newpicture.jpg") instead of ...(sound,"newpi...? Michael Shaw
Yeah, that would make sense, wouldn't it? Thanks again, Michael! Mark Guzdial
On page 44, it says "(50,50,50) would be a fairly light grey, and (100,100,100) is darker" which I think it is a wrong statement and we have to changeit to:
"(100,100,100) would be a fairly light grey, and (50,50,50) is darker".
Maryam Doroudi
(sigh) You're right – thanks for catching it, Maryam! Mark Guzdial
p.47(end of page): You can also ask a pixel for its color with getColor, and you can also set the color with setColor.
This sounds...simple. How about "You can also ask a pixel for its color with getColor, just as you can set the color with setColor."
Catherine Billiris
Nicer – thank you, Catherine! Mark Guzdial
On page 26 2nd paragraph from bottom, last sentence. Book says "We call our names for data "VARAIBLES" There is a transposition there with the "i" and "a," and should be "varIAbles.
"Jonathan Longhitano"
Even in italics! It even shows up in the Index because of that mistake. Thanks, Jonathan. Mark Guzdial
On page 24, 5th paragrah down (right before sec 2.4.1), 3rd sentence, the one in parantheses says, "...they contain data that IS can be interpreted to be a representation of a picture..." It seems the "is" between "that" and "can" should not be there.
Jonathan Longhitano
Agreed – thanks again, Jonathan! Mark Guzdial
Hope I am not being annoying, but on page 30, last paragraph, 4th sentence (the one in parantheses). It says, "In JES, you could USE ALSO USE one tab...." The first "use" should not be there.
Jonathan Longhitano
What? Don't you often use also use? :-) Good catch, Jonathan – thanks! Mark Guzdial
On page 37, first sentence under the "To Dig Deepere" paragraph, it says, "The best (deepest, most material, most elegance) computer science textbook..." Should it not be "...(deepest, most material, most "ELEGANT") computer science textbook..."
Jonathan Longhitano Can u tell I am reading the book right now?
Can you tell that I didn't read the book carefully enough? :-) Thanks! Got it in my notes. Mark Guzdial
On page 41, 3rd paragraph, 5th sentence, it says, "We can actually pick up luminance detail better with the sides of our eyes better than the center of our eye." Most will get the point of what you are trying to say, but it does not flow well, and that second "better" really does not belong there. I think it sounds better if you say, "Luminance detail is actually better at the sides of our eyes than it is at the center."
Jonathan Longhitano
I'll rewrite – thanks! Mark Guzdial
Also on page 41, very last sentence on the page, it says "Visible light in continuous." Should it be "Visible light IS continuous."
Jonathan Longhitano
Some people are such sticklers for verbs...:-) Thanks! Mark Guzdial
Sometimes you use gray and sometimes grey.
Barbara Ericson
I'll change them all to "gray" – thanks! Mark Guzdial

pg 75, recipe 21...should there be a space in "for yOffset in range (1, mirrorpoint):" between the "y" and the "o" in "offset"? Karin Bowman
No, there shouldn't be. yOffset is a variable name, and there can't be any spaces in variable names. They must be all one word. Mark Guzdial

pg 64 2nd paragraph, 2nd sentence. We want our functions to one and only one thing, I guess "do" was left out?
Check – thank you! Mark Guzdial

pg 146–2 raised to the fifteenth power appears as 2 to the first times 5
My poor use of LaTeX – thanks!
–3rd full paragraph, last sentence should say "it sounds bad" not "it sound bad"
Check! Thanks! Mark Guzdial
pg150–2nd paragraph, first sentence, "samples" should not be plural
Did you mean the word "examples"? The word "samples" I think is right there.
pg151–next to last paragraph from the bottom, your third sentence just cuts off in mid-word
Check – thanks! Mark Guzdial
Maybe a section containing the most common error messages and their explanations should be included so that the person can figure out for himself what could be wrong.
I actually have a start on that – see "errors" in the index. But that's one of the things that I need to beef up: Tables of information in the book. Thanks! Mark Guzdial

Upon your request, here are some possible errors I have found, on page 42, third sentence, it says, "Our brain determines WHAT A PARTICULAR COLOR BASED ON THE FEEDBACK...." I think there should be a "is" between "color" and "based." Jonathan Longhitano

On page 52, the second bulletpoint. It says, "The x and y position will be DISPLAY for the pixel you're POINT at." I think it should be "The x and y position will be displayED for the pixel you're pointING at." Jonathan Longhitano
On page 54, second sentence after the code on top. It says, "What we need IS WAY of telling the computer to do the...." I think it should be "What we need is A way of telling the computer to do the..." Jonathan Longhitano
On page 57, sentence right under the tracing the program box. It says, "Let's trace the function to INCREASE red and see how it worked." I think it should be "Let's trace the function to DECREASE red and see how it worked. I assume it is "decrease" because the whole page is talkinga about decreaseRed and the next page as well. Jonathan Longhitano
On page 59, at the very bottom of the page, where it says "We get the value of that pixel's red channel." Okay on top of that where the boxes are that are displaying the pixel color values. It says, value=168. Should that be value=160, because we are now talking about the the next pixel correct? According to the box it says value=160 for the next pixel, 168 was for the first pixel. Because then on the next page it then shows the new value of 80, which would be half 160. Jonathan Longhitano
I'm going through these one at a time and putting them into my notes. Thanks, Jonathan! This one is actually a matter of timing. Until we actually set value=getRed(p), value doesn't change. Thus, p changes BEFORE value. I need to make clearer at what point I imagine each text and picture appearing. Mark Guzdial
On page 65, the second paragraph, 8th sentence. It says, "Or would you rather make a LOOK to go through each of the frames..." It should be "...make a LOOP to go through each of the frames..." correct? Jonathan Longhitano
On page 67, the middle of the page, right on top of the second piece of code on the page for decreaseRed. It says, "We can pass in more THAN INPUT at a time." I think it should be, "We can pass in more than ONE input at a time." Jonthan Longhitano
On page 73, where we are walking through the program. On step 3 it says, "for y in range(1,getHeight(picture):" There is a closing parenthese missing after picture. Jonathan Longhitano
On page 76, the caption for Figure 3.24. Shouldn't it be reversed? That is the first picture(left) is Santa being mirrored horizontally from top to bottom, and for the second picture(right) he is mirrored bottom to top? The way it is written in the book is reversed. Jonathan Longhitano
On page 79, first sentence under Copying and Transforming Pictures. It says, "We can create wholly new pictures WHEN COPY pixels across pictures." There should be a "we" between "when" and "copy." Jonathan Longhitano
pg 170, recipe 56 names a "guzdialsound" and an "issound". For the sake of consistency, maybe make the names "guzdialSound" and "isSound" (in other examples, the second word starts with a capital letter). Nothing big, just a suggestion.
Near the bottom of page 171 after talking about target indexes, it says, "xxx Would some example pixtures help?". I'm guessing it's a note-to-self. Karin Bowman
Thank you for all of these, Jonathan! Yes, Karin, looks like I left in a note that should've disappeared. Thanks! Mark Guzdial

p. 140 first line, "different" should be "difference"

p. 140 2nd bullet in list, 2nd sentence "target volume and amplitude" should be "target frequency and amplitude"- I'm assuming you want a parallel comparison between instruments Michael Shaw
Thanks, Michael, for both. Mark Guzdial
On the CD, Folder "Speech" is missing. Adam Wilson
on page 11, encyclopedia is spelled wrong.
Are you sure? I meant multiple encyclopediae, and my Latin suggests that that's the right spelling – alumna, alumnae. I'll check dictionary.com... Mark Guzdial

I had to hunt all over for this one, but you are right! It's encyclopedias! See http://encyclopedia.thefreedictionary.com/Grammatical%20number Mark Guzdial

Got some more errors for you. On page 138, first sentence second paragraph. It says, "When we percIEVe..." It should be PercEIve. Jonathan Longhitano
This isn't really a typo, but a structure thing. On page 140, last paragraph before the first bullet. The last sentence says, "...the factors that make different sounds (especially different instruments) different. It just seems like there are too many "differents" in there. Just a suggestion, but what about, "...the factors that make VARIOUS sounds (especially different instruments) different." Jonathan Longhitano
On page 141, first paragraph, 3rd sentence. It says, "Using the sound tools, you can actually observe sounds as they're coming IN TO your computer's..." "In To" should be one word. Jonathan Longhitano
On page 155, first paragraph underneath the bullets. It says, "s and v are not as obvious what they are naming as sample and value." Shouldn't there be an "as to" between "obvious" and "what." Jonathan Longhitano
On page 157, 2nd to last paragraph, second sentence. It says, "When we evaluate increaseVolumes." Shouldn't the "s" be in parantheses in increaseVolumes, so increaseVolume(s). Also, shouldn't the period that is after increaseVolume not be there, because the next line the, "the" is lowercase, and it seems it is part of the same sentence. Jonathan Longhitano
On page 163, last paragrpah. It says, ...-write software that is understanDBle for the people..." There should be an "a" between the "d" and b."
okay so I need to work on my HTML, I only wanted to underline "understandable" Jonathan Longhitano
On page 168, last paragraph, second sentence. It says, "It's a standard notation in mNay languages for..." Their is a transposition with the "n" and "a" in "many." Jonathan Longhitano
Why is it underlining everything I type now?
Missed the closing bracket on the start underline – fixed now. As always, THANKS, JONATHAN!! Mark Guzdial
On page 172, 6th line down. It says, "for sourceIndex in range( 33414, 0052):" That should be 40052 right? Jonathan Longhitano
On page 174, last paragraph, second sentence. It says, "We don't have to DO always go in the same order." That "do" should not be there. Jonathan Longhitano
On page 126, it says that the picture without a flash in Figure 4.9 was jungle-fied, but that only happens in figure 4.10. Maybe its just me getting confused though.... Summar Shoaib
pg 138, 6th full paragraph, sentence that begins with "All sounds..", the word "In" should be lower case and "cyle" should be cycle".
I think that words after colons should be lower case...for example, on page 212 there are two sentences with colons and words begining with uppercase letters (first paragraph). But this is something all throughout the book...are my punctuation skills incorrect?
pg 215, might just be my copy, but the code is very blurry (and only the code) and there are squares in between the words.
not just you - in my book as well
This isn't so much an error as a suggestion... A glossary would be super helpful!
p 239 Section end of recipe. i chose a very...pixel is REaD Mireille Murad
pg. 287 Middle of the page says
"JES is interpreted twice which will always be faster than Photoshop".
Shouldn't it be "SLOWER than Photoshop"?
Jonathan Laing
These are great – thanks, Jonathan, Summar, and Mireille! I'm hoping to start typing in fixes during Finals week... Mark Guzdial
My book is falling apart. That's a big book error in my book :) I like the content though.
Glad to see someone is using it! Lauren Walker
PAGE 201 Section 7.1.1 - (spelling) 'reuquirements' should be requirements
Thank you! Mark Guzdial

page 232.. "Like onions and ogres, networks have layers." WAY too corny.
on page 235, should lines 7-10 of the recipe all have # in front?

Link to this Page