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

Autodistill execution error #124

Closed
1 task done
sa136199 opened this issue Feb 4, 2024 · 7 comments
Closed
1 task done

Autodistill execution error #124

sa136199 opened this issue Feb 4, 2024 · 7 comments
Labels
question Further information is requested

Comments

@sa136199
Copy link

sa136199 commented Feb 4, 2024

Search before asking

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

Question

When I use Autodistill on Roboflow to label images
After the marking is completed, the marked pictures will be automatically moved from Unassigned to Dataset
But in recent days, it cannot be executed correctly
The error message is as shown below
Is there a solution or do I need to wait for the system to repair automatically?
Thanks!
92425ee9f4190bbe335416e0f673b264a7c47b5d
f52cf21e7dc59429a131f8185bc49e9011df7a71
590d358c5778e5a81f47b80a6f56d4c23be7850a

Additional

No response

@sa136199 sa136199 added the question Further information is requested label Feb 4, 2024
@nguyenthekhoig7
Copy link

Hi, same here. I got the same problem, and I found a walkaround to get over it (not sure if it will work to submit as a PR).

You can open the yolo.py file (click on the blue link to the file), change the line that directly causing this error from
for xyxy, mask, _, class_id, _ in detections:

to

for xyxy, mask, _, class_id, _ , _ in detections: (add one placeholder)

The reason for this walkaround is that when I printed out the detections variable and turned out it had 6 var instead of 5, so I added one.

Hope this helps.

@nguyenthekhoig7
Copy link

Since the file I made the change to is in the supervision folder, not autodistill, I am not sure if I can submit a PR for this. I hope that there's another way for this rather than manually fixing like the way I did.

@sa136199
Copy link
Author

sa136199 commented Feb 8, 2024

Thank you
This method solved my problem
I also hope there can be a fundamental solution
Anyway thank you very much

@SkalskiP
Copy link
Contributor

SkalskiP commented Feb 8, 2024

Hi @nguyenthekhoig7 and @sa136199, This problem is related to a bug in the current version of supervision. All you must do is pip install supervision==0.19.0rc2 in your Python environment. This will update supervision and the bug should go away.

@sa136199
Copy link
Author

Thank you for providing a more convenient solution

@capjamesg
Copy link
Member

We will be releasing a new version of supervision in the next week that will solve this problem.

@capjamesg
Copy link
Member

This problem has since been fixed in supervision, so I am closing this issue. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants