MATLAB Answers

Bug in Matlab/statistics toolbox or is there a typo in the plsregress example? (or something wrong with my Matlab installation?)

8 views (last 30 days)
I’m having problems with getting the partial least squares regression to work properly and I suspect that there either is something wrong with my matlab installation or that there is a bug in matlab/statistics toolbox. If I type:
help plsregress
I get this example:
load spectra
[xl,yl,xs,ys,beta,pctvar,mse] = plsregress(NIR,octane,10,'CV',10);
octaneFitted = [ones(size(NIR,1),1) NIR]*beta;
but when I run these two lines exactly as in the example:
load spectra
[xl,yl,xs,ys,beta,pctvar,mse] = plsregress(NIR,octane,10,'CV',10);
I get this:
Error using horzcat
Dimensions of matrices being concatenated are not consistent.
Error in crossval
Error in plsregress>plscv (line 351)
sumsqerr = crossval(CVfun,X,Y,cvpType,cvp,'mcreps',mcreps,'options',ParOptions);
Error in plsregress (line 214)
mse = plscv(X,Y,ncomp,cvp,mcreps,ParOptions);
Could someone be kind enough to type the two lines in your matlab and see if it works for you? And if it doesn’t, is there a typo in how the example is written or is there a bug in matlab/statistics toolbox?


Steven Lord
Steven Lord on 11 Mar 2016
Which release of the toolbox are you using?
Are you executing the example from the online documentation or from the documentation included in your installation? If you're executing the online example, check if it's different than the example in your locally installed documentation.
Petter Stefansson
Petter Stefansson on 11 Mar 2016
It was from a locally installed documentation. But I tried installing the new 2016a vesion of matlab (together with a potentially newer version of statistics toolbox) and now the exact same lines work! So either there was a bug in the version I was using before or something was wrong with my installation. For now at least it seems solved with 2016a, so thats good.

Sign in to comment.

Accepted Answer

Petter Stefansson
Petter Stefansson on 11 Mar 2016
If others are running into the same problem, it seems to be solved by updating to matlab 2016a!


Sign in to comment.

More Answers (0)

Sign in to answer this question.