-
Notifications
You must be signed in to change notification settings - Fork 51
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
[jsk_footstep_planner] pcl/PointCloudConcatenateDataSynchronizer seems to cause tf2::InvalidArgumentException #546
Comments
How did you solve this problem? > @aginika |
if you solve this issue offline, please describe how did you solve this. ◉ Kei Okada On Tue, Jan 19, 2016 at 8:29 PM, Kohei Kimura [email protected]
|
@k-kimura I didn't get any error when I try to do it in gdb. So I don't know the solution sorry. |
@aginika thanks.
I found this error issue while checking https://github.com/start-jsk/rtmros_hrp2/blob/master/jsk_hrp2_ros_bridge/launch/hrp2_multisense_local.launch#L135-#L138 with @orikuma san. |
Ping @k-kimura |
When I checked jsk_footstep_planner's heightmap.launch on mensa (hrp2 remote desktop PC) just now, it seems no error about Environment
Execution result of heightmap.launch
Then, the following topics about heightmap_visualization are published correctly.
|
Issue
roslaunch jsk_footstep_planner heightmap.launch
causestf2::InvalidArgumentException
.I checked nodelets in heightmap_nodelet as follows and I reproduced this error when robot_center_pointcloud_with_map_origin_points is commented in.
It seems the same error as [jsk_footstep_planner] Empty Frame error has occured in heightmap.launch with PR2 #424
/body_on_odom, /map and /odom_init are published as /tf.
Both /robot_center_pointcloud/output and /robot_center_map_origin_points/output have /body_on_odom as their frame_id in headers.
Environment
hrp2007v with multisenseSL (firmware version 0x0303)
jsk_recognition at master in 810ba37c4fb36bc9d2fafd4329d7cb4d86c1a87d
jsk_common at master in 1a0ecef4643ec4b4a238b95d05f0f516584a510c
jsk_control at master in 79f4aab
ros-hydro-pcl-ros 1.1.11-0precise-20150111-0931-+0000 from apt
heightmap.launch is modified to use heightmap_nodelet (not to be combined with multisense_laser)
How to reproduce
gdb output
The text was updated successfully, but these errors were encountered: