LabKit MATLAB Workbench

overview

LabKit Apps

LabKit apps are independent MATLAB tools for complete laboratory workflows. Choose an app by the result you need, then use its app page for supported inputs, controls, interaction behavior, calculations, outputs, recovery, and programmatic APIs.

Start An App

Open labkit_launcher, select one app, and choose Open. The launcher's Documentation and History action opens the selected app page.

Source-checkout users can also call an app command after adding LabKit to the MATLAB path:

labkit_launcher
% Or, after repository path setup:
labkit_CIC_app

See Getting Started for installation, updating, version selection, and source-checkout setup. The LabKit Launcher manual documents its complete interactive and programmatic surface.

Choose An App

TaskAppInputPrincipal output
Discover, install, launch, diagnose, and package LabKit appsLabKit LauncherInstalled or source LabKit treeRunning app, maintenance report, or deployment ZIP
Register, crop, and mask image pairs for DICDIC PreprocessReference and moving imagesAligned images, crops, mask
Render and summarize Ncorr strain resultsDIC PostprocessNcorr MAT, reference image, maskStrain overlays and summary CSV
Overlay chrono voltage and current tracesChrono OverlayChrono DTAPlot and CSV
Measure charge-injection capacityCICChrono DTACIC result table and CSV
Compare cyclic and time-domain CSCCSCCV/CT DTAPer-cycle CSC and CV data
Inspect impedance curvesEISEIS DTANyquist/Bode plots and CSV
Estimate voltage-transient resistanceVT ResistanceChrono DTAResistance table and CSV
Convert tracked points into gait metricsGait AnalysisCurrent Video Marker project MATFrame, step, coordinate, and summary tables
Crop image batches at repeatable geometryBatch Image CropImage filesSame-size crops and manifest
Measure curve radius, curvature, and lengthCurvature MeasurementImageOverlay and measurement CSV
Decode and measure radiometric imagesFLIR ThermalFLIR radiometric imageTemperature data, measurements, rendered image
Fuse focal planesFocus StackAligned image stackFused image and focus map
Apply a repeatable enhancement pipelineImage EnhanceImage filesEnhanced images and manifest
Match appearance to a reference imageImage MatchSource and reference imagesMatched images and manifest
Annotate ordered landmarks across videoVideo MarkerVideoProject MAT and coordinate CSV
Restyle figures and export visible plot dataFigure StudioFIG or popout axesStyled figure and plot data
Inspect RHS recordings and define channelsRHS PreviewRHS file or folderPreview, protocol JSON, filter record
Detect trains and measure neural responsesNerve Response AnalysisFilter record and protocol JSONAnalysis JSON and CAP metrics
Review aligned responses and statisticsResponse Review and StatsAnalysis JSON or segment CSVMetrics CSV and summary
Compare multiple groups with the first using t-tests and one mean/SD plotT-Test WizardCSV, TSV, workbook, or entered valuesResult family, CSVs, and comparison plot
Inspect ECG and measure segment SNRECG PrintMAT or delimited tableSegment SNR CSV and waveform image

Browse By Family

How To Read An App Page

Concrete app pages use a common MATLAB-style order:

  1. purpose, requirements, and launch command;
  2. supported inputs and the shortest successful workflow;
  3. controls and interaction behavior;
  4. calculation or algorithm semantics, units, and assumptions;
  5. outputs, project files, autosave, and recovery behavior;
  6. GUI-free MATLAB examples and public app-owned APIs;
  7. errors, limitations, troubleshooting, related topics, and history.

The app page documents stable user-visible behavior. Exact callable syntax and data shapes live on the linked API reference pages. Internal callbacks and private implementation helpers are intentionally omitted.

Shared framework contracts are documented once in the App Framework, not repeated in every App page. An App page mentions shared behavior only when that App changes it or when the behavior is necessary to complete the App's workflow.

Common App Behavior

The App Framework owns lifecycle, busy state, file selection, state snapshots, screenshot actions, plot tools, and managed interactions. Apps own scientific choices, workflow-specific defaults, result schemas, and exports. See the App Framework for behavior shared across apps.

Action and input-selection buttons provide concise hover help. The shared Tools menu contains plot, screenshot, and project-state actions when the corresponding capability is available.

Input data and exported results should remain outside the replaceable LabKit runtime folder. Apps do not overwrite source files unless an app page states an explicit in-place operation.

Programmatic Use

Important scientific and deterministic app operations can be called without opening the GUI. Each app page identifies its supported app-owned functions and links them to the generated API Reference. Reusable file parsers and generic processing functions live in the public labkit.* libraries.

MATLAB must be able to see both the repository root and the owning app root. The launcher prepares these paths automatically. In a source checkout, add them explicitly before calling an app package:

repoRoot = "/path/to/LabKit-MATLAB-Workbench";
addpath(repoRoot)
addpath(fullfile(repoRoot, "apps", "electrochem", "cic"))

help cic.analysisRun.computeCIC

For another app, replace the final app path with the directory that directly contains its +package folder. Do not add every repository subfolder with genpath; app roots are independent and may contain same-named private or development files that should not become global MATLAB commands.