tutorial
Getting Started
This guide covers the shortest path from an empty folder to a running LabKit app. For source development, continue with the development guide.
Requirements
- A supported MATLAB installation.
- Internet access for the first launcher download or update. Installed source and P-code packages run offline unless an app's own input lives on a network drive.
- Any MathWorks products declared by the selected app. The launcher shows app requirements before launch.
Production apps do not create Python or Conda environments, download model weights, or install third-party packages on first use.
Install And Launch
- Download the latest
labkit_launcher.m. - Put it in a standalone folder such as
LabKit/. - Open MATLAB in that folder.
- Run:
labkit_launcher
The launcher can install or update the runtime, discover available apps, and start the selected app. Keep experimental data and exported results outside the LabKit runtime folder. See the LabKit Launcher manual for every button, programmatic mode, discovery rule, and maintenance action.
Choose A Version
- Release installs the latest stable GitHub release.
- Latest installs the current
mainbranch. - Versions selects a recent release, tag, or commit for a deliberate upgrade or rollback.
Before replacing an installed runtime, the launcher moves its current contents to a dated LabKit-previous-* folder. This provides a local recovery point but is not a substitute for backing up lab data.
Open An App
Select one row in the launcher and choose Open. The launcher prepares the MATLAB path, checks the app's LabKit version requirements, and displays startup progress until the app is ready.
Use the app catalog to choose a workflow and confirm its input and output formats.
Common App Commands
Every current LabKit app exposes one top-level Tools menu:
- Tools > Plots contains plot-specific actions such as opening larger editable views, copying plots, and saving plots.
- Tools > Screenshot > Copy to Clipboard copies the complete active App surface as an image.
- Tools > Screenshot > Save to File... saves the complete App surface.
- Tools > Project State > Save State... writes the current project document.
- Tools > Project State > Load State... opens a compatible project document.
State files preserve app projects. They are different from exported result files and from ignored diagnostic manifests under artifacts/diagnostics/.
Source Checkout
Clone the repository only when you need source development, tests, profiling, or review:
git clone https://github.com/Pluze/LabKit-MATLAB-Workbench.git
cd LabKit-MATLAB-Workbench
buildtool headless
See Testing before choosing a broader build task.
Next Steps
Change history
- 2026-07-20 - Launcher adopts the App SDK diagnostic launch contractfeat | compatible
- 2026-07-19 - Documentation structure becomes the navigation contractrefactor | compatible
- 2026-07-16 - Launcher reads the single App definitionrefactor | compatible
- 2026-07-16 - Launcher and maintainer tool manualsdocs | compatible
- 2026-07-15 - Searchable MATLAB-generated documentation site and launcher workflow groupsfeat | compatible
- 2026-07-13 - Launcher app version historyfeat | compatible
- 2026-07-09 - Multi-app launcher packagesfeat | compatible
- 2026-07-07 - Debug workflows, launcher tools, and changelog governancefeat | compatible
- 2026-07-06 - UI 5 facade redesign, app migration, and plot refreshrefactor | breaking
- 2026-07-02 - Startup responsivenessperf | compatible
- 2026-07-02 - Profiling and validation speedupsci | compatible
- 2026-07-01 - Launcher code-analysis exportfeat | compatible
- 2026-07-01 - Image app workflow improvementsfeat | compatible
- 2026-07-01 - Launcher update reliabilityfix | compatible
- 2026-06-29 - UI diagnostics and release v3.0.0feat | compatible
- 2026-06-28 - App diagnostics and hardened UI workflowsfeat | compatible
- 2026-06-26 - Launcher manager and stale callback fixfix | compatible
- 2026-06-23 - Version metadata baselinefeat | compatible