ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Doug's profile - activity

2023-01-30 06:23:28 -0500 received badge  Famous Question (source)
2022-10-07 08:53:44 -0500 received badge  Notable Question (source)
2022-10-07 08:53:44 -0500 received badge  Popular Question (source)
2022-05-31 19:17:45 -0500 asked a question [Autoware auto] - Monitored node

[Autoware auto] - Monitored node Hi all, Autoware.auto user here. Ade v4.4.0, on master branch, last commit is [e3e26b

2021-08-24 02:22:38 -0500 received badge  Famous Question (source)
2021-05-04 10:43:20 -0500 received badge  Notable Question (source)
2021-02-25 11:31:43 -0500 received badge  Popular Question (source)
2021-02-12 13:30:02 -0500 asked a question Kacanopen motor control - SDO error

Kacanopen motor control - SDO error Hi, I have been using Kacanopen ("easy-to-use CANopen stack") for communicating b

2020-02-11 04:50:50 -0500 received badge  Famous Question (source)
2020-01-15 06:35:46 -0500 received badge  Famous Question (source)
2020-01-02 17:51:43 -0500 received badge  Notable Question (source)
2019-12-16 19:53:22 -0500 received badge  Popular Question (source)
2019-12-12 11:53:16 -0500 commented answer Autoware - can't launch .launch file without runtime manager

Thanks ! That was it. I needed to do: rosparam load headless_setup.yaml

2019-12-12 11:42:10 -0500 marked best answer Autoware - can't launch .launch file without runtime manager
  • Ubuntu 16.04
  • Autoware Docker pre-built container autoware/autoware:latest-melodic-cuda
  • Local ROS version: Kinetic

Hi all,

I'm trying to use most of Autoware's packages without launching them from the runtime manager. I use a .launch file that launches all the packages and nodes I need. This works fine, except for ndt_matching.launch from the lidar_localizer package. I realized that even by running:

cd /home/autoware/Autoware

source install/setup.bash

roslaunch lidar_localizer ndt_matching.launch

I get the following error:

auto-starting new master process[master]: started with pid [12645] ROS_MASTER_URI=http://localhost:11311

setting /run_id to 5739dd7a-1c64-11ea-8d07-48a472bde50c process[rosout-1]: started with pid [12656] started core service [/rosout] process[ndt_matching-2]: started with pid [12659] terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error>

' what(): boost: mutex lock failed in pthread_mutex_lock: Invalid argument [ndt_matching-2] process has died [pid 12659, exit code -6, cmd /home/autoware/Autoware/install/lidar_localizer/lib/lidar_localizer/ndt_matching __name:=ndt_matching __log:=/root/.ros/log/5739dd7a-1c64-11ea-8d07-48a472bde50c/ndt_matching-2.log]. log file: /root/.ros/log/5739dd7a-1c64-11ea-8d07-48a472bde50c/ndt_matching-2*.log

Any idea why? I realized that this doesn't happen when I first launch the runtime manager and then kill the runtime manager's node from the command line and eventually launch ndt_matching.launch. This must be something configured when launching roslaunch runtime_manager runtime_manager.launch.

By the way, by default the ndt_matching method used is pcl_generic, and not pcl_anh or other, which I have read had some issues in the past with the same kind of error.

2019-12-12 11:42:10 -0500 received badge  Scholar (source)
2019-12-12 11:42:05 -0500 received badge  Supporter (source)
2019-12-11 16:32:01 -0500 asked a question Autoware - can't launch .launch file without runtime manager

Autoware - can't launch .launch file without runtime manager Ubuntu 16.04 Autoware Docker pre-built container autoware/

2019-12-11 16:07:11 -0500 received badge  Notable Question (source)
2019-12-04 12:05:19 -0500 commented answer Autoware.ai - Build package - colcon

@sgermanserrano @Maximus5684 Yes thanks, this is what I thought. After sourcing, roscd works fine. However, I added a

2019-12-03 13:41:29 -0500 received badge  Popular Question (source)
2019-12-03 13:41:16 -0500 commented answer Autoware.ai - Build package - colcon

Thanks ! It helps a lot ! Little concern about colcon create pkg <package_name> though. I'm getting the followin

2019-12-03 13:40:55 -0500 commented answer Autoware.ai - Build package - colcon

Thanks a lot, it helps a lot ! Little concern about colcon create pkg <package_name> though. I'm getting the fol

2019-12-03 13:13:22 -0500 received badge  Student (source)
2019-12-02 18:55:02 -0500 asked a question Autoware.ai - Build package - colcon

Autoware.ai - Build package - colcon Hi all, I am running on Ubuntu 16.04 with ROS Kinetic and Autoware's Docker image

2019-11-15 03:41:57 -0500 received badge  Famous Question (source)
2019-10-01 13:26:47 -0500 received badge  Notable Question (source)
2019-09-04 18:16:10 -0500 received badge  Enthusiast
2019-08-29 16:15:23 -0500 answered a question [Autoware 1.12.0] astar_avoid can't correct closest waypoint in some cases

I'm also very curious about this. Did you find out what was the issue ? Thanks

2019-08-29 13:58:21 -0500 commented answer [Autoware] Lidar fake perception

I see, thanks for the prompt answer. It helps a lot. I am getting this error now though: [ INFO] [1567104827.129211216

2019-08-29 13:57:56 -0500 commented answer [Autoware] Lidar fake perception

I see, thanks for the prompt answer. It helps a lot. I am getting this error now though: [ INFO] [1567104827.129211216

2019-08-29 01:21:46 -0500 received badge  Popular Question (source)
2019-08-27 17:42:46 -0500 asked a question [Autoware] Lidar fake perception

[Autoware] Lidar fake perception Hi all, Setup: - Ubuntu 16.04 - Ros Kinetic - Autoware - Docker I am trying to use