matlab-simulate-radar-detections
Configure, simulate, debug, and analyze radarDataGenerator within radarScenario. Use for: interactively building radar detection scenarios from datasheets or performance requirements; diagnosing missed detections and configuration errors; interpreting sensor spherical, body, and scenario-frame outputs; deriving ReferenceRange from hardware specs via link budget; scan mode configuration (mechanical, electronic/AESA, hybrid); and validating simulation results against analytical predictions.
npx skills add matlab/matlab-agentic-toolkit --skill matlab-simulate-radar-detections --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Build detection-level radar simulations using radarDataGenerator within radarScenario. This skill bridges user hardware specs and performance requirements to the Radar Toolbox statistical simulation API.
How it works
Follows a structured 9-step interactive workflow:
- Step 1: Recommend statistical-level simulation with
radarDataGeneratorinsideradarScenario; mention alternatives if I/Q fidelity is needed. - Step 2: Confirm use case, including scan type, coordinate frame, configuration, and propagation environment; offer atmosphere models via
atmosphere(scenario, model)as applicable. - Step 3: Determine sourcing direction (top-down, bottom-up, mixed) and branch accordingly using datasheet ingestion in
references/coupled-parameters.mdwhen applicable. - Step 4–9: Execute target-set design steps, presenting reference performance, coupled-parameter tables, geometry, sanity checks with horizon and Pd estimates, terrain/occlusion options, simulation duration, and finally produce a requirements sheet via the template at
references/requirements-sheet-template.md. - Key functions listed include:
radarScenario,radarDataGenerator,platform,waypointTrajectory,kinematicTrajectory,geoTrajectory,radareqrng,radareqpow,radareqsnr,detectability,horizonrange, and others.
When to use it
Use when you have radar hardware specs or performance requirements and want to build a statistical detection simulation for moving targets, compare scan strategies, perform Monte Carlo analyses, or validate against analytical predictions. Use when you need to feed detections into a tracker or perform sensor fusion, and when you want to validate against a link-budget prediction.
What it can touch
The workflow relies on a suite of functions in the Radar Toolbox, including:
radarScenarioandradarDataGeneratorfor the core simulation container and sensor model- trajectory tools:
platform,waypointTrajectory,kinematicTrajectory,geoTrajectory - detection and SNR utilities:
detect,detectability,radareqrng,radareqpow,radareqsnr - environmental and geometry helpers:
atmosphere,horizonrange, terrain/occlusion tools such aslandSurface,occlusion,HasOcclusion, etc.
Caveats
License: license is declared as NOASSERTION. The skill notes defaults like FreeSpace propagation and the need to choose appropriate atmosphere models; signal-level fidelity is outside scope (CFAR/beams). If a mismatch occurs in Pd at reference range, the flow instructs diagnosing and flagging, not guaranteeing outcomes. Source references include external markdown documents for steps and tables, but the agent should not assume any implicit outputs beyond what is stated in the workflow.
# Radar Data Generator — Statistical Detection Simulation Build detection-level radar simulations using `radarDataGenerator` within `radarScenario`. This skill bridges user hardware specs and performance requirements to the Radar Toolbox statistical simulation API. ## When to Use - User wants to simulate radar detections on moving targets - User has radar hardware specs (datasheet) or performance requirements and wants to build a simulation - User mentions surveillance radar, scanning, revisit time, detection probability, or radar coverage - User wants to compare scan strategies (mechanical vs electronic vs hybrid) - User wants to generate detections to feed a tracker (trackerGNN, trackerJPDA) or do sensor fusion - User wants Monte Carlo analysis, trade studies, or validation against link budget predictions - User is studying radar placement or geometry to maximize coverage - User has existing `radarDataGenerator` code that isn't working — missed detections, configuration errors - User wants to validate simulation results against expected performance ## When NOT to Use - User needs I/Q-level waveform simulation (use `radarTransceiver` + pulse-Doppler chain) - User needs CFAR detect
- When to Use
- When NOT to Use
- Detection Pathways
- Workflow
- Step 1: Recommend Approach
- Step 2: Confirm Use Case
- Step 3: Ask Parameter Sourcing Direction
- Step 4: Propose Reference Performance
- Step 5: Present Coupled-Parameter Table
- Step 6: Target Set Design
- Step 7: Terrain / Occlusion
- Step 8: Simulation Duration
- Step 9: Produce Requirements Sheet
- Key Functions
What does the matlab-simulate-radar-detections skill do?
Configure, simulate, debug, and analyze radarDataGenerator within radarScenario. Use for: interactively building radar detection scenarios from datasheets or performance requirements; diagnosing missed detections and configuration errors; interpreting sensor spherical, body, and scenario-frame outputs; deriving ReferenceRange from hardware specs via link budget; scan mode configuration (mechanical, electronic/AESA, hybrid); and validating simulation results against analytical predictions.
How do I install it?
Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-simulate-radar-detections --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From matlab/matlab-agentic-toolkit, a repository with 868 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
