{section: Executables}
-The MATLAB executable and supporting libraries must be made available on any computers on which the Condor jobs might run. Accomplish this by one of
-1: install MATLAB on each computer that may run a MATLAB Condor job
-2: install MATLAB on a shared file system, such that it is accessible by each computer that may run a MATLAB Condor job
-3: transfer the MATLAB executable (and supporting libraries) along with the Condor job
+The MATLAB executable and supporting libraries must be made available on any computers on which the Condor jobs might run.
+When using the MATLAB Compiler, instead of the full MATLAB executable and supporting libraries, the MCR is needed. The general techniques for making the MCR available are the same.
+Accomplish this by one of
-When using the MATLAB Compiler, instead of the full MATLAB executable and supporting libraries, the MCR is needed. The general techniques for making it available are the same as given above.
+*: *Install MATLAB on each computer that may run a MATLAB Condor job.*
-To compile "foo.m" with the MATLAB Compiler, you would use a command like the following. The various options are explained further below; -R simply tells Matlab to behave as though the next option was passed in when the job is started.
-{code}
-mcc -m -R -singleCompThread -R -nodisplay -R -nojvm -nocache foo.m
-{endcode}
-
-If you install Matlab locally on each computer, it is recommended to place Matlab in the same location on each computer. That way individual jobs can easily find it. If Matlab will be in different locations on each computer, you can set up {link:http://www.cs.wisc.edu/condor/manual/v7.6/3_3Configuration.html#param:SubsysAttrs STARTD_ATTRS} to advertise the correct location, then the job can use a {link:http://www.cs.wisc.edu/condor/manual/v7.6/condor_submit.html#73792 $$} expression to find it. For example, your configuration file might say:
+_:If you install Matlab locally on each computer, it is recommended to place Matlab in the same location on each computer. That way individual jobs can easily find it. If Matlab will be in different locations on each computer, you can set up {link:http://www.cs.wisc.edu/condor/manual/v7.6/3_3Configuration.html#param:SubsysAttrs STARTD_ATTRS} to advertise the correct location, then the job can use a {link:http://www.cs.wisc.edu/condor/manual/v7.6/condor_submit.html#73792 $$} expression to find it. For example, your configuration file might say:
{code}
MATLAB_PATH = /opt/matlab/bin
STARTD_ATTRS = MATLAB_PATH
{endcode}
-A user might specify in their submit file (simplified):
+_:A user might specify in their submit file (simplified):
{code}
executable = my_task
@@ -47,18 +41,30 @@
queue
{endcode}
-my_task would then be a script that did something like this:
+_:my_task would then be a script that did something like this:
{code}
#! /bin/sh
exec "$1"/matlab -nodisplay ./my_task.m
{endcode}
-Similar scripts would work on Windows.
+_:Similar scripts would work on Windows.
+
+*: *Install MATLAB on a shared file system, such that it is accessible by each computer that may run a MATLAB Condor job.*
+
+_:Installing on a shared filesystem is identical to installing it on each local computer, but may be less complicated for administration.
+
-Installing on a shared filesystem is identical to installing it on each local computer, but may be less complicated for administration.
+*: *transfer the MATLAB executable (and supporting libraries) along with the Condor job.*
+
+_:To bring Matlab along yourself, you would need to package it up, bring it along (transfer_input_files), then have a script unpack Matlab and start it. Matlab is a large piece of software, and this could be slow. It will also temporarily use a bunch of disk space with a copy of Matlab. If multiple Matlab jobs run on the same computer simultaneously, multiple copies of Matlab will be installed at once. Generally speaking this is not recommended, although it is more practical for the MCR.
+
+
+To compile "foo.m" with the MATLAB Compiler, you would use a command like the following. The various options are explained further below; -R simply tells Matlab to behave as though the next option was passed in when the job is started.
+{code}
+mcc -m -R -singleCompThread -R -nodisplay -R -nojvm -nocache foo.m
+{endcode}
-To bring Matlab along yourself, you would need to package it up, bring it along (transfer_input_files), then have a script unpack Matlab and start it. Matlab is a large piece of software, and this could be slow. It will also temporarily use a bunch of disk space with a copy of Matlab. If multiple Matlab jobs run on the same computer simultaneously, multiple copies of Matlab will be installed at once. Generally speaking this is not recommended, although it is more practical for the MCR.
{section: Invoking}
