-
Notifications
You must be signed in to change notification settings - Fork 639
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
No detect output from yolox #7779
Comments
share the rosbag. |
The bag was uploaded here https://drive.google.com/file/d/1Tp-cUaLl7m0XHDsvItfPMVkY-dWtGg7j/view?usp=drive_link |
Hi mits-san, will you help us by assign someone to take a look at this issue |
@beginningfan My environment:
|
@badai-nguyen Thanks for your reply.
|
@beginningfan Thank you for your confirmation. |
@badai-nguyen There is no useful information in the log. |
I use the same version as @beginningfan. Dai's version is a bit outdated; you should update the NVIDIA-related libraries.
As a result, the model (yolox-sPlus-opt-pseudoV2-T4-960x960-T4-seg16cls.onnx) worked without any issues, as shown in this image below. I'm not sure what is happening but could you try with this PR ? |
@miursh Thanks for your replay. |
@beginningfan |
hi miura-san,any feedback for “run yolox node in docker(20240618-devel-cuda-amd64 and 20240708-devel-cuda-amd64) ” ? @miursh |
@liuXinGangChina
It seems the build process does not complete successfully... |
@liuXinGangChina @beginningfan |
test on code up to this commit:083ed2f , it works fine |
Checklist
Description
I try to start the
tensorrt_yolox
node. When I setpreprocess_on_gpu
here totrue
,the ouptput in/perception/object_recognition/detection/rois0
is empty. When I set it tofalse
, it works well.Expected behavior
When I launch tensorrt_yolox with
preprocess_on_gpu
istrue
,the rois in output is not emptyActual behavior
Steps to reproduce
use
ros2 launch tensorrt_yolox yolox.launch.xml
to launch this nodeVersions
OS: Ubuntu
ROS2: humble
Autoware: latest
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: