Generated banner for Matlab Prepare Signal Data
Generated logo for Matlab Prepare Signal Data

Matlab Prepare Signal Data

MathWorksOfficialCreated by MathWorks

  • Skill
  • Tool integration
  • Data and AI
  • BSD-2-Clause
  • No issues found

From the author

Use this skill when conditioning, loading, preparing, or labeling signal data for analysis or ML training. Covers: cleaning a single signal (fill gaps, remove drift, deoutlier, denoise, resample/align a time base) BEFORE analysis; building a `signalDatastore` pipeline; creating a `labeledSignalSet` for Signal Labeler; deriving labels (filename, folder, in-file, ROI, time-frequency ROI); stratified train/val/test splits; framing long signals; parallel processing; and shaping datastore output for `trainnet`. Triggers include "clean up this signal", "remove drift / detrend", "fill gaps", "remove spikes / outliers", "denoise", "resample to a uniform rate", "align channels", "labels from filenames", "stratified split", "prepare for Signal Labeler", and function names like `fillgaps`, `fillmissing`, `detrend`, `filloutliers`, `smoothdata`, `resample`, `synchronize`, `signalDatastore`, `labeledSignalSet`, `filenames2labels`, `folders2labels`, `splitlabels`, `framesig`, `framelbl`, `createDatastores`.
— the description by MathWorks

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to signal data preparation, guiding users through the lifecycle of cleaning raw signals, managing datastores, applying labels, and partitioning data for machine learning. It emphasizes using high-level Signal Processing Toolbox functions to ensure readability and maintainability, while offering clear heuristics for ordering conditioning steps like detrending, smoothing, and outlier removal. The skill is designed to help users move from raw data to a ready-to-train state for models like trainnet.

What it does

  • Cleans signals by filling gaps, removing drift, denoising, and handling outliers.
  • Synchronizes and resamples multi-channel data onto a uniform time base.
  • Builds data pipelines using signalDatastore for efficient loading.
  • Creates labeledSignalSet objects for structured labeling and Signal Labeler interoperability.
  • Performs stratified splits and framing for long signal sequences.
  • Shapes and prepares datastore outputs for machine learning workflows.

When to use it

  • When you need to clean a single signal before analysis or training.
  • When preparing a dataset of signals for machine learning with specific labeling requirements.
  • When you need to align multiple signal channels or resample them to a uniform rate.
  • When you need to partition signal data into training, validation, and test sets.
  • When you need to frame long signals for windowed analysis or supervision.

Advantages

  • Promotes readable, maintainable code by preferring high-level toolbox functions.
  • Provides a logical, verified order for conditioning steps to prevent data corruption.
  • Reduces manual effort by automating common tasks like label derivation from filenames.
  • Ensures compatibility with Signal Labeler and deep learning training functions.
  • Offers clear guidance on when to escalate to lower-level methods.

Usage examples

“How do I remove a linear trend from my signal?”
The agent will recommend using detrend(x, 1) and explain why explicit degree specification is preferred for code clarity.
“I have a folder of signal files; how do I create a datastore and split them for training?”
The agent will guide you through using signalDatastore to load the files, followed by splitlabels to perform a stratified split.
“My signal has gaps; how should I fix them?”
The agent will suggest using fillmissing for short gaps or fillgaps for longer gaps in oscillatory signals, depending on the signal characteristics.
“How do I align two signals with different sampling rates?”
The agent will recommend using the synchronize function to place both signals onto a shared time grid.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/matlab/matlab-prepare-signal-data/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip matlab-prepare-signal-data.zip -d .agents/skills

Documentation by MathWorks

Prepare Signal Data

Look in Signal Processing Toolbox first. The conditioning, labeling, splitting, framing, and partitioning helpers here live in Signal Processing Toolbox — not in Stats & ML Toolbox or generic-MATLAB string utilities.

The arc: condition a raw signal (clean it) -> load a folder into a datastore -> label -> split / frame -> hand off to trainnet. Each stage is a workflow file; this page routes you to the right one.

When to Use

  • Cleaning a single signal before analysis: fill gaps, remove drift, deoutlier, denoise, put it on a uniform time base, align multiple channels.

  • Loading / preparing signal data for ML training: datastores, labels from filenames or folders, stratified splits, framing, parallel processing.

  • Structured labeling: labeledSignalSet for Signal Labeler, all label types.

When NOT to Use

  • Raw .wav audio classification with Audio Toolbox available. audioDatastore is the canonical path (this skill's custom-ReadFcn workflow handles .wav only when Audio Toolbox is absent — references/wf-custom-readfcn.md).

  • Frequency-selective filter DESIGN (band isolation, notch, custom FIR/IIR) — see the matlab-design-digital-filter skill. This skill's conditioning is about cleaning, not designing filters.

  • Computing per-frame features (RMS, crest factor, spectral / bandwidth, time-frequency features) from an already-conditioned signal — see the matlab-extract-signal-features skill. This skill's framesig / framelbl are for manual per-window labeling / supervision, not for deriving a feature table; the signal*FeatureExtractor objects window internally and emit the table.

Best practices

  • Deliverable is a runnable .m script the user can save, version, and re-run — not workspace state.

  • Prefer the highest-level function that does the job. detrend / smoothdata / fillmissing / resample read cleanly and are easy for a non-expert to follow. Drop to a lower-level / more-configurable path (designfilt + filtfilt, a hand-built AR model, a named primitive) only when you need control the high-level call cannot give, or when the user asks. Readability first; escalate to low-level for necessity, not by default.

    • The high-level call usually exposes the control you think you need. In particular smoothdata(x, "sgolay", fl) takes the frame length fl as an argument — it does NOT hide it — so prefer it over calling sgolayfilt directly. Reach for sgolayfilt only for what the dispatcher genuinely lacks (derivative output via dn, or an unusual polynomial order).

0. Common reflexes

If your first instinct is one of these, the canonical replacement is one row away.

ReflexCanonicalDetail
Hand-design a highpass/designfilt to remove a smooth driftdetrend(x, n) — escalate n = 1 -> 2 -> 3 before reaching for a filter; polynomial detrend has unity passband gainreferences/fn-detrend.md
Invent a gap-filler (regularizeNaNs, inpaintn — not real)fillmissing (interp) for short gaps; fillgaps (SPT, AR) for long gaps in oscillatory signalsreferences/wf-repair-missing.md
Hand-roll retime + shift + retime + concat to align channelssynchronize(A, B, ...) — one call to a shared gridreferences/wf-align-channels.md
Custom ReadFcn for a .csvsignalDatastore default reader + SignalVariableNamesreferences/fn-signaldatastore.md
cvpartition for a datastore splitsplitlabels + subset(ds, idx{k})references/fn-splitlabels.md
regexp / extractBefore / fileparts for labels from filenamesfilenames2labels(sds, Extract=...)references/fn-filenames2labels.md
regexp / nested fileparts for labels from subfoldersfolders2labels(sds.Files)references/fn-folders2labels.md
Manual framing loop with (i-1)*hop+1framesig(x, fl, OverlapLength=...)references/wf-frame-and-label.md
Manual ROI-to-frame vote with containers.Mapframelbl(rois, ...)references/wf-frame-and-label.md
for loop load(file) to read in-file label variablessignalDatastore(folder, SignalVariableNames=["x","label"])references/fn-signaldatastore.md
signalMask when you need Signal Labeler interoplabeledSignalSet with ROI labels (signalMask can't import)references/fn-labeledsignalset.md
signalLabeler(lss) (pass the set as an arg)Launch bare signalLabeler (zero args), then Import -> From Workspace or From Filereferences/wf-label-and-export.md

SPT-specialized functions exist — reach for them, don't reinvent. fillgaps (AR gap fill), medfilt1 / hampel (impulse handling), sgolayfilt / smoothdata(...,"sgolay") (feature-preserving smoothing) are in Signal Processing Toolbox.

1. Workflows

Each workflow file is the entry point and lists the functions it uses. Start here.

WorkflowUse whenReference
Repair missing samplesNaN gaps / dropouts to fill.references/wf-repair-missing.md
Detrend, smooth, deoutlierDrift, spikes, and/or broadband noise on one signal (smoothing/denoising lives here).references/wf-detrend-smooth-deoutlier.md
Align multi-rate / offset channelsSeveral channels onto a shared time base.references/wf-align-channels.md
Put one channel on a uniform rateOne channel -> uniform grid at a chosen rate: jittery timestamps to regularize, OR already uniform but the wrong rate to resample.references/wf-uniform-rate.md
Wavelet denoising (escalation)Non-stationary/multi-scale noise a tuned sgolayfilt can't remove; wdenoise (Wavelet TB).references/wf-denoise.md
Envelope extractionAmplitude outline (AM demod, peak hull) — not cleaning.references/wf-envelope.md
Load + label + splitFolder of files -> datastore for training.references/wf-load-and-split.md
Frame long signals + per-frame labelsLong signals, per-window supervision.references/wf-frame-and-label.md
Label + export (all label types)Structured labels (attribute/ROI/point/TF-ROI), export to Signal Labeler / DL.references/wf-label-and-export.md
Parallel processing across a parpoolPer-signal work across workers.references/wf-parallel-process.md
Custom ReadFcn (only when needed)Format isn't .mat / .csv, or has a metadata prelude.references/wf-custom-readfcn.md
Hand-off to trainnetDatastore ready; shape for trainnet / combine.references/wf-handoff-to-dl.md

Each workflow file names the fn- reference pages for the functions it uses; there is no separate function index — enter through the workflow that matches your task, or the reflex table above.

2. Ordering when a signal needs several conditioning steps

The governing principle (this is the real rule): order the steps so an earlier operation does not corrupt the input to a later one. Spikes bias least-squares fits and get smeared by filters/resamplers; an un-removed trend gets averaged into the signal by a smoother; most operations choke on NaN. Reason from that for the signal in front of you — do not follow a fixed chain blindly.

Default heuristic (a good starting order, not a universal law):

outliers -> detrend -> smooth, with fill and align placed by the principle above.

  • outliers -> detrend -> smooth is the verified core: remove spikes before a polynomial detrend (a spike biases the fit) and before a smoother (a smoother spreads the spike across its window); detrend before smooth so the smoother isn't averaging across a trend.

  • Fill NaN before any step that can't handle missing data (detrend, filters, most smoothers).

  • Align / resample: putting a signal on a new grid (retime/synchronize) creates NaN at non-overlapping times, so fill after aligning. BUT if the signal has spikes, deoutlier before resampling — resample's anti-alias filter will smear an un-removed spike. So align-vs-outliers order depends on the signal; the principle decides, not a fixed sequence.

Not every signal needs every step — identify which apply, order them by the principle, and each workflow file has an off-ramp if your problem is actually a different family.


Copyright 2026 The MathWorks, Inc.


Files

references/fn-synchronize.md

Function: synchronize

Used in: wf-align-channels.md Toolbox: MATLAB (base) — timetable method

The one-shot merge primitive for bringing several timetables onto a shared time base. It collects the variables from all input timetables, builds a common time vector, adjusts each variable onto it, and returns a single timetable.

Reach for synchronize whenever you have two or more timetables at different rates or offsets that need to become one aligned table. Do not hand-orchestrate retime per channel and then concatenate — that is the multi-step path synchronize collapses into one call.

Signature

TT = synchronize(TT1, TT2)                                  % union of times, no interpolation
TT = synchronize(TT1, TT2, newTimeBasis, method)            % common basis + adjust rule
TT = synchronize(TT1, TT2, newTimeStep, method)             % 'hourly', 'daily', ...
TT = synchronize(TT1, TT2, 'regular', method, 'SampleRate', Fs)
TT = synchronize(TT1, TT2, 'regular', method, 'TimeStep', dt)
TT = synchronize(TT1, TT2, newTimes, method)                % explicit target time vector
TT = synchronize(TT1, ..., TTN, ___)                        % N timetables at once

newTimeBasis picks where the common row times come from:

newTimeBasisCommon time vector isUse when
'union' (default)every distinct time across all inputsyou want to keep all samples and fill the rest
'intersection'only times present in every inputyou want rows that already line up, no interpolation
'commonrange'inputs' overlapping span, at union times inside ityou want the overlap only, dropping non-overlapping tails
'first'TT1's row timesyou want everything on the first table's grid
'last'TTN's row timesyou want everything on the last table's grid
'regular'a uniform grid (needs SampleRate or TimeStep)you want a clean uniform output rate

method is the adjustment rule applied to each variable at the new times. Same vocabulary as retime (see fn-retime.md): 'fillwithmissing' (default when no method given), 'linear', 'spline', 'pchip', 'makima', 'previous', 'next', 'nearest', plus aggregation rules ('mean', 'sum', ...) and 'fillwithconstant'.

Name-value pairs

NV-pairDefaultPurpose
EndValues'extrap'Extrapolation rule for interpolation methods. 'extrap' extends the trend past the data (can invent values); set to a scalar to clip instead.
Constant—Fill value when method is 'fillwithconstant'.
IncludedEdge'left'Which bin edge is included when aggregating.

The default is fill-with-missing, not interpolation

synchronize(TT1, TT2) with no method uses the union of times and inserts NaN (or NaT/<undefined>) wherever a variable has no sample. It does not interpolate.

TT = synchronize(A, B);          % union grid, NaNs at non-overlapping times

This is the honest default — it never fabricates values. It also means align typically creates missing data at times where one channel has no sample, so it precedes a fill step. See wf-repair-missing.md for the fill that follows.

To adjust onto the grid instead of NaN-filling, pass a method:

TT = synchronize(A, B, 'first', 'linear');   % B interpolated onto A's times

Gotchas

  • No method = NaN fill. If you expected interpolated values and got NaNs, you omitted the method argument. The two-argument form never interpolates.

  • 'linear' extrapolates by default. With EndValues='extrap' (the default), a channel that starts later than the common grid gets values extended backward past its first real sample. Pass EndValues=NaN (or a scalar) to refuse extrapolation, then fill deliberately.

  • 'union' keeps every time from every input — the output can be much longer than any single input and mostly NaN before filling. Use 'first'/'last'/'regular' when you want a controlled grid size.

  • Row times must be sorted and unique per input. Duplicate times need a resolution rule; synchronize errors otherwise. Deduplicate with retime/unique first.

  • All inputs must use the same time type (all duration, or all datetime). Mixed duration/datetime inputs error.

See also

  • fn-retime.md — the single-timetable sibling. synchronize is essentially retime applied across several tables at once, plus the merge.

  • fn-resample.md — for antialiased rate conversion of a signal (not a timetable merge).

  • wf-align-channels.md — the end-to-end alignment workflow.

  • wf-repair-missing.md — the fill step that follows a NaN-producing align.


Copyright 2026 The MathWorks, Inc.


Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
MathWorks
Publisher
MathWorks (Official)
Source
matlab/matlab-agentic-toolkit · skills-catalog/signal-processing/matlab-prepare-signal-data · commit 2a7f215
Licence
BSD 2-Clause License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE.md)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by MathWorks.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download matlab-prepare-signal-data.zip