r2011a vs r2010a findpeaks

Hi All, I wrote an m-file using FINDPEAKS in r2010a but the file doesn't run in r2011a. After a little trial and error, it seems that the output format (rows and columns) has been reversed half of the time. There are two ways the input data can be formatted: one row and many columns (row vector) or many rows and one column (column vector). In r2010a, either way provides a row vector output. In r2011a, the output data format is the same as the input.

In other words:

r2010a - Row in, row out. Column in, row out.

r2011a - Row in, row out. Column in, column out.

For me, it's a simple fix with careful use of the TRANSPOSE function, but it is a bit annoying. The example in the help documentation only covers row vectors and the subtle change isn't mentioned there. Has anyone else experienced similar problems with FINDPEAKS or other functions? Is this common between releases? Thanks.

Regards, Henry

Answer 1

[Andreas Goser]

I investigated the release notes and was unable to find a documentation of an intended change. It is important letting MathWorks know about this potential bug. Can you contact Technical Support with your observation? Ideally with example data and code (even if it is a one liner).

[Henry]

Thanks for checking. I have submitted a description for tech support's consideration.

Answer 2

[Bhavna Rajasekaran]

The findpeaks doesnt even exist in the R2011a release at the moment. Is that right? There is no explanation, even some of the functions that the findpeaks was using have been removed.I am using this function already & now cant because its does not exist in the new release!

[Titus Edelhofer]

The function findPeaks is in the Signal Processing Toolbox. Maybe you have not installed it when installing R2011a?

[Henry]

I have used findpeaks in R2011a and it works fine except for the difference in 2010 and 2011 editions I mentioned above. 'help findpeaks' is there as well. I just had to remove some transposing lines from my r2010a scripts and everything worked as expected. I e-mailed the tech support people and they said the change in output orientation was intentional but it probably should have made it into the release notes.

Good luck!

Answer 3

[Bhavna Rajasekaran]

Thank you, I found the problem. There was some problem with the installation. It works now!