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

How to evaluate the VisDrone dataset using YOLOv5 and ByteTrack #1420

Closed
1 task done
Czeni1 opened this issue May 8, 2024 · 3 comments
Closed
1 task done

How to evaluate the VisDrone dataset using YOLOv5 and ByteTrack #1420

Czeni1 opened this issue May 8, 2024 · 3 comments
Labels
question Further information is requested Stale

Comments

@Czeni1
Copy link

Czeni1 commented May 8, 2024

Search before asking

  • I have searched the Yolo Tracking issues and found no similar bug report.

Question

Author, I'm very sorry to bother you. I'm using yolo tracking8.0 and the tracker uses ByteTrack without REID. After running the track.py file, I wanted to see how the tracking performance works. However, I ran val.py again and a new val_utils file appeared. I want to know what this function is and how can I evaluate the performance of the VisDrone dataset? Looking forward to your answer, thank you very much!
3b738c79ccc759337e42ee2056e8125

@Czeni1 Czeni1 added the question Further information is requested label May 8, 2024
@mikel-brostrom
Copy link
Owner

@Czeni1
Copy link
Author

Czeni1 commented May 8, 2024

检查评估下:https://github.com/mikel-brostrom/yolo_tracking?tab=readme-ov-file#yolov8--yolo-nas--yolox-examples

Thank you for your reply, but I would like to ask why ByteTrack can only run one video instead of the entire test set in the dataset?
Looking forward to your reply!
c95882036dcf5d4d37e76a79d54d65a

Copy link

👋 Hello, this issue has been automatically marked as stale because it has not had recent activity. Please note it will be closed if no further activity occurs.
Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

@github-actions github-actions bot added the Stale label May 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

2 participants