Add stereo 3D detection docs images

[Bovey0809]

Summary

• Add 10 images for the beginner-friendly stereo 3D detection documentation
• Used in docs/en/tasks/s3d.md and docs/en/datasets/detect/kitti-stereo.md
• Images include architecture diagrams, detection examples, concept illustrations, and comparison charts

Images

File	Description	Size
compare_2d_vs_3d.jpg	2D vs 3D detection comparison	59 KB
concept_stereo_vision.jpg	Stereo vision concept diagram	45 KB
output_fields.jpg	Model output fields diagram	78 KB
architecture_overview.jpg	YOLO26 s3d architecture	95 KB
depth_bins_dfl.jpg	Depth bin distribution illustration	90 KB
model_comparison.jpg	Model size/accuracy chart	74 KB
sensor_cost_comparison.jpg	Stereo vs LiDAR cost comparison	64 KB
s3d_example_003870.jpg	Detection example - urban street	256 KB
s3d_example_003980.jpg	Detection example - suburban	219 KB
s3d_example_004800.jpg	Detection example - residential	252 KB

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR refreshes several documentation images in ultralytics/assets, improving the visual materials used to explain stereo vision, 3D concepts, model comparisons, and related architecture topics 🖼️✨

📊 Key Changes

• Updated multiple image assets under the docs/ directory.
• Refreshed visuals related to:
  • architecture overview
  • 2D vs 3D comparison
  • stereo vision concepts
  • depth bin visualization
  • model comparison
  • output field explanations
  • example stereo/3D images
  • sensor cost comparison
• Changes appear limited to documentation/media assets, with no code changes included in the provided diff.

🎯 Purpose & Impact

• Improves the clarity and quality of documentation visuals for users learning about 3D perception and related Ultralytics concepts 📚
• Makes technical topics easier to understand for both new and experienced users through clearer diagrams and examples 👀
• Helps documentation stay up to date and more polished, which can improve onboarding, presentations, and educational content 🚀
• Since the changes are asset-only, they should have little to no impact on runtime behavior, training, or model performance ✅

📋 Skipped 10 files (lock files, generated, images, etc.)

• docs/architecture_overview.jpg
• docs/compare_2d_vs_3d.jpg
• docs/concept_stereo_vision.jpg
• docs/depth_bins_dfl.jpg
• docs/model_comparison.jpg
• docs/output_fields.jpg
• docs/s3d_example_003870.jpg
• docs/s3d_example_003980.jpg
• docs/s3d_example_004800.jpg
• docs/sensor_cost_comparison.jpg

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[UltralyticsAssistant]

👋 Hello @Bovey0809, thank you for submitting a ultralytics/assets 🚀 PR! This is an automated message to help streamline review; an engineer will assist you soon 😊 Please review the checklist below to help ensure seamless integration of your documentation asset updates:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/assets main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

All 10 changed files are generated/vendored (skipped review)

📋 Skipped 10 files (lock files, generated, images, etc.)

• docs/architecture_overview.jpg
• docs/compare_2d_vs_3d.jpg
• docs/concept_stereo_vision.jpg
• docs/depth_bins_dfl.jpg
• docs/model_comparison.jpg
• docs/output_fields.jpg
• docs/s3d_example_003870.jpg
• docs/s3d_example_003980.jpg
• docs/s3d_example_004800.jpg
• docs/sensor_cost_comparison.jpg

[glenn-jocher]

Looks good @Bovey0809

[UltralyticsAssistant]

🎉 Wonderful to see this PR merged — thank you @Bovey0809, with support from @glenn-jocher, for polishing these documentation visuals so thoughtfully.

As Leonardo da Vinci said, “Simplicity is the ultimate sophistication.” This refresh does exactly that: it makes complex stereo vision, 3D perception, and model comparison concepts clearer, more approachable, and more impactful for everyone learning from Ultralytics docs.

Your work helps turn technical depth into intuitive understanding, and that kind of clarity is incredibly valuable to the community. Really appreciate the care and craftsmanship behind this update 🚀