{"id":4004,"date":"2025-10-14T06:11:12","date_gmt":"2025-10-14T10:11:12","guid":{"rendered":"https:\/\/blogs.mathworks.com\/matlab\/?p=4004"},"modified":"2025-10-14T06:11:12","modified_gmt":"2025-10-14T10:11:12","slug":"stop-using-r-to-run-matlab-in-batch-jobs","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/matlab\/2025\/10\/14\/stop-using-r-to-run-matlab-in-batch-jobs\/","title":{"rendered":"Stop using -r to run MATLAB in batch jobs"},"content":{"rendered":"
You have a script, let's call it <\/span>myscript.m<\/span>, and you want to run it non-interactively, or as a 'batch-job'. If you are still doing something like this<\/span><\/div>
matlab -nodisplay -nosplash -nodesktop -r \"myscript;exit\"<\/span><\/span><\/div><\/div>
or<\/span><\/div>
matlab -nodisplay -nosplash -nodesktop -r \"run('myscript.m');exit\"<\/span><\/span><\/div><\/div>
then stop! Since R2019a, MATLAB has had a <\/span>-batch<\/span> command line switch and we now recommend that you do the following instead<\/span><\/div>
matlab -nodisplay -batch myscript<\/span><\/span><\/div><\/div>
If nothing else, the newer syntax looks a lot cleaner and involves less typing. However, let's dig into some additional reasons why you should prefer the newer method. <\/span><\/div>

-batch is less noisy at the beginning<\/span><\/h2>
Lets say that <\/span>myscript.m<\/span> just contains the following<\/span><\/div>
% Contents of myscript.m<\/span><\/span><\/div><\/div>
fprintf(<\/span>\"Hello from MATLAB\\n\"<\/span>)<\/span><\/span><\/div><\/div><\/div>
Running this the old way is rather noisy! <\/span><\/div>
matlab -nodisplay -nosplash -nodesktop -r \"myscript;exit\"<\/span><\/span><\/div>
 <\/div>
 <\/div>
< M A T L A B (R) ><\/span><\/span><\/div>
Copyright 1984-2025 The MathWorks, Inc.<\/span><\/span><\/div>
R2025b (25.2.0.2998904) 64-bit (maca64)<\/span><\/span><\/div>
August 21, 2025<\/span><\/span><\/div>
 <\/div>
<\/span><\/span><\/div>
To get started, type doc.<\/span><\/span><\/div>
For product information, visit www.mathworks.com.<\/span><\/span><\/div>
<\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div><\/div>
Batch mode gets right to the point<\/span><\/div>
matlab -nodisplay -batch myscript <\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div><\/div>

-batch doesn't need an explicit exit<\/span><\/h2>
Anyone who has ever used the old way will have, at some point, forgotten to add 'exit' to the end of the command<\/span><\/div>
matlab -nodisplay -nosplash -nodesktop -r \"myscript\"<\/span><\/span><\/div>
 <\/div>
< M A T L A B (R) ><\/span><\/span><\/div>
Copyright 1984-2025 The MathWorks, Inc.<\/span><\/span><\/div>
R2025b (25.2.0.2998904) 64-bit (maca64)<\/span><\/span><\/div>
August 21, 2025<\/span><\/span><\/div>
 <\/div>
<\/span><\/span><\/div>
To get started, type doc.<\/span><\/span><\/div>
For product information, visit www.mathworks.com.<\/span><\/span><\/div>
<\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
>> <\/span><\/span><\/div><\/div>
MATLAB enters its terminal mode, runs your command and then sits there, waiting for you to type more commands. If you are sat at an interactive terminal and this happens, you shake you head at your forgetfulness, type <\/span>exit<\/span> and move on with your life. <\/span><\/div>
If you do this in a non-interactive setting such as on a High Performance Computing (HPC) cluster or in a CI\/CD environment, the job will sit there doing nothing until it is (hopefully!) terminated by the scheduler or a timeout.<\/span><\/div>
When you use <\/span>-batch,<\/span> MATLAB will always exit when it has completed your script. <\/span><\/div>

-batch exits on error<\/span><\/h2>
Inevitably, our code will sometimes exit with an error. Let's force the point with a new script: <\/span>myBadScript.m<\/span><\/div>
% Contents of myBadScript.m<\/span><\/span><\/div><\/div>
fprintf(<\/span>\"Hello from MATLAB\\n\"<\/span>)<\/span><\/span><\/div><\/div>
error(<\/span>\"Something has gone very wrong\"<\/span>)<\/span><\/span><\/div><\/div><\/div>
If we run this the old way, things don't go the way we'd like them to<\/span><\/div>
matlab -nodisplay -nosplash -nodesktop -r \"myBadScript;exit\"<\/span><\/span><\/div>
 <\/div>
< M A T L A B (R) ><\/span><\/span><\/div>
Copyright 1984-2025 The MathWorks, Inc.<\/span><\/span><\/div>
R2025b (25.2.0.2998904) 64-bit (maca64)<\/span><\/span><\/div>
August 21, 2025<\/span><\/span><\/div>
 <\/div>
<\/span><\/span><\/div>
To get started, type doc.<\/span><\/span><\/div>
For product information, visit www.mathworks.com.<\/span><\/span><\/div>
<\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
Error using myBadScript (line 3)<\/span><\/span><\/div>
Something has gone very wrong<\/span><\/span><\/div>
<\/span><\/span><\/div>
>> <\/span><\/span><\/div>
 <\/div><\/div>
MATLAB stops at the error so the <\/span>exit<\/span> command is never reached and we are stuck with the same problem we had when we forgot the <\/span>exit<\/span> command: MATLAB just sits there waiting for input. <\/span><\/div>
If we use <\/span>-batch<\/span>, MATLAB terminates gracefully after the error message<\/span><\/div>
matlab -nodisplay -batch myBadScript<\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
Error using myBadScript (line 3)<\/span><\/span><\/div>
Something has gone very wrong<\/span><\/span><\/div><\/div>
When you use <\/span>-batch<\/span>, the process also terminates with a non-zero error code if your script exits with an error. For example, on Linux or Mac we can query the shell variable <\/span>$?<\/span> to display the error code returned by the previous command.<\/span><\/div>
matlab -batch myscript <\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
 <\/div>
echo $?<\/span><\/span><\/div>
0<\/span><\/span><\/div>
 <\/div>
matlab -batch myBadScript<\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
Error using myBadScript (line 3)<\/span><\/span><\/div>
Something has gone very wrong<\/span><\/span><\/div>
<\/span><\/span><\/div>
echo $? <\/span><\/span><\/div>
1<\/span><\/span><\/div><\/div>

You can use batchStartupOptionUsed to infer you're running with -batch<\/span><\/h2>
Sometimes we want our script to behave one way if it is run interactively and another way if it is running in batch. With <\/span>-batch<\/span> there is a straightforward way of doing this via the <\/span>batchStartupOptionUsed<\/span><\/a> flag. Let's change <\/span>myscript.m<\/span> to the following<\/span><\/div>
% Contents of myscript.m<\/span><\/span><\/div><\/div>
fprintf(<\/span>\"Hello from MATLAB\\n\"<\/span>)<\/span><\/span><\/div><\/div>
if <\/span>batchStartupOptionUsed<\/span><\/span><\/div><\/div>
fprintf(<\/span>\"I am running in batch mode\\n\"<\/span>)<\/span><\/span><\/div><\/div>
else<\/span><\/span><\/div><\/div>
fprintf(<\/span>\"I think I'm running interactively\\n\"<\/span>)<\/span><\/span><\/div><\/div>
end<\/span><\/span><\/div><\/div><\/div>
Run this the old way and <\/span>batchStartupOptionUsed<\/span> is false<\/span><\/div>
matlab -nodisplay -nosplash -nodesktop -r \"myscript;exit\"<\/span><\/span><\/div>
 <\/div>
< M A T L A B (R) ><\/span><\/span><\/div>
Copyright 1984-2025 The MathWorks, Inc.<\/span><\/span><\/div>
R2025b (25.2.0.2998904) 64-bit (maca64)<\/span><\/span><\/div>
August 21, 2025<\/span><\/span><\/div>
 <\/div>
<\/span><\/span><\/div>
To get started, type doc.<\/span><\/span><\/div>
For product information, visit www.mathworks.com.<\/span><\/span><\/div>
<\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
I think I'm running interactively<\/span><\/span><\/div><\/div>
I am sure that there are ways to infer exactly how you've started MATLAB and to behave appropriately even using the old way of doing this but <\/span>batchStartupOptionUsed <\/span>is just easy and clean. <\/span><\/div>
matlab -nodisplay -batch myscript <\/span><\/span><\/div>
Hello from MATLAB<\/span><\/span><\/div>
I am running in batch mode<\/span><\/span><\/div><\/div>

-batch disables toolbox caching and changes to settings<\/span><\/h2>
Toolbox caching is normally used to speed up access to toolbox functions. Sounds like faster toolbox functions is a good thing so why is <\/span>-batch<\/span> disabling it? This is to ensure that there are no inconsistencies between runs. Caching is user specific and persistent but batch runs are meant to be ephemeral and isolated. Furthermore, Continuous Integration (CI) jobs always run in clean environments so caching wouldn't persist between sessions anyway.<\/span><\/div>
Similar thinking applies to <\/span>settings<\/span><\/a>. We want to ensure that batch jobs run in a predictable environment, unaffected by user-specific sessions.<\/span><\/div>

-batch could be faster<\/span><\/h2>
I wondered if -<\/span>batch<\/span> would be faster and although, in theory, it could be; it's not the case yet. As of R2025b, there isn't any compelling speed difference between <\/span>-batch<\/span> and the older way of doing things. This may change in the future, however, since <\/span>-batch<\/span> mode offers the possibility of not needing to load various things. <\/span><\/div>

So, use -batch for running batch jobs<\/span><\/h2>
It's a lot easier to remember than all the other switches you perhaps used to use.<\/span><\/div>

<\/span><\/h2>
<\/span><\/div>
<\/div>\r\n<\/div>