Where are write permissions needed working with MATLAB?

The purpose of this question is to collect a list of cases where write permissions are needed working with MATLAB. A special emphasis is on folders within the MATLAB installation path.

Background is that some IT departments are interested in reducing the number of folders with write permissions.

A of the inifite possibilities what you can do with MATLAB, other MathWorks products and 3rd party tools, as well as dependencies on OSs and maybe releases, this list simply can't be complete.

Thank You for your contribution!

Answer 1

[Andreas Goser]

Places that can be customized:

• C Code generation through Simulink Coder (Formerly Real-time Workshop) and Embedded Coder (Formerly Real-Time Workshop Embedded Coder)
• Stateflow also create files before running
• Simulink Accelerator and Rapid Accelerator

Answer 2

[Sean de Wolski]

A couple easy ones:

• Saving the MATLAB pathdef file.
• Overwiting any shipped MATLAB code.

[Jan]

I avoid overwriting Matlab code, but add a folder in front of the PATH to shadow toolbox functions.

Answer 3

[Friedrich]

Hi,

For modifying classpath.txt and librarypath.txt one needs write acces to the toolbox\local folder.

Note that for 13a and newer one can create a javaclasspath.txt and place it anywhere on the MATLAB search path. This file is picked up by MATLAB at startup and merged with the shipped classpath.txt then. So for 13a and newer one does not need write access to the classpath.txt. However for the librarypath.txt one still needs write permissions.

For example modifying this files is often needed when using DATABASE Toolbox in order to install a JDBC driver for MATLAB and allow the usage of windows authentication.

This needs to be done once, so the IT can take care of it.

For a user who works with MATLABs static java classpath and in an older release as R2013a write access is 100% needed. For newer releases he can work with the javaclasspath.txt and will be fine.

[Jan]

The single toolbox\local\javaclasspath.txt file for <2013a is a serious problem in multi-user setups, because a file working for one user might cause error for other users.

[Friedrich]

I guess you mean classpath.txt. And yes this can cause problems. But with nearly any MATLAB file you can shadow it. So copy the classpath.txt ot of the toolbox\local folder and place it in your own MATLAB startup folder. Add the entries you like and you and other users will be fine :)

Answer 4

[Jan]

Because I work in a multi-user setup, only one single change appears in Matlab's root folder: One folder is added to the PATH, which contains the function to add user- or project-dependent folder sets dynamically. By this method, users do not need write access to Matlab's path.

Even the startup.m file is replaced by a project depending method. But a dynamic modification of finish.m is required for some Matlab versions (6.5, 2011b, ...) to delete persistently store AudioPlayer objects.

I'm not sure if I understand the intention of the question: Are you asking for write access to other folders also?

[Andreas Goser]

The intention is to address user/IT requirement to give write access only for certain directories and obviously want to plan ahead. Maybe there are different IT viewpoints here, but I personally don't want to challenge that.