What problem does it solve?
Recorded trajectory and sensor measurement data rarely matches the input formats expected by MATLAB Sensor Fusion and Tracking Toolbox, forcing users to hand-write conversion code for ground truth timetables, trackingScenarioRecording structs, and objectDetection arrays.
Core Features & Use Cases
- Truth Data Import: Converts flight logs, GPS logs, ADS-B, and AIS data into trackingScenarioRecording structs, filter tuning timetables, truth logs, or converted tables with coordinate transforms (LLA to ECEF, NED to ECEF).
- Sensor Data Import: Builds task-oriented dataFormat structs from trackerSensorSpec configurations or legacy objectDetection arrays for radar, IR, lidar, camera, ESM, and sonar measurements.
- Guided Mapping Workflow: Inspects the user's actual file, infers units and time formats, proposes a column-to-field mapping table, and iterates with the user before generating code.
- Use Case: A user has a CSV of radar detections with azimuth, range, and Doppler columns and wants to feed them to a tracker; the skill configures a monostatic radar sensor spec, queries its dataFormat, and generates code producing per-timestep structs ready for multiSensorTargetTracker.
Quick Start
Import my flight_log.csv file into a trackingScenarioRecording so I can replay the trajectories in MATLAB.