Skip to content

Getting started with a typical analysis workflow

Purpose

This guide is the shortest path from imported recordings to results that can be reviewed later. Inspect the signal and settings before relying on a summary plot or export.

Explore the built-in demo data

The Windows release build ships with a set of demo experiments. On first launch with an empty library, MonStim offers to install the demos into your managed data folder. You can also choose File > Install Demo Experiments… at any time. Installation creates fresh local catalogs and refreshes the experiment list automatically. It contains three types of synthetic signals: H-reflex recruitment, a TA/LG/force/length 100 Hz vibration intensity series, and a TA/LG/force/length stretch ramp-hold-release intensity series. They are safe to inspect, edit, exclude, and export while learning the application; they are synthetic data for testing and learning purposes only.

You are never required to keep installed demos. Select a demo experiment and use File > Delete Current Experiment (or Edit > Data Curation > Manage Data…) to remove it. The bundled ZIP remains untouched, so you can install a fresh copy later; users who decline installation will not see demo experiments in the program.

1. Import and verify the hierarchy

Import an experiment, then confirm that experiment, dataset, and session identify the intended biological and acquisition units. Read Understanding the data hierarchy for the definitions and what each level stores, then use Experiment import for the required folder layout. A dataset does not guarantee that its sessions share identical latency windows.

For a supported non-MonStim source, use File > Import using Add-on… instead. Select the source file or folder; MonStim checks enabled compatible add-ons and uses the only high-confidence match. It asks you to choose when recognition is ambiguous and refuses to overwrite an existing experiment. See Importer add-ons.

2. Inspect a representative session

Open a filtered EMG or Single EMG plot. Check the stimulus-aligned trace, channel identity, polarity, sampling rate, and response timing. Use raw traces to inspect acquisition; most amplitude methods operate on filtered, unrectified data.

3. Set and audit latency windows

Open Edit > Session > Manage Latency Windows. The live context states the active data, the representative values loaded into the draft, and the scope that Apply overwrites. Start at Session scope. Choose Dataset or Experiment only when replacing every affected child-session window set is intended. See Latency windows.

4. Choose and record an amplitude method

Choose the method specified by the analysis plan; do not switch methods merely because one gives a preferred result. Analysis methods gives the equations, units, and limits for every available method.

5. Review exclusions, notices, and M-max

Exclude recordings only with a documented reason. Review Diagnostic notices. Before using relative-to-M-max results, inspect the M-wave window and confirm that MonStim detected a plateau; see M-max algorithm.

6. Preserve an audit trail

Record the profile, window scope, amplitude method, exclusion rules, and exported-data identifier. MonStim saves annotation changes. For unexpected results, start with Troubleshooting rather than changing several settings at once.

For further reference on the main window, plot levels, reports, and common commands, see Using MonStim Analyzer.