Seeed-Jetson-DevelopTool / deploy-depth-anything-v3
AGENTS.md57 starsChanged 4 months agoMITView on GitHub
Deploy Depth Anything V3 monocular depth estimation on Jetson AGX Orin with ROS2 Humble integration. Builds a ROS2 workspace with TensorRT-optimized ONNX models for real-time depth map generation from USB camera or video input. Requires JetPack 6.2 and ROS2 Humble.
- Installs packages
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository297 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-nvrAGENTS.md
- allxon-ota-updateAGENTS.md
- allxon-setupAGENTS.md
- alwaysai-setupAGENTS.md
- backup-restoreAGENTS.md
- bsp-source-buildAGENTS.md
- clawdbot-developmentAGENTS.md
- cochl-sense-setupAGENTS.md
- cvedia-setupAGENTS.md
- dashcamnet-xavier-nx-multicameraAGENTS.md
- deciai-setupAGENTS.md
- deepseek-quick-deployAGENTS.md
- deploy-deepseek-mlcAGENTS.md
- deploy-diaAGENTS.md
- deploy-efficient-vision-engineAGENTS.md
- deploy-frigateAGENTS.md
- deploy-live-vlm-webuiAGENTS.md
- deploy-nvbloxAGENTS.md
- deploy-ollama-anythingllmAGENTS.md
- deploy-riva-llama2AGENTS.md
- developtool-deviceAGENTS.md
- disk-encryptionAGENTS.md
- diy-bsp-buildAGENTS.md
- ethercat-communicationAGENTS.md
- ethercat-setupAGENTS.md
- finetune-llm-llama-factoryAGENTS.md
- fix-browser-snap-jetsonAGENTS.md
- gapi-setupAGENTS.md
- generative-ai-introAGENTS.md
- gpt-oss-liveAGENTS.md
- gr00t-n1-5-deploy-thorAGENTS.md
- gr00t-n1-6-deploy-agxAGENTS.md
- hardhat-setupAGENTS.md
- hybrid-bsp-dk-to-recomputerAGENTS.md
- imx477-a603-setupAGENTS.md
- j501-viola-fruit-sortingAGENTS.md
- jetpack5-ssd-boot-fixAGENTS.md
- jetpack-flash-wsl2AGENTS.md
- jetpack-jetson-overviewAGENTS.md
- jetpack-ota-updateAGENTS.md
- jetson-ai-toolsAGENTS.md
- jetson-docker-setupAGENTS.md
- jetson-faqAGENTS.md
- jetson-pc-wired-shareAGENTS.md
- jetson-project-galleryAGENTS.md
- jetson-resource-indexAGENTS.md
- jetson-tutorial-exercisesAGENTS.md
- ko-module-buildAGENTS.md
- l4t-differencesAGENTS.md
- langchain-output-formattingAGENTS.md
- lerobot-env-setupAGENTS.md
- llama-cpp-rpc-distributedAGENTS.md
- llm-interface-controlAGENTS.md
- local-chatbot-multimodalAGENTS.md
- local-chatbot-physicalAGENTS.md
- local-llm-text-to-imageAGENTS.md
- local-rag-llamaindexAGENTS.md
- lumeo-setupAGENTS.md
- maskcam-nanoAGENTS.md
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run one phase at a time. After each phase:
- Very specific: line 16
If output contains [STOP] → stop immediately, consult the failure decision tree.
- Very specific: line 17
If output ends with [OK] → tell the user "Phase N complete" and proceed to the next phase.
- Very specific: line 92
Place it in the ros2-depth-anything-v3-trt/onnx/ directory
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy Depth Anything V3 on Jetson AGX Orin
Depth Anything V3 generates high-quality depth maps from single RGB images. This skill deploys it on Jetson AGX Orin with ROS2 and TensorRT acceleration for real-time robotics use.
Execution model
Run one phase at a time. After each phase:
- Relay all output to the user.
- If output contains
[STOP]→ stop immediately, consult the failure decision tree. - If output ends with
[OK]→ tell the user "Phase N complete" and proceed to the next phase.
Prerequisites
| Requirement | Detail |
| Hardware | Jetson AGX Orin (e.g. reComputer Mini J501) |
| JetPack | 6.2 |
| ROS2 | Humble installed and sourced |
| Camera | USB camera connected |
| Network | Internet for cloning repos and downloading ONNX models |
Phase 1 — Install system dependencies (~3 min)
sudo apt update
sudo apt install -y \
build-essential cmake git libopencv-dev \
python3-pip python3-colcon-common-extensions v4l-utils
pip3 install numpy opencv-python[OK] when all packages install without error.
Phase 2 — Configure CUDA environment (~1 min)
echo '
# CUDA Environment
export CUDA_HOME=/usr/local/cuda
export PATH=$CUDA_HOME/bin:$PATH
export LD_LIBRARY_PATH=$CUDA_HOME/lib64:$LD_LIBRARY_PATH
export CUDACXX=$CUDA_HOME/bin/nvcc
' >> ~/.bashrc
source ~/.bashrc
nvcc --version[OK] when nvcc --version prints CUDA version info. [STOP] if nvcc is not found.
Phase 3 — Install ROS2 camera packages (~2 min)
sudo apt install -y ros-humble-usb-cam ros-humble-cv-bridge \
ros-humble-image-transport ros-humble-image-geometry ros-humble-rviz2[OK] when all ROS2 packages install successfully.
Phase 4 — Clone and build the ROS2 workspace (~5 min)
git clone https://github.com/zibochen6/ros2-depth-anything-v3-trt.git
cd ros2-depth-anything-v3-trt
colcon build --packages-select depth_anything_v3 --cmake-args -DCMAKE_BUILD_TYPE=Release
source install/setup.bash[OK] when colcon build completes with no errors. [STOP] if build fails.
Phase 5 — Download ONNX model and generate TensorRT engines (~10–20 min)
- Download the
.onnxmodel from https://huggingface.co/TillBeemelmanns/Depth-Anything-V3-ONNX - Place it in the
ros2-depth-anything-v3-trt/onnx/directory - Generate engines:
chmod +x generate_engines.sh
./generate_engines.sh onnx[OK] when .engine files appear in the onnx/ directory. [STOP] if conversion fails.
Phase 6 — Camera calibration (optional but recommended)
Install calibration tools:
sudo apt install -y ros-humble-camera-calibration ros-${ROS_DISTRO}-v4l2-cameraLaunch camera and calibrate:
# Terminal 1: launch camera
ros2 run v4l2_camera v4l2_camera_node --ros-args -p image_size:=[640,480] -p pixel_format:=YUYV
# Terminal 2: run calibration
ros2 run camera_calibration cameracalibrator \
--size 8x6 --square 0.025 \
--ros-args --remap image:=/image_raw --remap camera:=/v4l2_cameraSave calibration parameters to camera_info_example.yaml.
[OK] when calibration completes and parameters are saved.
Phase 7 — Run depth estimation (~1 min)
For USB camera:
CAMERA_INFO_FILE=camera_info_example.yaml ENABLE_UNDISTORTION=1 ./run_camera_depth.shFor video file:
./run_video_depth.sh[OK] when depth visualization appears.
Failure decision tree
| Symptom | Action |
nvcc: command not found | CUDA not installed or not in PATH. Verify JetPack 6.2 installation, re-run Phase 2. |
colcon build fails with missing dependency | Install missing ROS2 or system package, then rebuild. |
| TensorRT engine generation fails | Check ONNX model is valid and placed in correct directory. Verify TensorRT is installed: dpkg -l | grep tensorrt. |
No /dev/video* devices found | USB camera not detected. Replug camera, check with lsusb and v4l2-ctl --list-devices. |
| ROS2 topic not publishing | Source the workspace: source install/setup.bash. Check camera node is running. |
| OOM during engine generation | Close other GPU processes. Engine generation for large models needs significant GPU memory. |
Reference files
references/source.body.md— Full Seeed Wiki tutorial with screenshots, calibration details, and video demo links (reference only)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

