*: *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 file system 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 bring MATLAB along yourself, you would need to package it up, bring it along (specified with =transfer_input_files= in the submit description file), 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: MATLAB Compilation}
-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.
+To compile =foo.m= with the MATLAB Compiler, you would use a command like the following. The various options are explained further below; =-R= 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}
@@ -85,14 +86,14 @@
{section: Invoking}
-Matlab may try to create a graphical environment. Condor does not support graphical environments; it doesn't make sense to open up a user interface for a job that won't have a user directly looking at it. You may need some combination of -nosplash, -nodisplay, and possibly -nojvm to stop Matlab from creating a graphical environment. This should not be necessary for Matlab Compiler compiled jobs.
+MATLAB may try to create a graphical environment. Condor does not support graphical environments; it does not make sense to open up a user interface for a job that will not have a user directly looking at it. You may need some combination of =-nosplash=, =-nodisplay=, and possibly =-nojvm= to stop MATLAB from creating a graphical environment. This should not be necessary for compiled MATLAB Condor jobs.
-Unless you have special arrangements to use multiple CPU cores, you will want -singleCompThread so that Matlab only uses a single core.
+Unless you have special arrangements to use multiple CPU cores, you will want =-singleCompThread= so that MATLAB only uses a single core.
-|-nosplash | Disable splash screen. (No GUI support in Condor)|
-|-nodisplay | Disable GUI. (No GUI support in Condor)|
-|-nojvm | Disable GUI? Eliminate unnecessary Java (faster?)|
-|-singleCompThread | Only use one CPU core (play nicely when sharing computer)|
+|=-nosplash= | Disable splash screen. (No GUI support in Condor)|
+|=-nodisplay= | Disable GUI. (No GUI support in Condor)|
+|=-nojvm= | Disable GUI? Eliminate unnecessary Java (faster?)|
+|=-singleCompThread= | Only use one CPU core (play nicely when sharing computer)|
