Matlab2020a Stores DMR files to C: drive

Good Evening,

The workstaions I run the model on have lots of RAM and no spare (well < 30GB) C: drive capacity. Does an option exist which allows Matlab to store DRM in memory (workspace) rather than on the C: drive ?

or

Has an option to do this been added to a later version of Matlab ?

Thank You

[Julian Stoev]

Bump!

[Jan]

@Julian Stoev: "DRM" or "DMR" files? Where are the files stored? In the user's TEMP folder? Then it might be easy to use a different TEMP folder on another disk, which can be defined in the operating system.

Of course, cleaning up the C disk is an option also. I've seen some cases, where a huge C:\Windws\Logs\CBS\CBS.log file occupies the complete disk. Cleaning the temp folders is useful also. Did you run "Clean Disk" to omit old error reports and the update history?

[Paul Mitchell]

DRM files - my mistake. The major problem is the DMR files can get significantly large and they are not always deleted by Matlab - Even though options pertaining the the handling of these files by Matlab have been set. This seems to be an on-going issue which doesnot appear to have been resolved. I'm currently looking at R2022a to investigate this issue further

[Jan]

@Paul Mitchell: Is moving the TEMP folder to another drive an option? Maybe:

@ECHO off
REM File: Matlab_TempD.bat
set "TMP=D:\Temp"
start "" matlab
exit

Now tempdir replies 'D:\Temp\' and maybe the DMR files (what ever this is) are stored there.

[Paul Mitchell]

Hi Jan, I am running on a HPC system. Currently the data is written the Node C: drive [but filling this drive] - I have a shabby method of systematically running a Robocopy script which mirrors (/MIR) the Temp directory on the C: drive with an empty directory - thus clearing it out. Not ideal but it gets me around the problem it’s just tedious having to remember to keep running the script.

The alternative is to write it to the HPC storage array (as per your suggestion) which I have tried but here problems arise because of not only me but also many other people accessing the storage array at once - causing random model failures.

The DMR files are files associated with the Simulink Data Inspector - which can get quite large (>4GB) which Maltab does not appear to handle there removal very well - retaining hundered of these files soon fills the Node C: drive.