Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ask how yolov11 achieves segmentation. #18234

Open
1 of 2 tasks
ZHIYUAN816 opened this issue Dec 14, 2024 · 2 comments
Open
1 of 2 tasks

Ask how yolov11 achieves segmentation. #18234

ZHIYUAN816 opened this issue Dec 14, 2024 · 2 comments
Labels
enhancement New feature or request question Further information is requested segment Instance Segmentation issues, PR's

Comments

@ZHIYUAN816
Copy link

Search before asking

  • I have searched the Ultralytics issues and found no similar feature requests.

Description

Ask how yolov11 achieves segmentation. Can you provide a structural diagram for me to understand more deeply?

Use case

No response

Additional

No response

Are you willing to submit a PR?

  • Yes I'd like to help by submitting a PR!
@ZHIYUAN816 ZHIYUAN816 added the enhancement New feature or request label Dec 14, 2024
@UltralyticsAssistant UltralyticsAssistant added question Further information is requested segment Instance Segmentation issues, PR's labels Dec 14, 2024
@UltralyticsAssistant
Copy link
Member

👋 Hello @ZHIYUAN816, thank you for your interest in Ultralytics 🚀! We recommend checking out the Docs, where you'll find detailed explanations of various features, including segmentation, along with Python and CLI usage examples. Many of your questions might already be answered there.

If this is a ❓ Question about how segmentation works in YOLOv11, could you please elaborate on the details you are looking for or clarify your use case? Specific structural or implementation-related questions may also be addressed in the source code or through our reference guides.

If this request relates to a specific 🐛 Bug Report or feature request, we kindly ask you to share additional context or details, such as any implementation issues or specific outputs you're aiming to achieve. A minimum reproducible example would also be very helpful for debugging, where applicable.

Join the Ultralytics community where it suits you best to discuss this topic further:

  • For real-time interaction, visit our Discord 🎧.
  • Participate in deeper discussions on our Discourse forum.
  • Explore and share knowledge on our Subreddit.

Upgrade

Consider upgrading to the latest version of the ultralytics package to ensure you're benefiting from all recent updates and fixes. Run the following in a Python>=3.8 environment with PyTorch>=1.8:

pip install -U ultralytics

Environments

YOLOv11 can be run in various environments, including notebooks (with free GPUs), cloud platforms, and Docker. Choose any of the options outlined below to get started:

Status

Ultralytics CI

If this badge is green, all Ultralytics CI tests are currently passing. These CI tests verify the correctness of all Modes and Tasks across macOS, Windows, and Ubuntu on a 24-hour schedule and after every commit.

This is an automated response to help address your query quickly. An Ultralytics engineer will also assist you soon. Let us know if there's any further detail you'd like to share in the meantime 😊!

@glenn-jocher
Copy link
Member

@ZHIYUAN816 yOLO11 achieves segmentation by leveraging a variant of the U-Net architecture, enabling it to segment images into regions with high accuracy and speed. While we currently don't provide structural diagrams directly, you can explore more about segmentation and its implementation in our documentation here: https://docs.ultralytics.com/tasks/. For detailed inquiries, feel free to engage in the Ultralytics GitHub Discussions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested segment Instance Segmentation issues, PR's
Projects
None yet
Development

No branches or pull requests

3 participants