How from script in Matlab 2011a call function from Matlab 2013b? - matlab

I have a bunch of scipts and MEX-files that developed for MAtlab 2011a version. They doesn't work on 2013b version. But Matlab 2013b has a function with desired functionality... So how can I run scipts in Matlab 2011a, but with call one function from 2013b version?
I have error
Unexpected Standard exception from MEX file.
What() is:
Device -1: deviceMatrix(): no CUDA-capable device is detected
what looks like unsolvable for me because I cannot rewrite MEX-file.
There is CUDA-device which is detected fine by 2011a version.
I'm asking a particular question. I cannot rewrite MEX-file because I do not want to dive into it - it is not my code and I don't know CUDA and that way that I'm asking for looks like much simpler for me at least at this step of my work. Later if function will fits for me I will think about going to Matlab 2013b version.
Yes, CUDA is aviable on Matlab 2013b.

Related

How compile m-file without installed Matlab?

What is the simplest way to compile m-file without installed matlab?
And can someone say when will users get possibility for compiling programs with training networks (not only using training networks in compiling)?
MATLAB is not a compiled language, it is interpreted at runtime, so you need to have MATLAB installed to run a m-File (script). You can use the MATLAB compiler software to create a standalone application from an m-File or a function.
To run an m-file without having MATLAB, you can use GNU Octave. Octave is an open-source software which has almost the same syntax and functionality as MATLAB. They are not 100% identical though, so you will have to migrate your script. As mentioned in this question, code which runs in MATLAB will almost always run in Octave too, so it should work quite well.
for very basic scripting you can use this online octave(/matlab) compiler I found http://www.tutorialspoint.com/matlab/try_matlab.php There are some limitations of course, but for basic scripts it works well

using autocorr for different matlab versions

I'm trying to compute the autocorrelation of my timeseries. This work on my laptop with matlab R2011a, but not on my desktop with matlab R2013a. I read somewhere that the Signal Processing Toolbox needs to be installed, and that is the case on both of my computers. There seems to be no function at all called autocorr, but I can find it again on the matworks documentation for 2014b. I have the same problem with xcorr, although matlab seems to recognize the function ('help xcorr' works, 'help autocorr' not).
How can I fix this?

MATLAB Compiler vs MATLAB Coder

What's the difference between the two?
As far as I understand it, MATLAB Compiler wraps the MATLAB code into a .exe file so that it can be used without installing MATLAB, and only requires the MCR. On top of it MATLAB Builder NE can also be used to produce .Net assemblies to be used with .Net framework instead of the .exe file, but they still require MCR.
Now I don't understand what MATLAB Coder used for? It generates C/C++ code. But is the MATLAB code really converted into C/C++, or is it merely packaged like in the case of MATLAB Compiler? Does it also need the MCR to run?
I understand that this is not exactly a programming question. But I have searched the internet and still haven't found a clear answer. These are very expensive products so I would like to know what I am getting into.
MATLAB Compiler encrypts and archives your MATLAB code (which remains as MATLAB .m code), and packages it in a thin executable (either .exe or .dll) wrapper. This is delivered to the end user along with the MATLAB Compiler Runtime (MCR). If you wish, the MCR can be packaged within the executable as well.
The MCR is freely redistributable, and you can think of it as essentially a copy of MATLAB without a front-end desktop.
When the user runs the executable, it dearchives and decrypts the MATLAB code, and runs it against the MCR instead of MATLAB. Applications delivered via this method should therefore run exactly the same as they do within MATLAB (including the same speed).
MATLAB Coder converts a subset of the MATLAB language into C code. This can then be used in many different ways, including being brought back into MATLAB as a mex file, compiled with a C compiler to be called from another application, or delivered to an embedded device. Since it is C code rather than MATLAB code, it will often (though not always) run much faster than the original MATLAB code. The C code does not require the MCR. The supported subset of the MATLAB language is very extensive, but there are a few notable restrictions that you would want to look into before committing to this workflow. The code produced is C code, although it can produce a C++ wrapper if you have a need to use a C++ compiler rather than a C compiler.
MATLAB Compiler is intended for the use case that you want to simply and (fairly) straightforwardly share a MATLAB application that you've written with someone who does not have a copy of MATLAB. Since the deployed .m code is encrypted, it can also be used to share MATLAB code while protecting intellectual property.
MATLAB Coder has other use cases, such as wanting to speed up MATLAB code by converting to a mex file, or needing to produce C code for another application or an embedded device.
If you have more detailed questions, I would really recommend that you just call up MathWorks and ask them.
Edit: The information above is correct for versions of MATLAB R2014b and below. As of MATLAB R2015a, functionality from MATLAB Compiler has been remixed with functionality from the MATLAB Builder products, and there is also a new product MATLAB Compiler SDK.
As of R2015a, MATLAB Compiler works in the same way as described above (i.e. encrypt, archive and package, but not producing C), but will now package as .exe, and as an Excel add-in (.xla). Prior to R2015a, this functionality used to be present in the product MATLAB Builder EX for Excel.
As of R2015a, MATLAB Compiler no longer produces .dll components. This functionality has been moved to the new product MATLAB Compiler SDK, which also includes functionality to produce .NET assemblies and Java classes. Prior to R2015a, this functionality used to be present in the products MATLAB Builder NE for .NET and MATLAB Builder JA for Java.
In other words:
In R2014b and below, we had:
MATLAB Compiler: produce .exe and .dll components
MATLAB Builder NE for .NET: produce .NET assemblies
MATLAB Builder JA for Java: produce Java classes
MATLAB Builder EX for Microsoft Excel: produce Excel add-ins.
In R2015a, we have:
MATLAB Compiler: produce .exe and Excel add-ins
MATLAB Compiler SDK: produce .dll, .NET assemblies and Java classes.
The scope and use-cases of MATLAB Coder have not changed across these releases (although there are new features).
Edit: As of R2015b, MATLAB Compiler SDK also produces Python packages.
Additional information on distinguishing MATLAB Coder and MATLAB Compiler for C/C++ can be found here.
Comparison table of different MATLAB Products for code generation.
MATLAB Compiler SDK provides shared libraries that run against a MATLAB Runtime (MCR). It supports most of the features in MATLAB, including graphics, and protects your intellectual property by encrypting your MATLAB code.
MATLAB Coder, on the other hand, provides readable and portable source code. It supports a subset of the MATLAB Language focused on algorithms performing numerical computations.
This MATLAB Answers goes into more details comparing these two approaches:
http://www.mathworks.com/matlabcentral/answers/223937-should-i-use-matlab-compiler-sdk-or-matlab-coder-to-integrate-my-matlab-applications-with-c-c
For example, MATLAB Compiler SDK can be deployed only to platforms that support MATLAB (Windows, Mac, Linux) whereas MATLAB Coder generates C code that can run on any platform that supports C code.
Also, the packaged code from MATLAB Compiler SDK is encrypted to protect IP, whereas the generated C code from MATLAB Coder can be protected in the same way hand written C code is protected.
It's also worth noting that generated C code from MATLAB Coder has the potential of faster execution while the packaged code from MATLAB Compiler SDK will run as fast as it does in MATLAB.
I'm not an expert, but the Coder is described as generating standalone C/C++ code, making no mention of the MCR. I notice however that it says that it only supports a "subset" of the Matlab language, which you can read more about here. The Compiler appears to just package up your Matlab code as you suggested, so probably supports most features.
MATLAB coder generates C/C++ code, which could also depend on 3rd party libraries such as intel's TBB/IPP. If you want truly vanilla C/C++ code, you need MATLAB's embedded coder.
On the other hand, MATLAB compiler produces encrypted executables/libraries/etc which runs against MCR (Matlab runtime library). This requires the target computer to pre-install MCR (at no cost). Since MCR is over 1 GB in size, it's not very retargetable.
MATLAB coder is also more expensive than MATLAB compiler.

Workaround for Maple in MATLAB

I am trying to get the MATLAB toolbox SOSTOOLS to work inside a MATLAB R2010b (7.11.0.584) but get the following error:
??? Error using ==> maple at 54 The MAPLE command is not available.
Googling it I found out that MATLAB stopped using Maple at some stage and switched to MuPad.
Short of switching to an older version of MATLAB, is there a known workaround for this situation?
A solution in the form of installing Maple as the symbolic toolbox engine is not possible with your version of Matlab.
This outlines an alternative possible solution, I did not find a concrete workaround that will spare you work. I recommend you contact the authors, or check for octave versions with the same functionality.
The change to MuPad is a problem that's been posted numerous times, and there is a useful discussion of differences between Maple and MuPad here:
http://www.walkingrandomly.com/?p=178
For some commands it looks like a simple translator might work. Most of the implementation would apparently be in parsing the output from MuPad and turning it into what Maple would generate. The input to MuPad and Maple is apparently equal most of the time, but read the doc above.
To write a translator, you redirect calls to maple by placing in your path the following function maple that calls mupad:
function output=maple(input);
%prepare input here (if necessary) ...
output=mupad(input);
% parse the output (if necessary) ...
More likely than not, a naive call to this re-director will not solve the problem without some input/output parsing.

How to use lassoglm in matlab

I have this issue while using the lassoglm function in matlab. My matlab says that the statistics toolbox is installed. However, I couldn't see lassoglm function available in my matlab
Your Matlab version isn't recent enough.
It isn't there on my R2010a version. The documentation on the website is for 2012b.