Simulink Check Rapid Accelerator Compatibility
Statically analyze a Simulink model for Rapid Accelerator (raccel) mode incompatibilities.
Install
npx skills add matlab/simulink-agentic-toolkit --skill simulink-check-rapid-accelerator-compatibility -g -a claude-code -y- Repository
- matlab/simulink-agentic-toolkit1.3k
- Category
- Engineering
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Statically analyze a Simulink model for Rapid Accelerator (raccel) mode incompatibilities. Identifies unsupported blocks (Interpreted MATLAB Function, Level-2 S-Functions without TLC), configuration issues, and data type restrictions that prevent code generation. Classifies each issue as BLOCKER (build error) or WARNING (build warning). Use BEFORE calling sim() in rapid-accelerator mode, when buildRapidAcceleratorTarget fails, or when the user asks "why won't my model run in raccel?" TRIGGER: any request explicitly involving rapid accelerator mode, raccel, raccel build errors, or buildRapidAcceleratorTarget failures.
Checking Rapid Accelerator Compatibility
Statically analyze a Simulink model for all raccel incompatibilities in one pass, without iterative build-fail-fix cycles.
When to Use
- User wants to simulate a model in Rapid Accelerator mode
buildRapidAcceleratorTargetfails with errors- User asks "why won't my model run in raccel?"
When NOT to Use
- Model is only intended for Normal or Accelerator mode, use
simulating-simulink-modelsinstead - User is debugging a runtime error (model builds fine but crashes), exception: if the model crashes in raccel, run this check anyway; the root cause may be a static incompatibility that manifests as a runtime crash
- Issue is purely a compiler/toolchain problem (not model content)
- General code generation for GRT/ERT targets (not raccel-specific)
- Model Advisor checks (separate workflow)
- SIL/PIL/HIL or Simulink Real-Time deployment
All script functions are in the skill's scripts/ directory. Use evaluate_matlab_code with project_path set to the skill's scripts/ folder so MATLAB can find them. Never use addpath.
Diagnostic Workflow
Detect all incompatibilities statically, by parsing model structure, block parameters, data types, and configuration, without calling buildRapidAcceleratorTarget. This finds all issues in one pass.
Two-phase workflow: Phase 1 (Steps 1, 3a) produces the compatibility report, your response MUST END there. Phase 2 (Steps 3b, 3c) applies fixes one at a time, each requiring a separate user confirmation. Never combine both phases in one response.
Step 1: Static Inspection (primarily MCP tools)
Gather model information using MCP tools in parallel:
1a. Read block topology via model_read:
model_read(model: "ModelName", scope: "root", depth: "inf")
From the output, immediately flag blocks with these BlockType values:
