Create Sdi Run
Import data into the Simulation Data Inspector (SDI) from MAT, CSV, or Excel files...
Install
npx skills add matlab/simulink-agentic-toolkit --skill create-sdi-run -g -a claude-code -y- Repository
- matlab/simulink-agentic-toolkit1.3k
- Category
- Documents
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Import data into the Simulation Data Inspector (SDI) from MAT, CSV, or Excel files, from workspace variables, or from a Simulink simulation. Use when the user wants to view a logged file in SDI, load a bench-test log, or verify what a just-completed `Simulink.sdi.createRun` or `sim(model)` produced. Covers the `'file'`, `'vars'`, and `'namevalue'` sources of `createRun`, the auto-populate behavior after `sim()`, and post-import verification. Not for comparing existing runs (use `Simulink.sdi.compareRuns`); not for streaming data live during a running simulation (use `Simulink.sdi.createRunOrAddToStreamedRun`, a separate API); and not for authoring Gherkin or Simulink Test test cases, assertions, or regression tests (use `testing-simulink-models`). Do not activate on test-authoring or verification prompts even when no test-authoring skill is available, say so and stop.
Create SDI Run
Get data into the Simulation Data Inspector using the shortest path that works. Most agents reflexively read files into the workspace and rebuild signals by hand; this skill teaches the direct paths and when each applies.
When to Use
- User has a
.mat,.csv, or.xlsxfile of logged data and wants to view it in SDI. - User just ran
sim(model)and wants to see the logged signals. - User has
timeseries,timetable, orSimulink.SimulationData.Datasetvariables in the workspace and wants an SDI run. - User asks about
Simulink.sdi.createRun,Simulink.sdi.getAllRunIDs, orSimulink.sdi.getRun.
When NOT to Use
- Comparing two existing runs, that is a distinct workflow (
Simulink.sdi.compareRuns). - Streaming data live during a running simulation, this is a separate API (
Simulink.sdi.createRunOrAddToStreamedRun), not a mode ofcreateRun. Prompts like "stream data into SDI while my sim is running" belong to that API. Do not activate on those. - Files in MDF (
.mf4), ULG, ROS bag, CAN log, or HDF5 formats, see references/format-support.md for what SDI reads natively vs. what needs a different toolbox. - Customizing plot layout, cursors, or subplot arrangement beyond opening the SDI window.
- Authoring Gherkin
.featurefiles, Simulink Test cases,matlab.unittestclasses, or any pass/fail assertions or regression tests for a model or subsystem, usetesting-simulink-models(Gherkin-basedmodel_test, requires Simulink Test). Prompts like "write a Gherkin test for X", "verify abs(-5) equals 5", "create a regression test for this subsystem", or any request whose deliverable is a test artifact belong there. Do not activate this skill on such prompts even whentesting-simulink-modelsis unavailable, in that case, tell the user which skill is missing and stop.
Workflow
Answer these four questions in order. The first "yes" tells you what to do.
