As I need to call Matlab scripts from the command, e. g., for running Matlab scripts in a batch, every once in a while, I post a little reminder for my self here. Keep in mind that the called Matlab command needs to have an exit at the end, otherwise Matlab will keep running, waiting for input.

This is a follow up post of a previous one just using Matlab instead of Python. In the following paragraphs, I will show my way of reading and writing CSV files using Matlab. If you happen to know a better or more elegant solution, please drop a comment!

After I had to upgrade the X11 support on OS X 10.8 (Mountain Lion), I got an annoying dialog asking for some strange application called OroborOSX every time I wanted to start Matlab. After a quick look into the launch script, I found a solution and it seems to be aligned with Mathworks - the company behind Matlab.

Just want to note, that the previous post about solving Matlab crashes whenever a figure or plot command is called after a Mac OS X Java update has an update by Mathworks itself. Check this link and learn how to solve the problem also for older Mac OS X versions!

Cheers, iss

After Apple’s Java Update that came with Mac OS X 10.6.8, Matlab (R2008 and older) crashes whenever a figure or plot is opened. According to Matlab Central, you can fix the problem with the correct DYLD_LIBRARY_PATH during Matlab launch.

I know it’s almost common sense, but today I had to refix the slow GUI for Matlab yet another time. As the information seems to start vanishing from the web, I want to perpetuate it here.

Go into directory /Applications/MATLAB_R2007b/bin/maci (or wherever your installation resides) and create a file called java.opts with the following content.

-Dapple.awt.graphics.UseQuartz=true

Cheers,
iss

As I am doing some of my evaluations in Matlab, I was curious if I can emulate the behaviour of unsigned int, unsigned short C-variables in Matlab. However, they behave quite different! If you have a uint16 variable, which has the value 65 535 (the maximum it can take) and increment it, it remains at 65 535. No wrap around :/

I recently had to make a Matlab™ subplot and wanted to link the axes of the two plots together, so that both graphs show the same range on their x-axis. Of course, there is a simple command for this in Matlab™: linkaxes. Detailed information about the command can be found on the Web-Documentation. The following code shows, how I did it in my script.

Some days ago, I needed to write an m-file (Matlab™ Function File), which had to run under Octave as well. If you use full Octave compliant stuff, this works quite easily without modification of your code. But if you use e. g. subplot(…) with a range to make one plot broader or wider, Octave resigns. Therefore, I put in the following statement and wrote this blog message as a reminder :)