problem with findpeaks in R2016a

15 views (last 30 days)
John Ondov
John Ondov on 30 Mar 2016
Commented: Star Strider on 24 Apr 2016
The following works fine in R2015b, but not in R2016a (neither by live editor nor by command line)
[pks,locs,widths,proms]=findpeaks(A12ratio, x, 'MinPeakProminence', MPP);
In R2016a I get:
"Undefined function 'findpeaks' for input arguments of type 'double'."
Is this a known problem? Is there a workaround besides simply going back to using R2015b??

Answers (2)

Steven Lord
Steven Lord on 30 Mar 2016
Edited: Steven Lord on 30 Mar 2016
The findpeaks function is in Signal Processing Toolbox. It's possible you had this toolbox installed in your installation of release R2015b but don't have it installed in your installation of release R2016a.
  3 Comments
Steven Lord
Steven Lord on 31 Mar 2016
In that case, if you're using a network license it's possible all the license keys for Signal Processing Toolbox are checked out right now. Your license administrator could check this for you (if they're not sure how, ask them to take a look at page 3-61 of the Installation Guide.)
John Ondov
John Ondov on 24 Apr 2016
In case anyone else has this problem, it turned out to be a problem with the way R2016a deals with our University server array. At least, that's what our IT fellows told me after contacting MathSoft. As of April 20, 2016, it was not yet resolved. I'm back using R2015b until it is. That works just fine!

Sign in to comment.


Star Strider
Star Strider on 30 Mar 2016
You did install the Signal Processing Toolbox when you upgraded to R2016a, correct?
Assuming you did, my guess is that you have a path problem.
Try typing this from the Command Window (or embed it temporarily in your script):
restoredefaultpath
rehash toolboxcache
  6 Comments
John Ondov
John Ondov on 24 Apr 2016
I thought you might be interested in an update. it turned out to be a problem with the way R2016a deals with our University server array. At least, that's what our IT fellows told me after contacting MathSoft. As of April 20, 2016, it was not yet resolved. I'm back using R2015b until it is. That works just fine!
Star Strider
Star Strider on 24 Apr 2016
When I looked through the Release Notes, findpeaks hasn’t changed in R2016a, so the worst of your situation is simply the inconvenience, if you also need some new functionality in R2016a.

Sign in to comment.

Products

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!