-
Notifications
You must be signed in to change notification settings - Fork 14
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
Using other Object Detectors #4
Comments
Thank you for your attention. We will release the inference version of YOLOV8. |
Hi @Xavier-Lin , I have almost the same question. If the model training is to train a detector as @calvpang says, I think I can use it by setting config to a path of weghts created by training a detector separately. |
Hi @Mittag-tech,actually, there's no problem with this. In general, you can achieve the goal of changing the detector for training by replacing the detector model in the model folder and modifying the corresponding detector settings in the xxx_config.py file. |
Thank you for your response, @Xavier-Lin . Just to confirm, is this correct that the parameters of tracking module by pseudo-depth are adjusted manually? |
@Mittag-tech Manually adjusting the number of layers for pseudo-depth is possible, if needed. In general, we do not adjust the number of layers for pseudo-depth, but we do adjust the matching threshold. |
Thank you for your information, @Xavier-Lin ! |
From what I understand, the model training is specifically to train an object detector with YOLOX and not training the tracker itself.
If I had a functioning YOLOv5 model, I'm assuming I could use torch.load() and run inference on each frame using that.
But I'm a bit lost on where I can do this with the current code.
The text was updated successfully, but these errors were encountered: