Thursday, November 21, 2013

18.1 and 18.2, due november 26

i was a little confused by the parity check and two-dimensional parity code examples. i guess i am confused because parity means positive or negative, but i can’t see how that applies to either example. i felt like those examples were making sure the message was odd or even so that it would be easy to detect an error. maybe there’s another meaning of parity there that i’m not getting. that was a little confusing for me. i think i followed everything else pretty well though.

the error correcting codes were super interesting to me. it was cool to think about how we can change a vector into a codeword by changing the fewest places possible and that will allow us to detect errors. so far we have just learned about different encrypting methods, but we haven’t focused on how to protect against or anticipate errors in the coding. i think that’s an important thing to consider and i haven’t even thought about that.

No comments:

Post a Comment