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 .xlsx file 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, or Simulink.SimulationData.Dataset variables in the workspace and wants an SDI run.
• User asks about Simulink.sdi.createRun, Simulink.sdi.getAllRunIDs, or Simulink.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 of createRun. 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 .feature files, Simulink Test cases, matlab.unittest classes, or any pass/fail assertions or regression tests for a model or subsystem — use testing-simulink-models (Gherkin-based model_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 when testing-simulink-models is unavailable — in that case, tell the user which skill is missing and stop.