Errors thrown when Parallel Toolbox invoked or Coder generation attempted

Hi all, I'm trying to speed up some code by using Parallel Toolbox and/or Coder. Yesterday I downloaded 2013b with these packages and installed them, though they are not functioning correctly. When I try to set up a pool, I get this error:

    >> myPool=parpool(2);
Error using parpool (line 99)
Undefined function or variable 'matlab.internal.getSettingsRoot'.

Also, when trying to transfer the code to MEX using Coder, I get:

   >> coder -build FCP.prj
Compilation failed.
Undefined variable "coder" or class "coder.internal.moreinfo".
Use help codegen for more information on using this command.

I'm not sure if they're related. I've tried searching for these errors online, but I couldn't find anything right off. Maybe I'm not looking in the right places. Any help is appreciated, thanks much!

[Constantine]

I get a similar problem, only the error is "undefined function or variable 'parpool'". Anyone understand what's going on??

[Walter Roberson]

parpool is new as of R2013b I believe.

[Marko Budisic]

I had a similar issue happening when running 'matlabpool open'. The culprit was a custom pathdef.m file. It appears that Matlab 2013b's internals are arranged slightly differently compared to 2013a and earlier versions. If you have a custom pathdef.m from an earlier version, it overrides 2013b's path setup and causes errors such as above.

Solution was to erase and re-generate pathdef.m to restore Matlab's toolbox paths and then manually add all the custom-toolbox directories I use.

Answer 1

[Ryan Livingston]

I'll suggest the usual suspects. Try running:

 rehash toolboxcache
 restoredefaultpath

[Haripriya Sharma]

I suggest changing the sequence of execution of the above mentioned commands, to first restore the default search path and then refresh function and file system path caches. Next check if the restorations help resolve the issue, if yes and if you do not have custom search paths, you can save the path settings to default by executing:

>> savepath

To reflect the changes in some cases require restarting MATLAB.

[Rob]

Thanks; this did the trick for me when I ran into the problem in R2015a-prerelease!

>> restoredefaultpath
>> rehash toolboxcache
>> savepath

Answer 2

[Tom]

Came across this problem also. Marko Budisic's suggestion was exactly the problem in my case. Reset the "Set Path" directories to the default and re-added my custom directories and if by magic, solved!

Thanks.

To reset using the GUI: Open up "Set Path" (located in the "Environment tab of Matlab 2013+) and then hit the "Default" button at the bottom of the panel. Then add your custom directories once the defaults have been restored. Done.