Skip to content
cccskills
FreePublished on GitHub

bounding-boxes

Gets actor and level 3D bounding boxes and projects them into a camera image as 2D boxes — the dataset-annotation workflow. Lists box geometry, draws 3D boxes in the world via debug, or captures one camera frame and writes an annotated PNG plus a JSON of 2D boxes for matching actors. Use when the user asks to "get bounding boxes", "draw boxes around the cars", "project boxes onto the camera", or "generate a detection dataset / annotations".

The English summary is being prepared. Showing the original description.

See how to install

Files included (5)

  • SKILL.md4.2 KB
  • references/bounding-boxes.md2.2 KB
  • scripts/bounding_boxes.py9.8 KB
  • scripts/check_env.sh2.1 KB
  • scripts/env.sh1.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Bounding boxes

Paths. scripts/… and references/… below are relative to the directory holding this SKILL.md. Your working directory is the user's project, not that directory, so prefix them with its absolute path or the command is not found.

Three things: read actors' 3D boxes, draw them in the world, or project them into a camera image as 2D boxes with a JSON sidecar — the standard CARLA dataset-annotation pipeline (client_bounding_boxes.py).

Instructions

Progress:
- [ ] Step 1: Check prerequisites (bash scripts/check_env.sh), clear FAILs
- [ ] Step 2: For `project`, have a camera on the ego (create-sensor) + actors around
- [ ] Step 3: list / draw / project

Commands need CARLA_HOST/CARLA_PORT from scripts/env.sh.

Step 1: Check prerequisites

bash scripts/check_env.sh

Step 3: Boxes

source scripts/env.sh

# 3D box geometry of every vehicle
python3 scripts/bounding_boxes.py list --filter vehicle.*

# draw 3D boxes around vehicles — they track moving cars, stay 30 s (default)
python3 scripts/bounding_boxes.py draw --filter vehicle.*
python3 scripts/bounding_boxes.py draw --filter vehicle.* --seconds 60

# project vehicle boxes into a camera frame -> annotated PNG + JSON
python3 scripts/bounding_boxes.py project --camera <camera_id> --filter vehicle.* --out boxes.png

How the projection works (brief)

Capture one frame → build the camera intrinsics K from its fov + resolution → for each actor, take its 3D box's 8 world vertices (get_world_vertices), transform to camera space with the camera's inverse matrix, keep those in front, apply K → 2D points → the min/max is the 2D box. Off-frame and too-far (--max-dist) actors are skipped. Full math in the reference.

Examples

Example 1: annotate the ego camera

User says: "put boxes on the cars in the camera view"

Spawn a camera on the ego (create-sensor), then project --camera <id> --filter vehicle.* → boxes.png with green 2D boxes + boxes.json.

Example 2: how big is that actor

User says: "what are the dimensions of vehicle 137?"

list --filter vehicle.* (find 137) → its LxWxH from the extent.

Example 3: visualise in 3D

User says: "outline all the vehicles in the world"

draw --filter vehicle.* — green 3D boxes on a rendered server.

Troubleshooting

Problem: project finds no boxes Cause: no actors in front of / within --max-dist of the camera, or wrong filter. Solution: raise --max-dist, widen --filter, ensure vehicles are in view.

Problem: boxes misaligned Cause: the frame and the actor poses drifted (fast motion, async). Solution: capture in synchronous mode (set-world-settings) so the frame and poses are from the same tick.

Problem: draw shows nothing Cause: headless -nullrhi server. Solution: use a rendered server (see debug-draw).

Note: boxes always track moving actors draw re-stamps each frame for --seconds (default 30), so boxes ride moving cars automatically — the command blocks for that duration.

Outputs

  • list: box dimensions per actor.
  • draw: 3D box overlay (rendered view).
  • project: <out>.png (annotated) + <out>.json (2D boxes: id, type, xyxy).

Detail (intrinsics, world→camera transform, level boxes, lidar-to-camera) in references/bounding-boxes.md.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Adds a new ROS 2 message type to CARLA's native ROS 2 interface — the hand-written POD struct under LibCarla/source/carla/ros2/types/msg, its Fast-CDR serialize/deserialize pair, the RIHS01 type hash computed in Docker, the CdrTopicInfo registration and the type-hash test. Use when the user asks to "add a ROS message type", "support sensor_msgs/X in CARLA", "add a carla_msgs type", "why is my type hash warning appearing", or needs a message CARLA does not publish yet. There is no IDL codegen — every step is manual.

The English summary is being prepared. Showing the original description.

carla-simulator/carla-agentic-tools4Updated Sep 12, 2026

Adds a new topic to CARLA's native ROS 2 interface — a publisher (BasePublisher + PublisherImpl, topic suffix, QoS, registration in ROS2::GetOrCreateSensor, a ProcessDataFrom* entry point and its call site in the UE4 plugin) or a subscriber that lets ROS drive an actor. Also covers adding a middleware (RMW) behind IPublisherMiddleware. Use when the user asks to "publish X to ROS from CARLA", "add a ROS topic/publisher/subscriber", "make the obstacle/lane-invasion sensor publish", "add odometry to ROS", or "add another RMW".

The English summary is being prepared. Showing the original description.

carla-simulator/carla-agentic-tools4Updated Sep 12, 2026

Reads and summarises ScenarioRunner output — the criteria pass/fail tables from --output/--file, the machine-readable --json and --junit result files, and the criteria JSON written alongside a --record recording — and runs the metrics module (metrics_manager.py) to compute custom measurements over a recorded run offline, without the simulator. Use when the user asks "did the scenario pass", "why did it fail", "summarise these results", "compare these runs", or wants distance/speed/lane metrics from a recording.

The English summary is being prepared. Showing the original description.

carla-simulator/carla-agentic-tools4Updated Sep 12, 2026

Builds CARLA (branch ue4-dev, Unreal Engine 4.26) from source on Linux end-to-end — UE4 fork, the Carla server (editor C++ modules), the LibCarla Python client wheel, and content — then verifies them against a from-source server. Optionally builds the native ROS 2 interface in (ROS2=1 → --ros2, Fast-DDS/CycloneDDS/Zenoh), which is compile-time only and cannot be enabled later. Use when the user asks to "build CARLA from source", "compile CARLA ue4-dev", "set up CARLA on Ubuntu (incl. 24.04)", "build CARLA with ROS2 support", or "produce a CARLA server + client wheel". Cooking a distributable Dist/ package is a separate skill (package-carla-ue4); running the build is run-carla-server.

The English summary is being prepared. Showing the original description.

carla-simulator/carla-agentic-tools4Updated Sep 12, 2026

Builds CARLA on Unreal Engine 5.8 from the ue58-dev branch using its CMake build system — configure a preset, then build the carla-unreal / carla-unreal-editor / carla-python-api-install / launch targets — with ROS 2, DLSS, RSS and cook-scope options, and the engine-side build of the CarlaUnreal UE 5.8 fork. There is no Makefile and no Util/BuildTools in this tree, so every UE4 `make` recipe is invalid here. Use when the user asks to "build CARLA UE5", "build ue58-dev", "compile CARLA with cmake", "rebuild the Python API", or hits a CMake configure or target failure.

The English summary is being prepared. Showing the original description.

carla-simulator/carla-agentic-tools4Updated Sep 12, 2026

Create, migrate, improve, or debug detailed vehicle assets for CARLA using Blender and Unreal, including reference-based geometry, materials, wheels, physics, lights, and runtime validation. Use for vehicle asset authoring rather than ordinary traffic spawning or map decoration.

The English summary is being prepared. Showing the original description.

carla-simulator/carla-agentic-tools4Updated Sep 12, 2026

See all skills by carla-simulator

Report a problem with this skill