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

Add support for specifying tensorrt device #14898

Merged
merged 1 commit into from
Nov 10, 2024
Merged

Conversation

NickM-27
Copy link
Collaborator

@NickM-27 NickM-27 commented Nov 10, 2024

Proposed change

This makes it so when device is set to an integer and cuda or tensorrt is used for onnx then the device id is set

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code
  • Documentation Update

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • The code has been formatted using Ruff (ruff format frigate)

Copy link

netlify bot commented Nov 10, 2024

Deploy Preview for frigate-docs ready!

Name Link
🔨 Latest commit f2b79c1
🔍 Latest deploy log https://app.netlify.com/sites/frigate-docs/deploys/6730c1eaca24bf00088d4be1
😎 Deploy Preview https://deploy-preview-14898--frigate-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@hawkeye217 hawkeye217 merged commit 96c0c43 into dev Nov 10, 2024
13 checks passed
@hawkeye217 hawkeye217 deleted the specify-tensorrt-device branch November 10, 2024 14:43
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.

2 participants