{section: Executables}
 
-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.
+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.
 
-If you install Condor locally on each machine, it is recommended to place Matlab in the same location on each machine
+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.
+
+If you install Condor locally on each machine, it is recommended to place Matlab in the same location on each machine.  That way individual jobs can easily find it.  If Condor will be in different locations on each machine, 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):
+
+{code}
+executable = my_task
+arguments = $$(MATLAB_PATH)
+transfer_input_files= my_task.m
+queue
+{endcode}
+
+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.
+
+Installing on a shared filesystem is identical to installing it on each local computer, but may be less complicated for administration.
+
+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 machine 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}
+
+{section: Additional Resources}
+
+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}