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

Update DetectMultiBackend for tuple outputs #9274

Merged
merged 1 commit into from
Sep 4, 2022
Merged

Update DetectMultiBackend for tuple outputs #9274

merged 1 commit into from
Sep 4, 2022

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Sep 4, 2022

πŸ› οΈ PR Summary

Made with ❀️ by Ultralytics Actions

🌟 Summary

Refinement of model output handling for better compatibility across different platforms.

πŸ“Š Key Changes

  • Consolidated the condition that checks and unpacks the tuple output from the model.
  • Removed individual tuple unpacking conditions in each platform-specific code block (PyTorch, TorchScript, ONNX Runtime, etc.).

🎯 Purpose & Impact

  • Consistency: Streamlines output handling by ensuring all platform-specific code paths adhere to a unified approach for unpacking tuples.
  • Code Simplicity: Simplifies readability and maintenance since there's now only one instance where the tuple is unpacked, reducing redundancy.
  • User Benefit: Users can expect consistent behavior across different deployment platforms, potentially reducing platform-specific bugs.

@glenn-jocher glenn-jocher changed the title Update Update DetectMultiBackend for tuple outputs Sep 4, 2022
@glenn-jocher glenn-jocher merged commit 96c3c7f into ultralytics:master Sep 4, 2022
@glenn-jocher glenn-jocher self-assigned this Sep 4, 2022
@glenn-jocher glenn-jocher deleted the detectmultibackend branch September 4, 2022 12:02
ctjanuhowski pushed a commit to ctjanuhowski/yolov5 that referenced this pull request Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant