MATLAB is a high-level language and interactive environment that enables you to perform computationally intensive tasks faster than with traditional programming languages such as C, C++, and Fortran.
The MATLAB home page is at http://www.mathworks.com/products/matlab.
MATLAB is available to eligible users on Pan and should be available soon on Mahuika.
MATLAB is made available to researchers under commercial licence agreements with individuals, research groups, departments, faculties or institutions. Whether you have access to MATLAB, which versions you have access to, and under what conditions, will vary depending on where you work or study. You will only be permitted to access and use any given version of MATLAB on any NeSI cluster if you have a valid licence to use that version of MATLAB at your place of work or study, and if the terms of your licence permit cluster use. If you have any questions regarding your eligibility to access MATLAB or any particular version of it, please contact our support desk.
Some institutions only have a limited number of MATLAB licence tokens. To ensure that there are always enough of these tokens remaining for interactive work and for scheduled jobs to start sucessfully, we request that users from Massey University inform Slurm of their jobs' licence requirements:
- Massey University:
If you get an error message indicating that no licenses are available for a certain feature, you can use a command like the following to check the licensing situation. The output will show you the licensing situation for individual features.
lmutil lmstat -a
#!/bin/bash -e #SBATCH --job-name MATLAB_job #SBATCH --time 01:00:00 #SBATCH --mem-per-cpu 1G module load MATLAB/2017b # Run the MATLAB script MATLAB_job.m srun matlab -nodisplay -r MATLAB_job
For MATLAB jobs the number of Slurm tasks (--ntasks) should always be 1, but if given the necessary resources some MATLAB functions can make use of multiple threads (--cpus-per-task) or GPUs (--gres gpu). If you use the higher-level parpool-based language constructs such as spmd and parfor MATLAB will make temporary files under your home directory (in ~/.matlab/local_cluster_jobs) for communication with worker processes. To prevent simultaneous such parallel MATLAB jobs from interfering with each other you should tell them to each use their own job-specific local directories:
pc = parcluster('local') pc.JobStorageLocation = getenv('TMPDIR') parpool(pc, str2num(getenv('SLURM_CPUS_PER_TASK')))
The same can be acheived from outside the MATLAB code with the quick hack of changing HOME:
HOME=$TMPDIR matlab ...