Dynamically choosing files in a deployed application

Hello, thanks for the assistance.

I am working on a large MATLAB application, that will be compiled and deployed to some of our users.

One aspect of this program allows the user to select a certain type of a .m file that was written according to one of our templates, and the program will plot the data inside of it and allow the user to look at the raw data inside of MATLAB.

To achieve this functionality, I have written an interface that will send the .m file, and all the other parameters and data, from the deployed application (no MATLAB license) to an instance of MATLAB (using a concurrent license).

Because these user-written .m files are not compiled, and can be in any location, I am not sure how to point to them with my compiled application. (I am aware that a compiled application can't run uncompiled files, which is why the interface was written). When testing this on an uncompiled version of the program, I am able to use addpath() to add these files to the MATLAB path, which is not possible on a compiled version.

Any help or idea would be appreciated.

Answer 1

[Jan]

You can use absolute path names to address the files. This is trivial, actually, therefore I'm not sure if I understand your question.

What is "a certain type of m file"? Do you create m-files dynamically to store data? This would be a very bad idea. Use binary or text files to store data, but not some pseudo-code. Then there would be no need to access a Matlab instance, because the data can be processed in the deployed compiled code.

[Matthew Brown]

Jan,

The m file contains MATLAB code that is written by the engineers, in order to plot data from a source in a certain way. However, each user can customize these m files, and they can't be compiled each time with our program. They are not storing any data, data storage is done using mat files.

After the file is selected, the (compiled) program reads the name of the function to create a function handle, which is then passed through my interface to a Matlab instance.

The Matlab instance is required because some Matlab features are used, that can't be compiled (editing the plots, for example).

In regards to using the absolute path: I can try using that, but in the past I have gotten an error on the compiled version saying that the file is not found in the ctfroot.