https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Vdo2&feedformat=atomUMIACS - User contributions [en]2024-03-30T04:59:50ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&diff=7157Matlab2016-10-06T14:29:40Z<p>Vdo2: </p>
<hr />
<div>UMIACS has [[Matlab]] licenses that cover Linux, Windows and Mac. To access them you have to be using a university owned computer. If you would like to run Matlab on a machine that is not University-owned, you can check the pricing through OIT/SLIC [http://www.oit.umd.edu/units/slic/products/mathworks/matlab.html here]<br />
<br />
==Linux==<br />
Below are the different versions of Matlab across our supported linux workstations and servers. The one in bold is our latest version. RHEL5 is no longer supported as of R2013b, and 32-bit Linux distributions are no longer supported as of R2012b. For more information, please see [http://www.mathworks.com/support/sysreq/roadmap.html this page].<br />
<br />
[[Modules | Modules]] is the preferred way to interact with Matlab and the page will provide information on adding Matlab into your environment and using it.<br />
<br />
===RHEL5===<br />
* /opt/matlab-r2007b<br />
* /opt/matlab-r2008a<br />
* /opt/matlab-r2008b<br />
* /opt/matlab-r2009b<br />
* /opt/matlab-r2010a<br />
* /opt/matlab-r2010b<br />
* /opt/matlab-r2011a<br />
* /opt/matlab-r2011b<br />
* /opt/matlab-r2012a<br />
* /opt/matlab-r2012b<br />
* '''/opt/matlab-r2013a''' <br />
<br />
===RHEL6,7/Ubuntu===<br />
<br />
* /opt/common/matlab-r2007b<br />
* /opt/common/matlab-r2008a<br />
* /opt/common/matlab-r2008b<br />
* /opt/common/matlab-r2009b<br />
* /opt/common/matlab-r2010a<br />
* /opt/common/matlab-r2010b<br />
* /opt/common/matlab-r2011a<br />
* /opt/common/matlab-r2011b<br />
* /opt/common/matlab-r2012a<br />
* /opt/common/matlab-r2012b<br />
* /opt/common/matlab-r2013a<br />
* /opt/common/matlab-r2013b<br />
* /opt/common/matlab-r2014a<br />
* /opt/common/matlab-r2014b<br />
* '''/opt/common/matlab-r2015a'''<br />
<br />
==Windows==<br />
Below are the different locations of Matlab available for university-owned machines running Windows. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2007a<br />
* Matlab r2007b<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009a<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011a<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a<br />
* Matlab r2013b<br />
* Matlab r2014a<br />
* Matlab r2014b<br />
* Matlab r2015a<br />
* '''Matlab r2016a'''<br />
<br />
==OSX==<br />
Below are the different locations of Matlab available for university-owned machines running OSX. We expect that all versions should run on OSX 10.8 and newer. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a (OSX 10.8+)<br />
* '''Matlab r2013b''' (OSX 10.8+)<br />
<br />
==License Troubleshooting==<br />
<br />
Campus has a limited number of seats for Matlab itself, as well as the various toolboxes. When calling functions in a toolbox, Matlab will automatically check out a license, making it temporarily unavailable to other users. Sometimes it's necessary to check the number of toolbox licenses available.<br />
<br />
===Windows License Troubleshooting===<br />
On Windows machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. "win64" needs to be adjusted to "win32" on a 32-bit installation:<br />
$MATLAB_PATH\etc\win64\lmutil lmstat -c "$MATLAB_PATH\licenses\network.lic" -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2012b on a 64-bit Windows 7 host for the Aerospace Blockset Toolbox: <br />
"C:\Program Files\matlab\r2012b\etc\win64\lmutil.exe" lmstat -c "C:\Program Files\matlab\r2012b\licenses\network.lic" -f Aerospace_Blockset<br />
<br />
===Unix License Troubleshooting===<br />
On Unix machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. "glnxa64" needs to adjusted to "glnx86" on a 32-bit installation::<br />
$MATLAB_PATH/bin/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2010b on our 64-bit RHEL5 hosts for the Parallel Computing Toolbox:<br />
/opt/matlab-r2010b/bin/glnxa64/lmutil lmstat -c /opt/matlab-r2010b/licenses/network.lic -f Distrib_Computing_Toolbox<br />
<br />
===Toolbox Shortnames===<br />
The toolbox names themselves don't always work with this command; Rather, Matlab has a set of shortnames which can be passed to the lmstat command. The following are all the valid shortnames:<br />
<br />
Aerospace_Blockset <br />
Aerospace_Toolbox <br />
Bioinformatics_Toolbox <br />
Communication_Blocks <br />
Communication_Toolbox <br />
Compiler <br />
Control_Toolbox <br />
Curve_Fitting_Toolbox <br />
Data_Acq_Toolbox <br />
Database_Toolbox <br />
Datafeed_Toolbox <br />
Distrib_Computing_Toolbox <br />
Econometrics_Toolbox <br />
Excel_Link <br />
Fin_Derivatives_Toolbox <br />
Financial_Toolbox <br />
Fixed_Income_Toolbox <br />
Fixed_Point_Toolbox <br />
GADS_Toolbox <br />
Identification_Toolbox <br />
Image_Acquisition_Toolbox <br />
Image_Toolbox <br />
Instr_Control_Toolbox <br />
MAP_Toolbox <br />
MATLAB <br />
MATLAB_Builder_for_Java <br />
MATLAB_Coder <br />
MATLAB_Excel_Builder <br />
MATLAB_Report_Gen <br />
MPC_Toolbox <br />
Neural_Network_Toolbox <br />
Optimization_Toolbox <br />
PDE_Toolbox <br />
Real-Time_Workshop <br />
Robust_Toolbox <br />
Signal_Blocks <br />
Signal_Toolbox <br />
SimMechanics <br />
Simscape <br />
SIMULINK <br />
Simulink_Control_Design <br />
Stateflow <br />
Stateflow_Coder <br />
Statistics_Toolbox <br />
Symbolic_Toolbox <br />
Video_and_Image_Blockset <br />
Virtual_Reality_Toolbox <br />
Wavelet_Toolbox<br />
<br />
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus' Division of Information Technology.<br />
<br />
==Matlab Customizations==<br />
<br />
You can tweak your Matlab experience using a file "startup.m". If this file is present in the current working directory where you launch Matlab, it will be executed. You can perform a variety of tasks using this file. These include (but are not limited to) customizing the window environment, setting variables for later use, and enabling use of 3rd party toolboxes. Alternatively, you can use the userpath env variable to set a path other than the current working directory for startup and 3rd party toolbox locations. Please see the following links for more information:<br />
<br />
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]<br />
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]</div>Vdo2https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&diff=7154Matlab2016-09-29T15:41:33Z<p>Vdo2: </p>
<hr />
<div>UMIACS has [[Matlab]] licenses that cover Linux, Windows and Mac. To access them you have to be using a university owned computer. [[Modules | Modules]] is the preferred way to interact with Matlab and the page will provide information on adding Matlab into your environment and using it. If you would like to run Matlab on a machine that is not University-owned, you can check the pricing through OIT/SLIC [http://www.oit.umd.edu/units/slic/products/mathworks/matlab.html here]<br />
<br />
==Linux==<br />
Below are the different locations of Matlab across our supported linux workstations and servers. The one in bold is our latest version. RHEL5 is no longer supported as of R2013b, and 32-bit Linux distributions are no longer supported as of R2012b. For more information, please see [http://www.mathworks.com/support/sysreq/roadmap.html this page].<br />
<br />
===RHEL5===<br />
* /opt/matlab-r2007b<br />
* /opt/matlab-r2008a<br />
* /opt/matlab-r2008b<br />
* /opt/matlab-r2009b<br />
* /opt/matlab-r2010a<br />
* /opt/matlab-r2010b<br />
* /opt/matlab-r2011a<br />
* /opt/matlab-r2011b<br />
* /opt/matlab-r2012a<br />
* /opt/matlab-r2012b<br />
* '''/opt/matlab-r2013a''' <br />
<br />
===RHEL6,7/Ubuntu===<br />
<br />
* /opt/common/matlab-r2007b<br />
* /opt/common/matlab-r2008a<br />
* /opt/common/matlab-r2008b<br />
* /opt/common/matlab-r2009b<br />
* /opt/common/matlab-r2010a<br />
* /opt/common/matlab-r2010b<br />
* /opt/common/matlab-r2011a<br />
* /opt/common/matlab-r2011b<br />
* /opt/common/matlab-r2012a<br />
* /opt/common/matlab-r2012b<br />
* /opt/common/matlab-r2013a<br />
* /opt/common/matlab-r2013b<br />
* /opt/common/matlab-r2014a<br />
* /opt/common/matlab-r2014b<br />
* '''/opt/common/matlab-r2015a'''<br />
<br />
==Windows==<br />
Below are the different locations of Matlab available for university-owned machines running Windows. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2007a<br />
* Matlab r2007b<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009a<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011a<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a<br />
* Matlab r2013b<br />
* Matlab r2014a<br />
* Matlab r2014b<br />
* Matlab r2015a<br />
* '''Matlab r2016a'''<br />
<br />
==OSX==<br />
Below are the different locations of Matlab available for university-owned machines running OSX. We expect that all versions should run on OSX 10.8 and newer. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a (OSX 10.8+)<br />
* '''Matlab r2013b''' (OSX 10.8+)<br />
<br />
==License Troubleshooting==<br />
<br />
Campus has a limited number of seats for Matlab itself, as well as the various toolboxes. When calling functions in a toolbox, Matlab will automatically check out a license, making it temporarily unavailable to other users. Sometimes it's necessary to check the number of toolbox licenses available.<br />
<br />
===Windows License Troubleshooting===<br />
On Windows machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. "win64" needs to be adjusted to "win32" on a 32-bit installation:<br />
$MATLAB_PATH\etc\win64\lmutil lmstat -c "$MATLAB_PATH\licenses\network.lic" -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2012b on a 64-bit Windows 7 host for the Aerospace Blockset Toolbox: <br />
"C:\Program Files\matlab\r2012b\etc\win64\lmutil.exe" lmstat -c "C:\Program Files\matlab\r2012b\licenses\network.lic" -f Aerospace_Blockset<br />
<br />
===Unix License Troubleshooting===<br />
On Unix machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. "glnxa64" needs to adjusted to "glnx86" on a 32-bit installation::<br />
$MATLAB_PATH/bin/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2010b on our 64-bit RHEL5 hosts for the Parallel Computing Toolbox:<br />
/opt/matlab-r2010b/bin/glnxa64/lmutil lmstat -c /opt/matlab-r2010b/licenses/network.lic -f Distrib_Computing_Toolbox<br />
<br />
===Toolbox Shortnames===<br />
The toolbox names themselves don't always work with this command; Rather, Matlab has a set of shortnames which can be passed to the lmstat command. The following are all the valid shortnames:<br />
<br />
Aerospace_Blockset <br />
Aerospace_Toolbox <br />
Bioinformatics_Toolbox <br />
Communication_Blocks <br />
Communication_Toolbox <br />
Compiler <br />
Control_Toolbox <br />
Curve_Fitting_Toolbox <br />
Data_Acq_Toolbox <br />
Database_Toolbox <br />
Datafeed_Toolbox <br />
Distrib_Computing_Toolbox <br />
Econometrics_Toolbox <br />
Excel_Link <br />
Fin_Derivatives_Toolbox <br />
Financial_Toolbox <br />
Fixed_Income_Toolbox <br />
Fixed_Point_Toolbox <br />
GADS_Toolbox <br />
Identification_Toolbox <br />
Image_Acquisition_Toolbox <br />
Image_Toolbox <br />
Instr_Control_Toolbox <br />
MAP_Toolbox <br />
MATLAB <br />
MATLAB_Builder_for_Java <br />
MATLAB_Coder <br />
MATLAB_Excel_Builder <br />
MATLAB_Report_Gen <br />
MPC_Toolbox <br />
Neural_Network_Toolbox <br />
Optimization_Toolbox <br />
PDE_Toolbox <br />
Real-Time_Workshop <br />
Robust_Toolbox <br />
Signal_Blocks <br />
Signal_Toolbox <br />
SimMechanics <br />
Simscape <br />
SIMULINK <br />
Simulink_Control_Design <br />
Stateflow <br />
Stateflow_Coder <br />
Statistics_Toolbox <br />
Symbolic_Toolbox <br />
Video_and_Image_Blockset <br />
Virtual_Reality_Toolbox <br />
Wavelet_Toolbox<br />
<br />
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus' Division of Information Technology.<br />
<br />
==Matlab Customizations==<br />
<br />
You can tweak your Matlab experience using a file "startup.m". If this file is present in the current working directory where you launch Matlab, it will be executed. You can perform a variety of tasks using this file. These include (but are not limited to) customizing the window environment, setting variables for later use, and enabling use of 3rd party toolboxes. Alternatively, you can use the userpath env variable to set a path other than the current working directory for startup and 3rd party toolbox locations. Please see the following links for more information:<br />
<br />
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]<br />
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]</div>Vdo2https://wiki.umiacs.umd.edu/umiacs/index.php?title=FileTransferProtocol&diff=7072FileTransferProtocol2016-08-11T13:43:13Z<p>Vdo2: </p>
<hr />
<div>UMIACS provides FTP services for transferring data to and from external collaborators. Since the FTP protocol is conducted entirely in plaintext, external users login to the service as anonymous, and internal users can access the file directories internally. Users will never authenticate over FTP with their UMIACS account. Please see [[SFTP]] for more information on a secure file transfer protocol.<br />
<br />
==Getting data from Collaborators==<br />
<br />
Collaborators can drop data for users into their FTP incoming file system, located from the FTP service at<br />
<br />
<pre>ftp://ftp.umiacs.umd.edu/incoming/<username>/</pre><br />
<br />
FTP logins can write to this space to upload data, but cannot list the files they have placed there. Users can then access the data in their ftpincoming space from <br />
<br />
* '''/fs/ftp/incoming/<username>''' from supported unix machines<br />
* '''\\umiacs-webftp\ftp-umiacs\incoming\<username>''' - from supported windows machines<br />
<br />
/fs is an automounted file system. This means it will mount other file systems on demand. Although the ftp directory may not be visible to an ls command while in fs, one can still cd into ftp.<br />
<br />
Please move your data as soon as possible after it is left for you - files older than 15 days are subject to deletion as necessary.<br />
<br />
==Publishing data sets via FTP==<br />
{{Note|'''This part of our FTP service is deprecated in favor of the UMIACS Object Store. Please see [[OBJbox]].'''}} <br />
<br />
Users can place data to be externally accessible in their public FTP space, which is located from the FTP service as<br />
<br />
<pre>ftp://ftp.umiacs.umd.edu/pub/<username>/</pre><br />
<br />
To upload data to your public site, you can upload data to,<br />
<br />
* '''/fs/ftp/pub/<username>''' from supported unix machines<br />
* '''\\umiacs-webftp\ftp-umiacs\pub\<username>''' - from supported windows machines<br />
<br />
==Effects of tmpwatch==<br />
There is a configuration of tmpwatch[http://linux.die.net/man/8/tmpwatch] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.</div>Vdo2https://wiki.umiacs.umd.edu/umiacs/index.php?title=FileTransferProtocol&diff=7071FileTransferProtocol2016-08-11T13:41:57Z<p>Vdo2: </p>
<hr />
<div>UMIACS provides FTP services for transferring data to and from external collaborators. Since the FTP protocol is conducted entirely in plaintext, external users login to the service as anonymous, and internal users can access the file directories internally. Users will never authenticate over FTP with their UMIACS account. Please see [[SFTP]] for more information on a secure file transfer protocol.<br />
<br />
==Getting data from Collaborators==<br />
<br />
Collaborators can drop data for users into their FTP incoming file system, located from the FTP service at<br />
<br />
<pre>ftp://ftp.umiacs.umd.edu/incoming/<username>/</pre><br />
<br />
FTP logins can write to this space to upload data, but cannot list the files they have placed there. Users can then access the data in their ftpincoming space from <br />
<br />
* '''/fs/ftp/incoming/<username>''' from supported unix machines<br />
* '''\\umiacs-webftp\ftp-umiacs\incoming\<username>''' - from supported windows machines<br />
<br />
/fs is an automounted file system. This means it will mount other file systems on demand. Although the ftp directory may not be visible to an ls command while in fs, one can still cd into ftp.<br />
<br />
Please move your data as soon as possible after it is left for you - files older than 15 days are subject to deletion as necessary.<br />
<br />
==Publishing data sets via FTP==<br />
{{Note|'''This part of our FTP service is deprecated in favor of the UMIACS Object Store. Please look at [[OBJbox]].'''}} <br />
<br />
Users can place data to be externally accessible in their public FTP space, which is located from the FTP service as<br />
<br />
<pre>ftp://ftp.umiacs.umd.edu/pub/<username>/</pre><br />
<br />
To upload data to your public site, you can upload data to,<br />
<br />
* '''/fs/ftp/pub/<username>''' from supported unix machines<br />
* '''\\umiacs-webftp\ftp-umiacs\pub\<username>''' - from supported windows machines<br />
<br />
==Effects of tmpwatch==<br />
There is a configuration of tmpwatch[http://linux.die.net/man/8/tmpwatch] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.</div>Vdo2https://wiki.umiacs.umd.edu/umiacs/index.php?title=FileTransferProtocol&diff=7070FileTransferProtocol2016-08-11T13:40:36Z<p>Vdo2: /* Publishing data sets via FTP */</p>
<hr />
<div>UMIACS provides FTP services for transferring data to and from external collaborators. Since the FTP protocol is conducted entirely in plaintext, external users login to the service as anonymous, and internal users can access the file directories internally. Users will never authenticate over FTP with their UMIACS account. Please see [[SFTP]] for more information on a secure file transfer protocol.<br />
<br />
==Getting data from Collaborators==<br />
<br />
Collaborators can drop data for users into their FTP incoming file system, located from the FTP service at<br />
<br />
<pre>ftp://ftp.umiacs.umd.edu/incoming/<username>/</pre><br />
<br />
FTP logins can write to this space to upload data, but cannot list the files they have placed there. Users can then access the data in their ftpincoming space from <br />
<br />
* '''/fs/ftp/incoming/<username>''' from supported unix machines<br />
* '''\\umiacs-webftp\ftp-umiacs\incoming\<username>''' - from supported windows machines<br />
<br />
/fs is an automounted file system. This means it will mount other file systems on demand. Although the ftp directory may not be visible to an ls command while in fs, one can still cd into ftp.<br />
<br />
Please move your data as soon as possible after it is left for you - files older than 15 days are subject to deletion as necessary.<br />
<br />
==Publishing data sets via FTP==<br />
{{Note|This part of our FTP service is deprecated in favor of the UMIACS Object Store. Please look at [[OBJbox]].}} <br />
<br />
Users can place data to be externally accessible in their public FTP space, which is located from the FTP service as<br />
<br />
<pre>ftp://ftp.umiacs.umd.edu/pub/<username>/</pre><br />
<br />
To upload data to your public site, you can upload data to,<br />
<br />
* '''/fs/ftp/pub/<username>''' from supported unix machines<br />
* '''\\umiacs-webftp\ftp-umiacs\pub\<username>''' - from supported windows machines<br />
<br />
==Effects of tmpwatch==<br />
There is a configuration of tmpwatch[http://linux.die.net/man/8/tmpwatch] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.</div>Vdo2