You will need to make the Matlab executable and supporting libraries available on any computers on which your jobs might run on.  You might install Matlab on each computer, install it on a shared filesystem, or bring Matlab along with you.
 
-For executables compiled with the Matlab Compiler, instead of the full Matlab install, you will need the MCR, the Matlab Compiler Runtime, but the general techniques are the same.
+For executables compiled with the Matlab Compiler, instead of the full Matlab install, you will need the MCR, the Matlab Compiler Runtime, but the general techniques are the same.  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:
 
@@ -73,7 +76,7 @@
 
 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.
 
-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);
@@ -88,7 +91,8 @@
 {endcode}
 
 *: *TODO*: Is the lastN necessary? Seems unlikely, unless Matlab gets cranky when return values are ignored.
-*: *TODO*: maxNumCompThreads is deprecated. The preferred solution is to pass "-singleCompThread" on the command line. _check if -singleCompThread works for compiled jobs_, we don't think it does.
+
+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.
 
 {section: Example}
 
@@ -110,6 +114,9 @@
 queue
 {endcode}
 
+
+
+
 {section: Additional Resources}
 
 Many other sites are using Matlab under Condor.  Here are links to the documentation from just a few.