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 use YOLOX as the detector for evaluation? #1422

Closed
1 task done
yaoshanliang opened this issue May 9, 2024 · 5 comments
Closed
1 task done

How to use YOLOX as the detector for evaluation? #1422

yaoshanliang opened this issue May 9, 2024 · 5 comments
Labels
question Further information is requested Stale

Comments

@yaoshanliang
Copy link
Contributor

Search before asking

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

Question

generate_dets_n_embs.py seems to use yolov8 as the detector as the YOLO() method is from ultralytics repository.
When I pass a YOLOX model for the --yolo-mode parameter, no results are shown in dets and embs folders. The results in line 80 is generated from the yolov8n.pt in line 31.

@yaoshanliang yaoshanliang added the question Further information is requested label May 9, 2024
@yaoshanliang
Copy link
Contributor Author

@mikel-brostrom Help me. Have you tried using official YOLOX as the detector? Thanks a lot.

@mikel-brostrom
Copy link
Owner

mikel-brostrom commented May 14, 2024

You can take inspiration from track.py. track.py can run yolox. I would be more than happy to review a PR for this. I just only have time for minor bug fixes at the moment.

@yaoshanliang
Copy link
Contributor Author

@mikel-brostrom I just tried track.py. However, no results are detected. I am sure that the trained weight file is successful using official validation script, and can get the detection results.

@mikel-brostrom
Copy link
Owner

The default ByteTrack Crowdhuman weights run without problem...

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 25, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 28, 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