StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO'Symbolic Math Toolbox' functions exist in MATLAB but not in the documentation
text
Body
copied!<p>This problem may seem a bit weird; please bear with me.</p> <p>When I try to access any function in the 'Symbolic Math Toolbox' in MATLAB, such as <code>help ztrans</code> or <code>help laplace</code>, I get the following kind of message</p> <pre><code>ztrans not found. Use the Help browser Search tab to search the documentation, or type "help help" for help command options, such as help for methods. </code></pre> <p>However, the toolbox seems to be installed when I try the <code>ver</code> or <code>pathtool</code> command.</p> <p>Moreover, when I try some simple code such as:</p> <pre><code>>> syms k x >> f = sin(k); >> ztrans(f, k, x) </code></pre> <p>the code works fine and on trying the <code>help</code> command again, they seem to work fine as well. However, the problem again arises when I close and reopen MATLAB.</p> <p>I found a few instances of other users facing similar problems on the Mathworks portal, but none of them seemed to provide any concrete solutions. Some of them seem to blame it on MATLAB hashing the tollbox incorrectly, so I tried the <code>rehash toolbox</code> command as well, but had no luck.</p> <p>I'm not sure if this problem is just for this particular toolbox or not, but the other toolboxes I use at least seem to work fine.</p> <p><strong>EDIT-I</strong></p> <p>I also realised that the documentation is always available when I take <code>Help --> Product Help</code> from the menu-bar, though it is not available in the function browser even after I try the sample code.</p> <p><strong>EDIT-II</strong></p> <pre><code>>> license('checkout','Symbolic_Toolbox') </code></pre> <p>gives me</p> <pre><code>ans = 1 </code></pre> <p>I'm not working on a student license either.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload