konet's profile - activity

overview network karma followed questions activity

2018-07-28 05:30:26 -0500	received badge	● Taxonomist
2015-01-11 23:45:17 -0500	received badge	● Notable Question (source)
2015-01-11 23:45:17 -0500	received badge	● Famous Question (source)
2014-01-27 08:13:23 -0500	received badge	● Famous Question (source)
2013-11-22 11:04:49 -0500	marked best answer	pointcloud_to_laserscan error on eddiebot stack Hi everybody, I'm trying to run successfully the following launch file: robotictang/eddiebot/blob/master/eddiebot/eddiebot_bringup/kinect.launch root@ubuntu:/opt/ros/groovy/share# roslaunch eddiebot_bringup kinect.launch ... logging to /home/omar/.ros/log/08c16556-8f48-11e2-9041-68a3c42c6822/roslaunch-ubuntu-7662.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server SUMMARY ======== PARAMETERS * /kinect_laser/max_height * /kinect_laser/min_height * /kinect_laser/output_frame_id * /kinect_laser_narrow/max_height * /kinect_laser_narrow/min_height * /kinect_laser_narrow/output_frame_id * /openni_launch/debayering * /openni_launch/depth_frame_id * /openni_launch/depth_mode * /openni_launch/depth_registration * /openni_launch/depth_time_offset * /openni_launch/image_mode * /openni_launch/image_time_offset * /openni_launch/rgb_frame_id * /pointcloud_throttle/max_rate * /rosdistro * /rosversion NODES / kinect_laser (nodelet/nodelet) kinect_laser_narrow (nodelet/nodelet) openni_launch (nodelet/nodelet) openni_manager (nodelet/nodelet) pointcloud_throttle (nodelet/nodelet) core service [/rosout] found process[openni_manager-1]: started with pid [7683] process[openni_launch-2]: started with pid [7684] process[pointcloud_throttle-3]: started with pid [7704] process[kinect_laser-4]: started with pid [7730] process[kinect_laser_narrow-5]: started with pid [7764] [ INFO] [1363556169.497509524]: Initializing nodelet with 4 worker threads. [ERROR] [1363556169.517297970]: Failed to load nodelet [/pointcloud_throttle] of type [pointcloud_to_laserscan/CloudThrottle]: According to the loaded plugin descriptions the class pointcloud_to_laserscan/CloudThrottle with base class type nodelet::Nodelet does not exist. Declared types are depth_image_proc/convert_metric depth_image_proc/disparity depth_image_proc/point_cloud_xyz depth_image_proc/point_cloud_xyzrgb depth_image_proc/register depthimage_to_laserscan/DepthImageToLaserScanNodelet image_proc/crop_decimate image_proc/debayer image_proc/rectify image_view/disparity image_view/image nodelet_tutorial_math/Plus openni_camera/driver pcl/BAGReader pcl/ExtractIndices pcl/NodeletDEMUX pcl/NodeletMUX pcl/PCDReader pcl/PCDWriter pcl/PassThrough pcl/PointCloudConcatenateDataSynchronizer pcl/PointCloudConcatenateFieldsSynchronizer pcl/ProjectInliers pcl/StatisticalOutlierRemoval pcl/VoxelGrid stereo_image_proc/disparity stereo_image_proc/point_cloud stereo_image_proc/point_cloud2 uvc_camera/CameraNodelet uvc_camera/StereoNodelet [ERROR] [1363556169.522330024]: Failed to load nodelet [/kinect_laser] of type [pointcloud_to_laserscan/CloudToScan]: According to the loaded plugin descriptions the class pointcloud_to_laserscan/CloudToScan with base class type nodelet::Nodelet does not exist. Declared types are depth_image_proc/convert_metric depth_image_proc/disparity depth_image_proc/point_cloud_xyz depth_image_proc/point_cloud_xyzrgb depth_image_proc/register depthimage_to_laserscan/DepthImageToLaserScanNodelet image_proc/crop_decimate image_proc/debayer image_proc/rectify image_view/disparity image_view/image nodelet_tutorial_math/Plus openni_camera/driver pcl/BAGReader pcl/ExtractIndices pcl/NodeletDEMUX pcl/NodeletMUX pcl/PCDReader pcl/PCDWriter pcl/PassThrough pcl/PointCloudConcatenateDataSynchronizer pcl/PointCloudConcatenateFieldsSynchronizer pcl/ProjectInliers pcl/StatisticalOutlierRemoval pcl/VoxelGrid stereo_image_proc/disparity stereo_image_proc/point_cloud stereo_image_proc/point_cloud2 uvc_camera/CameraNodelet uvc_camera/StereoNodelet [FATAL] [1363556169.523161694]: Service call failed! [FATAL] [1363556169.524654815]: Service call failed! [ERROR] [1363556169.525195480]: Failed to load nodelet [/kinect_laser_narrow] of type [pointcloud_to_laserscan/CloudToScan]: According to the loaded plugin descriptions the class pointcloud_to_laserscan/CloudToScan with base class type nodelet::Nodelet does not exist. Declared types are depth_image_proc/convert_metric depth_image_proc/disparity depth_image_proc/point_cloud_xyz depth_image_proc/point_cloud_xyzrgb depth_image_proc/register depthimage_to_laserscan/DepthImageToLaserScanNodelet image_proc/crop_decimate image_proc/debayer image_proc/rectify image_view/disparity image_view/image nodelet_tutorial_math/Plus openni_camera/driver pcl/BAGReader pcl/ExtractIndices pcl/NodeletDEMUX pcl/NodeletMUX pcl/PCDReader pcl/PCDWriter pcl/PassThrough pcl/PointCloudConcatenateDataSynchronizer pcl/PointCloudConcatenateFieldsSynchronizer pcl/ProjectInliers pcl/StatisticalOutlierRemoval pcl/VoxelGrid stereo_image_proc/disparity stereo_image_proc/point_cloud stereo_image_proc/point_cloud2 uvc_camera/CameraNodelet uvc_camera/StereoNodelet [FATAL] [1363556169.526699191]: Service call failed! [ERROR] [1363556169.528594041]: Failed to load nodelet [/openni_launch] of type [openni_camera/OpenNINodelet]: According to the loaded plugin descriptions the class openni_camera/OpenNINodelet with base class type nodelet::Nodelet does not exist. Declared types are depth_image_proc/convert_metric depth_image_proc/disparity depth_image_proc/point_cloud_xyz depth_image_proc/point_cloud_xyzrgb ... (more)
2013-09-02 04:09:27 -0500	received badge	● Notable Question (source)
2013-07-31 23:33:07 -0500	received badge	● Famous Question (source)
2013-07-04 06:12:47 -0500	received badge	● Famous Question (source)
2013-06-21 00:15:06 -0500	received badge	● Popular Question (source)
2013-06-08 07:08:11 -0500	received badge	● Popular Question (source)
2013-04-24 13:47:35 -0500	received badge	● Notable Question (source)
2013-04-23 01:09:14 -0500	received badge	● Popular Question (source)
2013-04-22 05:07:59 -0500	asked a question	using turtlebot tf's for another robot Hi everyone, I have an eddie robot running the package "eddiebot" for it's integration with ros. the eddiebot package uses the turtlebot APIs. so I was wondering if I can use the Turtlebot code regarding the tf configurations for the eddie, and if so were I can find that code to port it to the eddie. the only difference between the eddie and the turtlebot it's that it doesn't have an IMU. so I'll need to disable that part of the code.
2013-04-22 03:40:42 -0500	received badge	● Famous Question (source)
2013-04-22 03:40:42 -0500	received badge	● Notable Question (source)
2013-04-14 05:55:05 -0500	received badge	● Popular Question (source)
2013-04-11 18:25:25 -0500	asked a question	succesfully running gazebo but cannot run simulator_gazebo hey guys take a look at the following code: successful run: `root@ubuntu:/opt/ros/groovy/stacks# gazebo Gazebo multi-robot simulator, version 1.6.1 Copyright (C) 2013 Open Source Robotics Foundation. Released under the Apache 2 License.` gazebosim.org Msg Waiting for master.Gazebo multi-robot simulator, version 1.6.1 Copyright (C) 2013 Open Source Robotics Foundation. Released under the Apache 2 License. gazebosim.org Warning [parser.cc:361] Converting a deprecated SDF source[/usr/share/gazebo-1.6/worlds/empty.world]. Warning [Converter.cc:61] Version[1.3] to Version[1.4] Please use the gzsdf tool to update your SDF files. $ gzsdf convert [sdf_file] Warning [parser.cc:361] Converting a deprecated SDF source[/home/konet/.gazebo/models/sun/model.sdf]. Set SDF value Warning [Converter.cc:61] Version[1.2] to Version[1.4] Please use the gzsdf tool to update your SDF files. $ gzsdf convert [sdf_file] Warning [parser.cc:361] Converting a deprecated SDF source[/home/konet/.gazebo/models/ground_plane/model.sdf]. Set SDF value Warning [Converter.cc:61] Version[1.2] to Version[1.4] Please use the gzsdf tool to update your SDF files. $ gzsdf convert [sdf_file] Msg Waiting for master Msg Connected to gazebo master @ //127.0.0.1:11345 Msg Publicized address: 192.168.0.19 Msg Connected to gazebo master @ //127.0.0.1:11345 Msg Publicized address: 192.168.0.19 non-successful run: root@ubuntu:/opt/ros/groovy/stacks# roslaunch gazebo_worlds empty_world.launch ... logging to /home/konet/.ros/log/6fa89b8e-a327-11e2-909e-68a3c42c6822/roslaunch-ubuntu-3071.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server //ubuntu:41494/ SUMMARY ======== PARAMETERS * /rosdistro * /rosversion * /use_sim_time NODES / gazebo (gazebo/gazebo) gazebo_gui (gazebo/gui) auto-starting new master process[master]: started with pid [3085] ROS_MASTER_URI=//localhost:11311 setting /run_id to 6fa89b8e-a327-11e2-909e-68a3c42c6822 process[rosout-1]: started with pid [3098] started core service [/rosout] process[gazebo-2]: started with pid [3112] process[gazebo_gui-3]: started with pid [3121] Gazebo multi-robot simulator, version 1.3.0 Copyright (C) 2012 Nate Koenig, John Hsu, and contributors. Released under the Apache 2 License. //gazebosim.org Gazebo multi-robot simulator, version 1.3.0 Copyright (C) 2012 Nate Koenig, John Hsu, and contributors. Released under the Apache 2 License. //gazebosim.org Warning [parser.cc:361] Converting a deprecated SDF source[/opt/ros/groovy/stacks/simulator_gazebo/gazebo_worlds/worlds/empty.world]. Set SDF value Version[1.2] to Version[1.3] Please use the gzsdf tool to update your SDF files. $ gzsdf convert [sdf_file] Msg Waiting for master Msg Connected to gazebo master @ //127.0.0.1:11345 Msg Publicized address: 192.168.0.19 [ INFO] [1365740057.248876597]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting... Error [Rendering.cc:37] Failed to load the Rendering engine subsystem unable to find OpenGL rendering system. OGRE is probably installed incorrectly. Double check the OGRE cmake output, and make sure OpenGL is enabled. Msg Waiting for master Msg Connected to gazebo master @ //127.0.0.1:11345 Msg ... (more)
2013-04-11 04:38:40 -0500	received badge	● Famous Question (source)
2013-04-10 07:38:04 -0500	asked a question	error in rosmake eddiebot_follower Hi Guys I'm trying to make the following package: github.com/robotictang/eddiebot_follower but I receive the following errors: root@ubuntu:/opt/ros/groovy/stacks# rosmake eddiebot_follower [ rosmake ] rosmake starting... [ rosmake ] Packages requested are: ['eddiebot_follower'] [ rosmake ] Logging to directory /home/konet/.ros/rosmake/rosmake_output-20130410-123224 [ rosmake ] Expanded args ['eddiebot_follower'] to: ['eddiebot_follower'] [rosmake-0] Starting >>> catkin [ make ] [rosmake-0] Finished <<< catkin ROS_NOBUILD in package catkin No Makefile in package catkin [rosmake-0] Starting >>> cpp_common [ make ] [rosmake-1] Starting >>> rospack [ make ] [rosmake-2] Starting >>> smclib [ make ] [rosmake-3] Starting >>> genmsg [ make ] [rosmake-0] Finished <<< cpp_common ROS_NOBUILD in package cpp_common No Makefile in package cpp_common [rosmake-1] Finished <<< rospack ROS_NOBUILD in package rospack No Makefile in package rospack [rosmake-0] Starting >>> rostime [ make ] [rosmake-3] Finished <<< genmsg ROS_NOBUILD in package genmsg No Makefile in package genmsg [rosmake-3] Starting >>> genlisp [ make ] [rosmake-1] Starting >>> roslib [ make ] [rosmake-2] Finished <<< smclib ROS_NOBUILD in package smclib No Makefile in package smclib [rosmake-3] Finished <<< genlisp ROS_NOBUILD in package genlisp No Makefile in package genlisp [rosmake-3] Starting >>> genpy [ make ] [rosmake-0] Finished <<< rostime ROS_NOBUILD in package rostime No Makefile in package rostime [rosmake-2] Starting >>> gencpp [ make ] [rosmake-1] Finished <<< roslib ROS_NOBUILD in package roslib No Makefile in package roslib [rosmake-1] Starting >>> rosunit [ make ] [rosmake-0] Starting >>> roscpp_traits [ make ] [rosmake-3] Finished <<< genpy ROS_NOBUILD in package genpy No Makefile in package genpy [rosmake-3] Starting >>> roslang [ make ] [rosmake-2] Finished <<< gencpp ROS_NOBUILD in package gencpp No Makefile in package gencpp [rosmake-2] Starting >>> message_generation [ make ] [rosmake-1] Finished <<< rosunit ROS_NOBUILD in package rosunit No Makefile in package rosunit [rosmake-1] Starting >>> rosconsole [ make ] [rosmake-0] Finished <<< roscpp_traits ROS_NOBUILD in package roscpp_traits No Makefile in package roscpp_traits [rosmake-0] Starting >>> roscpp_serialization [ make ] [rosmake-3] Finished <<< roslang ROS_NOBUILD in package roslang No Makefile in package roslang [rosmake-3] Starting >>> xmlrpcpp [ make ] [rosmake-2] Finished <<< message_generation ROS_NOBUILD in package message_generation No Makefile in package message_generation [rosmake-2] Starting >>> console_bridge [ make ] [rosmake-1] Finished <<< rosconsole ROS_NOBUILD in package rosconsole No Makefile in package rosconsole [rosmake-1] Starting >>> rosgraph [ make ] [rosmake-0] Finished <<< roscpp_serialization ROS_NOBUILD in package roscpp_serialization No Makefile in package roscpp_serialization [rosmake-0] Starting >>> message_runtime [ make ] [rosmake-1] Finished <<< rosgraph ROS_NOBUILD in package rosgraph No Makefile in package rosgraph [rosmake-1] Starting >>> rosparam [ make ] [rosmake-2] Finished <<< console_bridge ROS_NOBUILD in package console_bridge No Makefile in package console_bridge [rosmake-2] Starting >>> class_loader [ make ] [rosmake-3] Finished <<< xmlrpcpp ROS_NOBUILD in package xmlrpcpp No Makefile in package xmlrpcpp [rosmake-3] Starting >>> rosmaster [ make ] [rosmake-0] Finished <<< message_runtime ROS_NOBUILD in package message_runtime No Makefile in package message_runtime [rosmake-0] Starting >>> std_msgs [ make ] [rosmake-1] Finished <<< rosparam ROS_NOBUILD in package rosparam No Makefile in package rosparam [rosmake-3] Finished <<< rosmaster ROS_NOBUILD in package rosmaster No Makefile in package rosmaster [rosmake-1] Starting >>> rosclean [ make ] [rosmake-3] Starting >>> angles [ make ] [rosmake-2] Finished <<< class_loader ROS_NOBUILD in package class_loader No Makefile in package class_loader [rosmake-2] Starting >>> pluginlib [ make ] [rosmake-0] Finished <<< std_msgs ROS_NOBUILD in package std_msgs No Makefile in package std_msgs [rosmake-0] Starting >>> rosgraph_msgs [ make ] [rosmake-3] Finished <<< angles ROS_NOBUILD in package angles No Makefile in package angles [rosmake-1] Finished <<< rosclean ROS_NOBUILD in package rosclean No Makefile in package rosclean [rosmake-0] Finished <<< rosgraph_msgs ROS_NOBUILD in package rosgraph_msgs No Makefile in package rosgraph_msgs [rosmake-3] Starting >>> roscpp [ make ] [rosmake-2] Finished <<< pluginlib ROS_NOBUILD in package pluginlib No Makefile ... (more)
2013-04-10 06:54:57 -0500	answered a question	pointcloud_to_laserscan error on eddiebot stack Hey Guys, now I'm trying to run this kinect launch (based on turlebot 3dsensor.launch) it gets stuck on the last line of the following code: root@ubuntu:~# roslaunch eddiebot_bringup kinect.launch ... logging to /home/konet/.ros/log/2e88ae1c-a1fd-11e2-909e-68a3c42c6822/roslaunch-ubuntu-28243.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB. started roslaunch server http://ubuntu:36231/ SUMMARY ======== PARAMETERS * /camera/depth_registered/rectify_depth/interpolation * /camera/depthimage_to_laserscan_loader/output_frame_id * /camera/depthimage_to_laserscan_loader/range_min * /camera/depthimage_to_laserscan_loader/scan_height * /camera/openni_camera_loader/depth_frame_id * /camera/openni_camera_loader/depth_mode * /camera/openni_camera_loader/depth_registration * /camera/openni_camera_loader/depth_time_offset * /camera/openni_camera_loader/image_mode * /camera/openni_camera_loader/image_time_offset * /camera/openni_camera_loader/rgb_frame_id * /rosdistro * /rosversion NODES /camera/ camera_nodelet_manager (nodelet/nodelet) depthimage_to_laserscan_loader (nodelet/nodelet) openni_camera_loader (nodelet/nodelet) points_xyzrgb (nodelet/nodelet) /camera/depth_registered/ rectify_depth (nodelet/nodelet) /camera/rgb/ debayer (nodelet/nodelet) rectify_color (nodelet/nodelet) rectify_mono (nodelet/nodelet) auto-starting new master process[master]: started with pid [28272] setting /run_id to 2e88ae1c-a1fd-11e2-909e-68a3c42c6822 process[rosout-1]: started with pid [28285] started core service [/rosout] process[camera/camera_nodelet_manager-2]: started with pid [28297] process[camera/openni_camera_loader-3]: started with pid [28300] process[camera/rgb/debayer-4]: started with pid [28324] process[camera/rgb/rectify_mono-5]: started with pid [28349] process[camera/rgb/rectify_color-6]: started with pid [28405] process[camera/depth_registered/rectify_depth-7]: started with pid [28449] process[camera/points_xyzrgb-8]: started with pid [28484] process[camera/depthimage_to_laserscan_loader-9]: started with pid [28526] it doesn't show any errors but it doesn't start either, it gets stuck there. EDIT: it seems that the error is not that the process gets "stuck" the error is that this launch file is not related with the kinect hardware... in other words it works with or without the kinect connected to my computer. any suggestions to fix this? any help will be very apreciated. thank you!
2013-03-29 16:22:32 -0500	asked a question	turtlebot simulator groovy Hello Guys does anybody knows a workaround for this simulator to work under Groovy? Thanks!
2013-03-29 15:07:19 -0500	received badge	● Notable Question (source)
2013-03-25 21:06:34 -0500	answered a question	port of turtlebot_navigation HI Fergs, Thank you for your answer. What you are proposing is more concerned on creating the navigation stack from scratch right? Because I just wanted to know if there is a way of reusing as much code as possible from the turtlebot_navigation stack, since the eddie uses the turtlebot API.
2013-03-24 19:39:42 -0500	received badge	● Notable Question (source)
2013-03-22 12:24:08 -0500	received badge	● Popular Question (source)
2013-03-22 06:49:35 -0500	asked a question	port of turtlebot_navigation Hello everyone, I want to port the turtlebot_navigation stack to a robot called eddie, which it uses the turtlebot API to use it under ros which is the follwing: http://www.ros.org/wiki/eddiebot After successfully running that package I have 2 basic nodes running: minimal.launch kinect.launch this is the stack for the turtlebot navigation (which is needed for SLAM): http://ros.org/wiki/turtlebot_navigation?distro=groovy which has the following dependencies: Dependencies (3) `gmapping move_base turtlebot_bringup` In our case we already have the turtlebot_bringup. and I think the "gmapping" package is a generic one so it doesn't needs to be modify if I'm correct. The problem is that the move_base package needs to be made for the eddiebot, so I was going to ask you what do I need to do to get this package running? Thanks, Omar
2013-03-21 02:56:57 -0500	answered a question	Gmapping with eddiebot package (Based on turtlebot API) My question is if it could be possible to use the "turtlebot_navigation" package for this purposes. the question is what do I need to modify to make it work? my idea is to modify only certain parameters for example in the launch file: <launch> <include file="$(find eddie_bringup)/launch/3dsensor.launch"> <arg name="rgb_processing" value="false"/> <arg name="depth_registration" value="false"/> <arg name="depth_processing" value="false"/> </include> <include file="$(find turtlebot_navigation)/launch/includes/_gmapping.launch"/> <include file="$(find turtlebot_navigation)/launch/includes/_move_base.launch"/> </launch> to <launch> <include file="$(find eddie_bringup)/launch/kinect.launch"> <arg name="rgb_processing" value="false"/> <arg name="depth_registration" value="false"/> <arg name="depth_processing" value="false"/> </include> <include file="$(find eddie_navigation)/launch/includes/_gmapping.launch"/> <include file="$(find eddie_navigation)/launch/includes/_move_base.launch"/> </launch> it could be as simple as that? since the eddiebot is using the turtlebot API's Omar
2013-03-20 21:04:10 -0500	received badge	● Popular Question (source)
2013-03-20 17:40:50 -0500	asked a question	Gmapping with eddiebot package (Based on turtlebot API) Hello Guys, I;m trying to use this package: http://www.ros.org/wiki/gmapping with the eddie robot (parallax) using the eddiebot stack (Based on Turtlebot API) http://www.ros.org/wiki/eddiebot I already have the bringup runing (kinect.launch and minimal.launch) but I would like to know how to get gmapping running I dont know if it could be possible to use the gmapping code from the turtlebot and port it to work with eddie. http://www.ros.org/wiki/turtlebot_navigation/Tutorials/Build%20a%20map%20with%20SLAM what should I do to port it? if it could be possible to use the "turtlebot_navigation" package for this purposes. what do I need to modify to make it work? my idea is to modify only certain parameters for example in the launch file: <launch> <include file="$(find eddie_bringup)/launch/3dsensor.launch"> <arg name="rgb_processing" value="false"/> <arg name="depth_registration" value="false"/> <arg name="depth_processing" value="false"/> </include> <include file="$(find turtlebot_navigation)/launch/includes/_gmapping.launch"/> <include file="$(find turtlebot_navigation)/launch/includes/_move_base.launch"/> </launch> to <launch> <include file="$(find eddie_bringup)/launch/kinect.launch"> <arg name="rgb_processing" value="false"/> <arg name="depth_registration" value="false"/> <arg name="depth_processing" value="false"/> </include> <include file="$(find eddie_navigation)/launch/includes/_gmapping.launch"/> <include file="$(find eddie_navigation)/launch/includes/_move_base.launch"/> </launch> it could be as simple as that? since the eddiebot is using the turtlebot API's thank you! Omar
2013-03-20 17:33:36 -0500	received badge	● Editor (source)
2013-03-20 17:33:36 -0500	edited answer	pointcloud_to_laserscan error on eddiebot stack thank you it worked, here is my generic kinect.launch file <launch> <include file="$(find openni_launch)/launch/openni.launch"/> <node pkg="nodelet" type="nodelet" name="kinect_laser" args="load depthimage_to_laserscan/DepthImageToLaserScanNodelet camera_nodelet_manager"> <remap from="image" to="/camera/depth/image_raw"/> </node> </launch> do I need to modify anything else?