-
Notifications
You must be signed in to change notification settings - Fork 62
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
C++ client produces no detections #51
Comments
Hi, my client example works with wang-xinyu implementation of yolo-trt plugin (release v1.3.0 of this repo), doesn't work with current implementation on master branch(jkjung-avt implementation) , I should change input/output layer names |
The current main branch has changes in preparation for a v1.4.0 release. |
has the yolov4.wts file changed in the google drive? it fails to produce the .engine file using the v1.3 release |
for c++ client try to use yolov4.wts weights from tensorrtx-modelzoo |
hi @olibartfast I downloaded the yolov4.wts file from tensorrtx-modelzoo Creating builder |
ok , which triton server release are you using to create the engine? The code in v1.3.0 is a bit old now unfortunately and doesn't support tensorRT 8 (i.e. Triton server > r21.06), I just tested myself and i created correctly the .engine using triton server r21.05 |
Im using nvcr.io/nvidia/tensorrt:21.05-py3 |
I must been having hiccups with the .wts file, I'm getting the engine file now with the correct .wts file and tensorrt:21.05-py |
Hello @olibartfast
Thank you for your efforts. I am running the c++ client but I faced some issue.
First I needed to change model input and output name.
I also need to change the namespaces in common.hpp file to be compatible with the latest version of triton.
Now the c++ code client works with no errors but I get no detections. However when I run the python client while loading the same model I get bounding boxes and detection.
Could you please check the code and let me know if I need to change anthing to run the c++ client with this repo release.
Thanks.
The text was updated successfully, but these errors were encountered: