-
Notifications
You must be signed in to change notification settings - Fork 50
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
fix: Improve detection and classification pipelines #690
fix: Improve detection and classification pipelines #690
Conversation
Signed-off-by: Antonio Martinez <[email protected]>
Signed-off-by: Antonio Martinez <[email protected]>
Signed-off-by: Antonio Martinez <[email protected]>
Signed-off-by: Antonio Martinez <[email protected]>
|
||
- [Prerequisites](#prerequisites) | ||
- [QuickStart](#quickstart) | ||
- [Run pipeline on integrated GPU](#run-pipeline-on-integrated-gpu) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [Run pipeline on integrated GPU](#run-pipeline-on-integrated-gpu) | |
- [Run pipeline on integrated GPU (iGPU)](#run-pipeline-on-integrated-gpu) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to add or modify a make target to call the docker-compose-sensors along with the main compose file?
Signed-off-by: Antonio Martinez <[email protected]>
@ejlee3 I will create another make target for that compose. The reason is, if we want to run benchmarks, we don't want any extra overhead. I will create a separate PR |
PR Checklist
What are you changing?
Issue this PR will close
close: #issue_number
Anything the reviewer should know when reviewing this PR?
Test Instructions if applicable
Run:
If the there are associated PRs in other repositories, please link them here (i.e. intel-retail/automated-self-checkout )