I remember in the days of modems we used to use a 511 bit pseudo-random error pattern to test data links. If you listened to it on the line, it was a surprisingly repetetive sound compared to real random data. So I can see how you'd "hear" patterns in data this way.
While I agree that we are able to see patterns and automatically expand, rescale, and focus on anomolies with our eyes, I don't beleive the same is true with our ears. They are much more 2d(or arguably, 1d) and are thus easily outdone by relatively unsophisticated algorithms.
old-time computer folks used to debug with an AM radio next to their system. Back in those days, clocks used to be in the hundreds of kilohertz, and you could hear the program flow (loops, jumps, interrupts) in the buzz on the corresponding AM frequency.
Good comment przemek. And folks still use the AM radio technique. Put it near the AC service panel of a house and see (hear) if any x10, etc. devices are wired somewhere and perhaps therefore interfering with some other system. Turn off individual breakers to isolate and find.
I used to work in radiopaging sending digital data packets and during development would often say or hear "there was something wrong with that packet". We were rarely, if ever, wrong.
Most people who use(d) modems will have had a "that didn't sound right" moment.
Very much so, I used to deal with multisite modems on a polling system and got to know when there was something wrong on the line by the sounds. For instance, you could teell how many sites were responding, or if one was retransmitting a lot.
While Selinz may be sceptical, just as your eyes will register small changes in what you see, so the ear can distinguish small changes or patterns in modulated data. I can see how that could be used to find patterns or other irregularities in data - it would only give you a starting point for further investigation but you could get through a lot of data quickly.
Power supply designers use touch all the time to tell if things are running hot. Low voltage circuits, of course. And sight, smell, and hearing give a quick indication that an electrolytic is in backwards. Or, what is left of it was in backwards. If something is hot, we can often tell by the smell if it's a semiconductor or a resistor.
Evaluating data by sound , smell, or touch is indeed a very good method, particularly when the required results are qualitative, such as "good or bad". But it calls for skilled personal judgement and so it would not be found acceptable by that segment of managers who strongly want to eliminate the need for such skills in the name of uniformity. Think ISO9000 and similar policies.
But listening is still a very handy way to detect problems, beyond any doubt.
Agreed, by ISO9000, and even good solid logic, measurements must be done by instumentation. But a first cut, fire it up, qualitative run can use all the senses. And when something goes wrong, a good nose or ear is often the first indication. On a power supply, the first indication of a failure is sometimes that loud popping sound, flash of light, and acrid smell. Of course, if that's the case, the fact that the product no longer works makes it obvious.
Blog Doing Math in FPGAs Tom Burke 12 comments For a recent project, I explored doing "real" (that is, non-integer) math on a Spartan 3 FPGA. FPGAs, by their nature, do integer math. That is, there's no floating-point ...