Checks a local CARLA checkout for missing API documentation, outdated references, broken links, and pages absent from navigation. Produces a grouped Markdown report without building the project or running the simulator.
Fill documentation gaps identified by a CARLA documentation audit, following the project's writing style. Work through one category at a time, assess which findings deserve entries, update source files, and report changes and skipped findings.
Check which CARLA features are missing on UE 5.5 compared with UE 5.8. Read source markers to identify the checkout, review unsupported workflows, and see which UE 5.8 procedures also apply.
Guides custom map imports into CARLA on UE 5.8, from FBX geometry and OpenDRIVE road data to packaging or temporary road generation. Helps choose a supported route and verify map files and loading.
Prepare and launch Autoware with CARLA on UE 5.8 through its native ROS 2 interface. Check communication topics and sensors, generate required maps, and configure either the classical stack or camera-only VAD model.
Create, migrate, refine, or debug CARLA vehicle assets with Blender and Unreal. Use real vehicle references to guide geometry and materials, configure wheels, lights, and physics, and deliver editable sources with evidence from runtime validation.
Import a custom pedestrian into CARLA on UE 5.8, connect it to the shared animation skeleton, and verify that it moves. Export an existing walker as an FBX starting point or investigate a walker that stands still.
Import FBX 3D models into CARLA on UE 5.8 and register them as props that can be placed in a simulation. Check measured dimensions, adjust scale, verify placement on a running server, and undo imports when needed.
Start, inspect, and stop a CARLA UE 5.8 server. Choose an editor-based server, packaged build, or full editor; configure headless operation and ports; and enable native ROS 2 integration when the build supports it.
Build CARLA for Unreal Engine 5.8 using CMake, the tool that configures its build process. The skill guides engine setup, optional ROS 2 support, Python API rebuilding, editor builds, and checks that the expected files were actually produced.
Package a CARLA server built with UE 5.8 for distribution, choosing which maps to include. Inspect the resulting files for mismatched containers, missing road data, and exposure settings that can cause runtime failures.
Start a CARLA simulator server from a downloaded release, packaged build, or source checkout. It selects the launch mode, supports headless or windowed operation, checks client connectivity, and guides clean shutdown.
Package a CARLA Leaderboard agent into a Docker image for submission. It checks required directories and Python package files, supports ROS variants, and verifies that dependencies import and the agent loads inside the image.
Create and edit CARLA driving routes by placing waypoints and scenario triggers in the simulator. Inspect routes visually, review summary tables, check XML structure and trigger positions, and convert older route files to the 2.x format.
Build distributable CARLA releases or asset packages containing selected maps and props. It prepares content for runtime use, checks output files, supports destination changes, and preserves native ROS 2 support when explicitly enabled.
Summarize ScenarioRunner results to see which scenarios passed and which checks failed. Compare runs before and after changes, or analyze recorded driving to produce measurements and plots of vehicle distance and deviation from the lane center.
Read existing CARLA sensors to view live camera or lidar output, save recordings, or inspect a single reading. Display multiple sensors together and check ROS 2 topic names, delivery settings, and whether publishing is enabled.
Control street, building, and vehicle light sources in CARLA. Switch groups on or off, adjust their color and brightness, and enable automatic nighttime lighting to prepare illuminated city scenes or blackouts.
Populate a running CARLA simulation with autonomous traffic, evenly spaced vehicles in one lane, or a single vehicle for control and sensors. Filter vehicle models, keep automated driving active, and remove vehicles when the scene is finished.
Read and change a running CARLA server’s timing, physics substeps, and rendering settings. Switch between client-controlled steps and automatic progression, keep Traffic Manager synchronization aligned, and read back the settings to verify each change.
Add pedestrians to a CARLA map and let them walk autonomously. Adjust crowd size, walking speed, road-crossing frequency, and placement seeds, create stationary crowds, and remove pedestrians together with their movement controllers in the correct order.
Inspect a running CARLA simulation and identify vehicles or pedestrians by type, role, color, or proximity. Retrieve their IDs, scene snapshots, static object bounds, ground positions, and expected ROS 2 topics with reasons for missing publications.
Extend CARLA’s native ROS 2 interface to publish sensor data or receive vehicle commands. Covers topic implementation, registration, data connections, and verification, plus adding middleware, the communication layer used to exchange messages.
Read and display CARLA object bounding boxes, then project them onto a camera image as 2D rectangles. Export an annotated PNG and box coordinates in JSON for object detection annotation work.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)