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

topic mismatch #9

Open
eirikese opened this issue Sep 6, 2023 · 8 comments
Open

topic mismatch #9

eirikese opened this issue Sep 6, 2023 · 8 comments

Comments

@eirikese
Copy link

eirikese commented Sep 6, 2023

I'm getting this error message when running: rosrun lidar_obstacle_detector obstacle_detector_node

[ WARN] [1694011142.137067402]: couldn't register subscriber on topic [/]
[ERROR] [1694011142.138495795]: Tried to advertise on topic [/] with md5sum [c8f4a8bb1acd18ce778d183912bb472d] and datatype [jsk_recognition_msgs/BoundingBoxArray], but the topic is already advertised as md5sum [1158d486dd51d683ce2f1be655c3c181] and datatype [sensor_msgs/PointCloud2]
[ERROR] [1694011142.138548295]: Tried to advertise on topic [/] with md5sum [c16aecef51c24c6808480a0295e47806] and datatype [autoware_msgs/DetectedObjectArray], but the topic is already advertised as md5sum [1158d486dd51d683ce2f1be655c3c181] and datatype [sensor_msgs/PointCloud2]

@HiYvaine
Copy link

I also encountered the same problem, the root cause is that the hungarianFind function in the hpp file lacks a stable return value.

@SS47816
Copy link
Owner

SS47816 commented Jan 23, 2024

Hi,

Thanks for spotting the issue! I have now fixed the return value in the function hungarianFind().

Please let me know if your issue still persists.

Best regards,
Shuo

@juannn01
Copy link

Hi there! I'm facing the similar problem when launching the mai_city.launch file.
image

I'm trying with my own data using the point cloud obtained from RoboSense LiDAR and the topics contained in the rosbag are as follows:
image

I've also made some changes on the mai_city.launch file to suit my own lidar and the codes are shown below:
image

When I launched the file and play the rosbag at the same time, the warning error exists and the rviz is not showing any result unless I selected the Velodyne Points to view the original point cloud from my rosbag file.
image

Would really appreciate if you could provide any advice in solving this issue. Thanks in advance!

@SS47816
Copy link
Owner

SS47816 commented Mar 12, 2024

Hi juannn01,

May I know if your issue still exists after trying the latest code (the version with the hungarianFind() return value fixed)?

I am not able to reproduce your error on my side right now. If it persists, please provide more information so I can track down the root cause.

Thanks!
Shuo

@Reyshwanth
Copy link

Hey Shuo Sun,

I have the same issue. I believe you have not pushed the code with the change to hungarianFind() yet!

Reyshwanth

@ddwnbe
Copy link

ddwnbe commented May 14, 2024

Hello Shuo Sun

I am encountering the same error as the others:
image

I am using the mai_city.launch, but modified to receiver another sensor_msgs/PointCloud2 as input. I pulled the code yesterday and built it for ROS Noetic 1.16.0.
image

Best regards
ddwnbe

edit: in obstacle_detector_node.cpp I came across the following:
image
I removed ROS_ASSERT(...) and after that, I no longer got the error. A std::cout showed that the topics were empty, when ROS_ASSERT(...) was present in the code. I did not look further into why this is.

@yulongheart
Copy link

2024-05-15 21-05-03 的屏幕截图
Hello, I have encountered some issues. It seems that there is an undefined symbol, "_ZN4rviz12EnumPropertyC1ERK7QStringS3_S3-PNS_8PropertyE", when loading the libjsk_rviz_plugins.so dynamic link library. I would like to ask if you have encountered this issue and how to solve it.

@JiaoxianDu
Copy link

2024-05-15 21-05-03 的屏幕截图 Hello, I have encountered some issues. It seems that there is an undefined symbol, "_ZN4rviz12EnumPropertyC1ERK7QStringS3_S3-PNS_8PropertyE", when loading the libjsk_rviz_plugins.so dynamic link library. I would like to ask if you have encountered this issue and how to solve it.

apt update and apt upgrade solved same problem to me.

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

8 participants