-
-
Notifications
You must be signed in to change notification settings - Fork 268
yolo component #1033
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
yolo component #1033
Conversation
✅ Deploy Preview for viseron canceled.
|
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.
Added some comments on the error handling that i think should be changed.
Otherwise everything looks good!
|
If you want to check out the docs you can either use the Preview link created by Netlify or you can run the docs locally |
|
Thanks for the comments I will update the PR. |
|
CI is failing due to the hosted agent running out of space when installing ultralytics and all the deps. Investigating |
Thanks. Where do I place the image for the component browser entry? I have |
|
I forgot to mention that the version of the Ultralytics library I referenced doesn't have type hints. This is probably a the cause of failure of the mypy pre-commit check. For my workflow I need to use a couple of machines and the one I submit code doesn't have the pre-commit checks enabled so that is how it got submitted without passing. I see in the last week there was an update that has type annotations in the library. I have not tested yet but can hold off on PR until that has been verified. error: |
Where did you find it? One option is to find a link to a hosted version and use that instead of commiting it to the repo |
I made some changes which should increase disk space available on the agent. |
8201443 to
75c2cf7
Compare
I should re-squash into a new branch? Or should I leave the commits in existing branch? |
That is up to you! You either merge dev into your branch or rebase and force push. Edit: ah I see you did that already. Will start the CI |
|
Hmm i cant get the CI to work. Need some more time to investigate |
|
Now its working again, two small issues tho, would you mind trying to fix them? Pylint error should be easy. And i think the mypy error can be fixed by adding this to |
|
I will make that changes |
|
Done and pushed. |
|
Pylint is still complaining, but i can fix that for you if you like. I have pestered you enough already 😄 |
|
I will fix that. It is in an additional file that is not part of this change but it looks pretty benign. Should take a minute or two. |
|
Also note that that the tests I added will take 10 seconds each or so to run and are not quick like other tests. They wait for the concatenate thread to finish in order to validate the timing aspects of the change. If this is a concern maybe these can be conditionally in some way (e.g. do not run locally). |
|
Awesome, great job! And thanks for sticking with it all the way :) |
|
No problem and thanks for this great application. I could not have done any of this without all the hooks and interfaces you put in place. |
|
Oh...I just updated to this version and so far it works as expected :) |
|
Great! 🚀 |
This is a component to load an Ultralytics YOLO model and perform object detection with it.
The component browser entry should explain the usage. That said, I have not yet found a rendered version of the updated documentation.
There have been changes since the review branch was made. Most recently the exception error messages are now more descriptive. Also, if the component fails to load or there is a fatal error with yolo prediction the yolo objection detection is disabled.