Signal processing toolbox not recognized in Octave

[ido]

From [email protected] on August 10, 2011 14:18:18

What steps will reproduce the problem? 1. > initPmtk3Octave 2. > plotMFCC What is the expected output? What do you see instead? The specgram function does not run and no plot is produced. I expected 'signalToolboxInstalled' to be true, but it is not.

What version / revision of the product are you using? On what operating system?

I'm using a copy off trunk at http://pmtk3.googlecode.com/svn/trunk with Octave 3.2.3 on Ubuntu 10.04.3 LTS. Please provide any additional information below. I investigated and found that the initPmtkOctave function unilaterally sets ToolboxInstalled variables to 0. Inspecting the normal init function, I learned how I *thought things should work and made modifications such that it did. My patch for this assumes that if the folder named in 'toolbox' exists in the path, then the toolbox must be installed. This may or may not be the appropriate way to detect this in Octave. If it is not, I'd be happy to improve the patch by making it more robust.

I also had make another change in order to get this to work correctly. It seems restoredefaultpath() does not do what I expected, in that the signal processing toolbox is omitted from the path after this function is called. But upon further reading, it appears the correct behavior is to set the path to its value /prior to any octaverc processing/ ( http://octave.1599824.n4.nabble.com/octaverc-and-version-in-path-td1648598i20.html ). So, given the fact that the toolkit paths are added in /etc/octave3.2.conf, I'm proposing restoredefaultpath() be removed. Would this cause problems elsewhere? If so, perhaps there is a way to trigger the path changes that come from the system-wide initialization file (and perhaps the user initialization files as well), so that restoredefaultpath() can still be used, but the add-on paths are included as well.

Attachment: init.diff

Original issue: http://code.google.com/p/pmtk3/issues/detail?id=30