Differences

This shows you the differences between two versions of the page.

--- software:matlab:matlab [2019-08-27 15:59] – anita
+++ software:matlab:matlab [2021-02-24 16:37] (current) – [Details by cluster] anita
@@ Line 8: / Line 8: @@
 ====== License information ======
-MATLAB is product licensed by Mathworks.  The MATLAB product and related toolboxes are usually installed, on campus, to use the UD license server.  When MATLAB is started a license token is checked out from the license server. Each toolbox function also requires the availability of a license token to start during a MATLAB session. The UD license server currently has tokens for [[central licenses|core MATLAB and about 40 toolboxes]].
+MATLAB is product licensed by Mathworks.  The MATLAB product and related toolboxes are usually installed requiring access to the UD license server and requires a **persistent network connection** as well as [[http://www.udel.edu/it/help/connecting/vpn/|UD VPN]] when accessing off-campus. When MATLAB is started a license token is checked out from the license server. Each toolbox function also requires the availability of a license token to start during a MATLAB session. The UD license server currently has tokens (number of licenses) for [[central licenses|core MATLAB and about 50 toolboxes]].
 The Mathworks R2013b and newer license server is being queried every 6 minutes on each cluster for available seats licensed for Matlab, Simulink and associated toolboxes.
@@ Line 32: / Line 32: @@
 When you have a MATLAB job tested and debugged in a project directory, you are ready run on a cluster.
-===== Copy the project folder =====
+See [[#details-by-clusters|cluster details]] for examples on running your Matlab job on a particular cluster.
-Copy the project folder to a directory on the cluster.
-Use  any [[:abstract:farber:transfer|file transfer client]] to copy your entire project directory.
-====== Batch job======
-See [[#cluster details]] for running MATLAB as a batch application since each cluster will have different job templates based on the job scheduler such as Slurm or Grid-Engine.  You should have a copy of your MATLAB [[#project directory]] on the cluster.
-<note important>**Versions of MATLAB**
-MATLAB has a new version twice a year.  It is important to keep the version you use on your desktop the same as the
-one on the cluster.  The command
-<code>
-vpkg_versions matlab
-</code>
-will show you the versions available on a cluster.  Choose the one that matches the version on your desktop.  We recommend you do not upgrade MATLAB in the middle of a project, unless there is a new feature or bug fix you need.
-</note>
-<note tip>**Two directories**
-It is frequently advisable to keep your MATLAB project clean from non-MATLAB files such as the queue
-script file and the script output file.  But you may combine them, and even use the MATLAB editor to
-create the script file and look at the output file.
-If you create the file on a PC, take care to not transfer the files as binary. See Transfer Files for the appropriate cluster.
-When you have one combined directory, do not put the ''cd'' command in the queue script; instead, change
-to the project directory using ''cd'' on the command line, before submitting your job.
-</note>
-===== Create a queue script file =====
-You should create a queue script file to submit a batch job. Start by modifying a job template file (''/opt/templates''), for example, to submit a serial job on one core of a compute node, copy the serial template.
-In your copy change the commented ''vpkg_require'' command to
-require MATLAB, and then add your shell commands to the end of the file. Your copy may contain the lines:
-<code>
-# Add vpkg_require commands after this line:
-vpkg_require matlab
-# Now append all of your shell commands necessary to run your program
-# after this line:
-cd project_directory
-matlab -nodisplay -singleCompThread -r main_script
-</code>
-The ''project_directory'' should have a file named ''main_script.m'' with your script.  It could have just
-one line **''display 'Hello World'''**.
-For more examples, including examples that use multiple computational threads or the Parallel toolbox, see the [[#cluster details]]
 ====== Parallel job ======
@@ Line 100: / Line 53: @@
-=====Details by clusters=====
+======Details by cluster======
+  * [[software:matlab:caviness | Caviness]]
   * [[software:matlab:farber | Farber]]
   * [[software:matlab:mills| Mills]]