(no subject)
Jan. 17th, 2007 04:51 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Matlab is similar in many ways to IDL, which I used extensively as an undergraduate. Most SSX analysis codes, at least in recent memory, tended to be written in IDL because of its capacity for image manipulation, and largely because IDL was the language taught in the Physics 50 numerical methods/programming lab. I wonder what will happen now that John Boccio has switched to teaching Matlab in Physics 50.
Anyway, it appears that one of the bigger things I need to remember about Matlab vs. IDL is that if you enter a command in interactive mode without suppresing the output with a semicolon at the end of the line, Matlab automatically prints the entire contents of the output to screen. This is bad when you're working with files that are 1024x1280 images (or rather, arrays of pixel values) and failing to include the semicolon results in rows upon rows of seemingly meaningless numbers drowning out the display.
Anyway, it appears that one of the bigger things I need to remember about Matlab vs. IDL is that if you enter a command in interactive mode without suppresing the output with a semicolon at the end of the line, Matlab automatically prints the entire contents of the output to screen. This is bad when you're working with files that are 1024x1280 images (or rather, arrays of pixel values) and failing to include the semicolon results in rows upon rows of seemingly meaningless numbers drowning out the display.