The toolbox is published in two forms. You need one of them, not both.
MTI-Toolbox-<version>.mltbx — the normal case. MATLAB
installs it as an add-on, sets your path for you, and registers the
documentation with the MATLAB Help browser.MTI-Toolbox-<version>-source.zip — for when your
environment restricts add-ons, or you would rather not run an installer.
You put the files on the path yourself, and read the manual that comes
in the folder instead of the Help browser.Both forms carry the same toolbox: the same source, the same demos, the same bundled third-party kit and the same offline HTML documentation. The build compares the two against each other file by file, so neither can quietly ship something the other does not.
Note: Nothing is downloaded while you install
Neither form fetches anything. Everything the toolbox needs from outside MathWorks — that is, the Sparse Grids MATLAB Kit — is already inside the file you downloaded, so installation works offline and cannot fail because a download did.
Read Requirements and check the product tables against your licence. Nothing here enforces them: both routes install perfectly happily without the Optimization Toolbox, and you find out when the toolbox will not run. The environment check named in both routes below is what turns that into an answer you get on purpose.
Download MTI-Toolbox-<version>.mltbx and either
double-click it in MATLAB’s Current Folder browser,
which opens MATLAB’s add-on installer, or install it from the Command
Window:
matlab.addons.install("MTI-Toolbox-3.0.0.mltbx")That is the whole installation. MATLAB unpacks the toolbox into its
add-ons folder and puts src/, demo/,
externalTools/ and doc/ on your MATLAB path,
with their subfolders — you do not run addpath, and you do
not need to save the path.
Run this before anything else:
environmentCheckerIt reports every product and package the toolbox depends on, says
whether each one is available to you, and — when one is not — what to do
about it. For a MathWorks product it separates not installed
from installed but no licence available, because only the
second one is your licence administrator’s problem. See environmentChecker.
The installer registers the toolbox documentation with MATLAB, so the
pages you are reading now are available offline inside MATLAB, under
Supplemental Software in the Help browser. Every
documented function also carries a Documentation: link at
the end of its help text that opens its page there.
Then try a demo — every entry in the demo
catalogue has a one-line openDemo command you can copy
into the Command Window.
Uninstall it the way you would any add-on: on the
Home tab, open Add-Ons, then
Manage Add-Ons, and remove MTI-Toolbox. From the
Command Window, matlab.addons.installedAddons lists what is
installed and matlab.addons.uninstall takes it away.
Download MTI-Toolbox-<version>-source.zip and
unzip it. It unpacks to a single folder named for the release,
MTI-Toolbox-<version>/, so it cannot scatter itself
over whatever directory you unzipped in.
Move that folder to where you want to keep it before the next step. The path entry you are about to add points at wherever the folder is, so unpacking into a downloads directory and adding it from there is a surprise you meet later.
Point these two lines at wherever you put the folder:
addpath(genpath("C:\Toolboxes\MTI-Toolbox-3.0.0"))
savepathgenpath gives you the same set of folders the installer
would have added. savepath makes it survive a restart.
Warning: If savepath cannot write
savepath needs permission to write MATLAB’s path file,
and a locked-down installation — quite possibly the reason you are on
this route — may not give it. Put the addpath line in your
startup.m
instead; it then runs at every MATLAB start.
Run this before anything else:
environmentCheckerIt reports every product and package the toolbox depends on, says
whether each one is available to you, and — when one is not — what to do
about it. On this route it also confirms the path step above worked,
since it can only run once src/ is on the path. See environmentChecker.
This route gets no Help-browser integration. Nothing
registers the pages with MATLAB, so they do not appear under
Supplemental Software, and doc will not find them.
That is expected rather than a failed installation — and it is why the
archive carries its own documentation:
MTI-Toolbox-Manual-<version>.pdf,
in the folder you unpacked. The complete documentation as one printable
manual.doc/html/, the same pages as HTML, for
reading in a browser. Each function’s Documentation: help
link opens its page from here, in MATLAB’s browser, exactly as on the
other route.index.md, the documentation landing
page, as the short orientation.Then try a demo — every entry in the demo
catalogue has a one-line openDemo command you can copy
into the Command Window.
rmpath(genpath(...)) on the same folder you added, then
savepath, then delete the folder. Nothing was installed
anywhere else.
One capability — multilinearizing a Simulink model with
mlinearize — needs a third-party package, the Sparse Grids
MATLAB Kit. You do not have to obtain it: it ships inside both
forms, in its own folder under externalTools/, so
a normal installation puts it on your path with everything else.
It stays listed as a gated capability on the Requirements page regardless, because
shipping a package says how it reaches you, not whether the toolbox
needs it — and an installed copy can still be deleted. That is one of
the things environmentChecker looks for.
MyToolbox Documentation | Generated automatically by CI/CD pipeline