deepstream-run-mv3dt

Run and operate the DeepStream Multi-View 3D Tracking reference app with samples, custom datasets, and Kafka metadata.

2|Updated Aug 20, 2026
One-click install
npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill deepstream-run-mv3dt-atomicrajat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepstream-run-mv3dt
Source: https://github.com/atomicrajat/industry_safety_monitoring_system/tree/main/.claude/skills/deepstream-run-mv3dt
Command: npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill deepstream-run-mv3dt-atomicrajat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up and running NVIDIA's DeepStream Multi-View 3D Tracking (MV3DT) reference app involves many fragile steps: resolving the app checkout, preparing datasets and calibration, generating configs, choosing display versus headless modes, and verifying Kafka/BEV outputs. This Skill guides an agent through that entire workflow safely and reproducibly. ## Core Features & Use Cases - Sample Runs: Launch the shipped 4-camera or 12-camera MV3DT samples in display or headless mode with correct detector and tracker configs. - Custom Datasets: Run MV3DT on your own synchronized MP4 files, delegating missing camera calibration to the AutoMagicCalib skills and normalizing modelInfo for the selected detector. - Visualization & Metadata: Inspect the OSD grid, capture BEV videos offline from Kafka, and verify tracking metadata on the mv3dt topic. - Use Case: You have six synchronized warehouse camera MP4s but no calibration files. The Skill stages the videos, hands off calibration to AutoMagicCalib, lands the export, generates configs, and runs DeepStream headlessly with saved tiled and BEV MP4 outputs. ## Quick Start Ask the agent to run the DeepStream MV3DT 4-camera sample and show the OSD and BEV outputs.

Frequently Asked Questions about deepstream-run-mv3dt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the DeepStream MV3DT sample app?

Resolve the deepstream-tracker-3d-multi-view app directory, verify prerequisites with the setup script's check-only mode, then run the 4-camera sample by default. Display mode shows OSD and BEV windows; headless mode saves a tiled MP4 and a Kafka-derived BEV MP4.

How do I run MV3DT on custom synchronized MP4 videos?

Place videos under a dataset's videos directory with matching camInfo calibration files, then generate configs with the auto-configurator and launch DeepStream in Docker. If calibration is missing, the workflow delegates to AutoMagicCalib and normalizes modelInfo for your chosen detector.

Which detectors does DeepStream MV3DT support?

MV3DT supports PeopleNetTransformer as the default people detector, RTDETR as a warehouse multi-class detector, and PeopleNet v2.6.3. The selected DETECTOR_MODEL drives both config generation and calibration modelInfo normalization.

Can I run MV3DT headlessly over SSH without a display?

Yes, headless mode generates configs with file output and message broker enabled, producing a tiled DeepStream MP4 and an offline BEV MP4 captured from Kafka. No X11 display is required for this path.

Why is my BEV video empty after an MV3DT run?

Empty BEV output usually means the offline capture started too early or too late relative to the DeepStream launch, or Kafka offsets never advanced. Start a fresh capture with --from-end immediately before the Docker launch and verify nonzero message and frame counts in the capture log.

Why does MV3DT require docker run with --privileged and --net=host?

The reference launch uses those flags for broad device, network, and mounted-repo access, so the Skill requires explicit user approval before executing. It also documents least-privilege alternatives such as --gpus all, specific device mounts, and explicit port mappings.