Sharing toolbox (built-in functions) with two different versions of Matlab

Hello,

I have access to two different versions of Matlab. I need to use optimization toolbox in Simulink. The problem is that the version of Matlab that has Simulink does not include optimization toolbox. The one that includes optimization toolbox does not have Simulink installed. I was wondering if there is a way to use the optimization toolbox of one verion of Matlab from another. I am specifically interested in using "lsqnonneg()" and "lsqnonlin()" functions from the optimization toolbox in Simulink. Thanks in advance.

Ernur

Answer 1

[Jan]

You can run one Matlab version as an automation server, such that it can controlled remotely from the other version. See in the docs: External interface->MATLAB COM Automation server support and MATLAB COM client support.

[Walter Roberson]

An interesting approach -- but won't the version of Matlab chosen to serve the COM client depend upon the registry? If so then there could potentially be conflicts between running the two versions.

Answer 2

[Walter Roberson]

This question is closely related to a recent question #2187 about mixing toolbox versions.

Answer 3

[Walter Roberson]

As directly calling a routine from a different toolbox version is unstable, you are left with possibilities such as Jan describes for communicating between two sessions each running Matlab.

You might be able to do so productively on the the same system by using memmapfile() -- but that approach will likely run into synchronization problems.

There is a Matlab File Exchange contribution for sharing memory between matlab sessions using shared memory.

There is a Matlab File Exchange contribution "tcpudpip" which can use tcp or udp to communicate between different Matlab sessions, even if they are not on the same system. Exchanging actual variables is a bit of a nuisance, though.

Answer 4

[Ernur]

Thank you all for your time and discussions.

Jan's suggestion seems to be working so far. I will update you if there is a problem with that implementation. Thanks again.

Ernur