syigzaw's profile - activity

Autoware lidar_euclidean_cluster_detect not using gpu On Ubuntu 18.04, Ros Melodic I'm trying to use lidar_euclidean_cl

Autoware lidar_euclidean_cluster_detect not using gpu On Ubuntu 18.04, Ros Melodic I'm trying to use lidar_euclidean_cl

Autoware lidar_euclidean_cluster_detect not using gpu On Ubuntu 18.04, Ros Melodic I'm trying to use lidar_euclidean_cl

I'm getting the same problem as well. Additionally, when I check the Baselink support box, I get the following error mes

Since I'm asking this for Autoware, they already have a Dockerfile structure in place. I'm trying to add the pip install

Thanks a lot, I got everything working now. I suppose this means that if I ever need to install new python packages, I n

Installed packages not staying when exiting Autoware docker container and re-entering In the docker container I'm using

Thank you so much for your detailed response. I just submitted a pull request, and I also set up Autoware using the base

In this commit: https://gitlab.com/autowarefoundation... the value of v is changed from -1.3 to -5.

In the Runtime Manager Dialog: https://gitlab.com/autowarefoundation... the way a parameter is determined to be a float instead of an int is by checking whether one of the min, max, or v values is a float. If at least one of them is a float, then it'll be a float param which can receive float values from the user in the dialog box. Before the above commit, this would have worked, but now it's not working and I can't change the clip_min_height value without changing these files manually and rebuilding. In addition, even if I do change these values, they just reset every time I exit the docker container and re-enter. Is there a way to permanently fix these values on my end, or do I need to go in and change them and rebuild every time I re-enter the container?

Either way, I just wanted to let you guys know of this issue. Thanks for your help.

Autoware runtime manager lidar_euclidean_cluster_detect clip_min_height parameter unable to take float values In this co

Ubuntu 16.04, ROS distro: Kinetic, ROS version: 1.12.14, Autoware version: 1.12.0

The only relevant documentation I found on this package is here: https://gitlab.com/autowarefoundation...

I'm playing a pcap file which is publishing to /points_raw, rviz is showing the points, but when I go into the Computing tab of the Runtime Manager and select lidar_euclidean_cluster_detect, nothing happens. I tried changing some of the parameters it has, like changing the input_points_node parameter to /points_raw, but nothing's worked. Is there something from the parameters I'm missing, or do I need to look in a completely different area? Thanks in advance for your help.

The solution is to find your internal IP address, I did this using hostname -I. Take an address from the output and ente

Ok, thank you very much for your help, and thanks for being patient with me for all the questions I had.

Ok, so other than the polygonal bounds, is there any way to get 3D bounding boxes? I'm trying to get the same thing that

Ok, so other than the polygonal bounds, are there any way to get 3D bounding boxes? I'm trying to get the same thing tha

I see, I may have been mistaken about the use of /detection/lidar_detector/objects. Is there a way to visualize bounding

Ok, it's almost working! It's now publishing to: /points_cluster /detection/lidar_detector/objects /detection/lidar_d

Ok, it's almost working! It's now publishing to: /points_cluster /detection/lidar_detector/objects /detection/lidar_d

I just saw that the subscriptions were wrong so I changed it: Subscriptions: /points_raw [sensor_msgs/PointCloud2] /

I just saw that the subscriptions were wrong so I changed it: Subscriptions: /points_raw [unknown type] /tf [unknown

I'm not running roscore outside the docker container. I changed ROS_IP to equal one of the addresses that were outputte

contacting node http://129.97.69.75:44442/ ... Pid: 12441 Connections: topic: /rosout to: /rosout direction: outbo

I'm not running roscore outside the docker container. I changed ROS_IP to equal one of the addresses that were outputte

# echo $ROS_IP localhost # echo $ROS_MASTER_URI http://localhost:11311 Initially, echo $ROS_IP didn't output anythi

# echo $ROS_IP localhost # echo $ROS_MASTER_URI http://localhost:11311 Initially, echo $ROS_IP didn't output anything

I entered the docker container by running $ docker exec -it <container-id> bash I did this multiple times, in o

@amc-nu The comments are starting to get hidden now so I didn't see your comment until now. It's all running in one dock

The comments are starting to get hidden now so I didn't see your comment until now. It's all running in one docker conta

It's all running in one docker container, connected to by several different terminals. I set it up by running $ ./run.s

# rosnode info lidar_euclidean_cluster_detect Node [/lidar_euclidean_cluster_detect] Publications: /cluster_centr

# rosnode list /detection/lidar_detector/cluster_detect_visualization_01 /lidar_euclidean_cluster_detect /rosout /run