HTCondorWiki: How To Run Matlab

 
 A local installation may provide additional options for parallel, usually in the form of offering a job two or more CPUs on a single computer.  Local administrators should be able to describe available functionality.
 
-Given the default configuration, it is usually better to break your work down into multiple independent jobs.  For example, if you are processing 10,000 images, instead of a single Matlab job that processes them, perhaps you could have 10,000 jobs that each process 1 image.  Condor is then able to schedule your jobs across multiple computers or at least multiple cores on a single computer, giving you the speed benefits of parallelism.
+Given the default configuration, it is usually better to break your work down into multiple independent jobs.  For example, if you are processing 10,000 images, instead of a single MATLAB job that processes them, perhaps you could have 10,000 jobs that each process 1 image.  Condor is then able to schedule your jobs across multiple computers or at least multiple cores on a single computer, giving you the speed benefits of parallelism.
 
-For older Matlab (Possibly pre 2011?), to ensure that Matlab only uses one core, put this in your Matlab script:
+For older MATLAB (Possibly pre 2011?), to ensure that MATLAB only uses one core, put this in your MATLAB script:
 
 {code}
 lastN = maxNumCompThreads(1);   (Pre r2009bsp1)
 {endcode}
 
-If you're using the Matlab Compiler, but want to use multiple threads when doing development, you could use something like this to limit Matlab to one thread only for compiled versions:
+If you are using the MATLAB Compiler, but want to use multiple threads when doing development, you could use something like this to limit MATLAB to one thread only for compiled versions:
 
 {code}
 if isdeployed
@@ -121,15 +121,15 @@
 
 If you do the above with R2009sp1 and newer and also use the -R -singleCompThread it will error out.
 
-*: *TODO*: Is the lastN necessary? Seems unlikely, unless Matlab gets cranky when return values are ignored.
+*: *TODO*: Is the lastN necessary? Seems unlikely, unless MATLAB gets cranky when return values are ignored.
 
-The above does not work on newer versions of Matlab, as maxNumCompThreads is deprecated.  Instead, pass the -singleCompThread option.  If you are using mcc (the Matlab compiler), add "-R -singleCompThread" to your compiler options.
+The above does not work on newer versions of MATLAB, as maxNumCompThreads is deprecated.  Instead, pass the =-singleCompThread= option.  If you are using mcc (the Matlab compiler), add =-R -singleCompThread= to your compiler options.
 
-The best you can do is prevent the compiled job from using one thread per core. It will still have 5 threads with all the time on one of them. Java aps will use a few more threads. But you will have less then one thread per core which is what it will do on its own.
+The best you can do is prevent the compiled job from using one thread per core. It will still have 5 threads with all the time on one of them. Java applications will use a few more threads. But you will have less then one thread per core which is what it will do on its own.
 
 {section: Example}
 
-This example assumes that Matlab is available in /opt/Matlab/bin.
+This example assumes that MATLAB is available in =/opt/Matlab/bin=.
 
 *COMPLETELY UNTESTED*
 *:*TODO*: Is the DISPLAY=:0.0 required? Seems unlikely.
@@ -147,9 +147,9 @@
 queue
 {endcode}
 
-{section: Compiled Matlab Example (completely tested)}
+{section: Compiled MATLAB Example (completely tested)}
 
-Given a successful mcc run, as described above, and assuming the matlab runtime isn't pre-install on any of the execute machines, you can transfer the runtime along with the condor job.  There is an example of this in chtc in /home/gthain/CompiledMatlabExample.  First, put the whole runtime into a single tar file, called m.tgz.  Then, edit the run_foo.sh wrapper (which was created by the compiler) to add the lines
+Given a successful mcc run, as described above, and assuming the MATLAB runtime is not pre-installed on any of the execute machines, you can transfer the runtime along with the Condor job.  There is an example of this in CHTC in =/home/gthain/CompiledMatlabExample=.  First, put the whole runtime into a single tar file, called =m.tgz=.  Then, edit the =run_foo.sh= wrapper (which was created by the compiler) to add the lines
 
 {code}
 tar xzf m.tgz
@@ -158,7 +158,7 @@
 export MCR_CACHE_ROOT=`pwd`/cache
 
 {endcode}
-at the beginning of the script, but after the #! line.  When matlab runs, it wants to create a cache directory under the user's home directory, which may not exist on an execute machine, or may conflict with other concurrently running matlab.  Then, create a submit file that looks something like:
+at the beginning of the script, but after the #! line.  When MATLAB runs, it wants to create a cache directory under the user's home directory, which may not exist on an execute machine, or may conflict with other concurrently running MATLAB.  Then, create a Condor submit description file that looks something like:
 
 {code}
 universe = vanilla
@@ -181,7 +181,7 @@
 
 {section: Additional Resources}
 
-Many other sites are using Matlab under Condor.  Here are links to the documentation from just a few.
+Many other sites are using MATLAB under Condor.  Here are links to the documentation from just a few.
 
 *: {link:http://www.cae.wisc.edu/matlab-condor University of Wisconsin - Madison - CAE}
 *: {link:http://www.liv.ac.uk/csd/escience/condor/matlab/old_instructions.htm University of Liverpool}