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 did you switch the detection framework of YOLOV5 to YOLT? #6

Open
Scheaven opened this issue Aug 2, 2022 · 1 comment
Open

Comments

@Scheaven
Copy link

Scheaven commented Aug 2, 2022

Thank you for your work. I have some questions about your project code:
I looked at the model you called YoloV5 in the middle, but did not see the operation about model modification mentioned in your article (modifying the image network structure, such as modifying the Stride size, upsampling the image, and Ensemble).
The most important thing is that you do not read the model. yaml configuration file like YOLOv5, how did you switch the detection framework of YOLOV5 to YOLT?

@github-day
Copy link

Thank you for your work. I have some questions about your project code: I looked at the model you called YoloV5 in the middle, but did not see the operation about model modification mentioned in your article (modifying the image network structure, such as modifying the Stride size, upsampling the image, and Ensemble). The most important thing is that you do not read the model. yaml configuration file like YOLOv5, how did you switch the detection framework of YOLOV5 to YOLT?

Have you figured it out? Please let me know.
I read train.py and yolo.py, finding that it's just using the default yolov5l.pt and yolov5l.yaml by ckpt = torch.load(weights, map_location='cpu') #train.py line 119.
Maybe the original yolov5l model is good enough???

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

No branches or pull requests

2 participants