What problem does it solve?
Getting logged data into Simulink's Simulation Data Inspector (SDI) is error-prone: agents often manually read MAT/CSV/Excel files and rebuild signals by hand, create duplicate runs after sim(), or hit cryptic import errors from misnamed time columns. This Skill encodes the direct Simulink.sdi.createRun paths and the verification steps that prevent silent failures.
Core Features & Use Cases
- File import in one call: Load
.mat, .csv, and .xlsx files directly via the 'file' source, including multi-sheet Excel workbooks that return one run per sheet.
- Workspace variable import: Use
'vars' for named timeseries/timetable data or 'namevalue' for bare arrays, with guidance on the timeseries.Name precedence gotcha.
- Post-simulation handling: Detect SDI auto-population after
sim(model) using getAllRunIDs to avoid duplicate runs, and verify every import with SignalCount checks.
- Use Case: A user has a bench-test log
bench_run.csv whose time column is named Timestamp. The Skill tries the direct file import, catches SDI:sdi:ImportError, and falls back to a readmatrix + array2timetable + 'vars' pattern without modifying the source file.
Quick Start
Ask your agent to import the file 'logs/bench_test.mat' into the Simulation Data Inspector and verify the run's signal count.