charkoteow's profile - activity

overview network karma followed questions activity

2023-04-13 18:47:28 -0500	received badge	● Taxonomist
2021-03-14 06:54:34 -0500	marked best answer	rviz 'measure' tool On rviz, there's a measure tool at the menu on top. How do I use it? It doesn't seem to be displaying any sort of 'measurement' like distance or coordinates. Edit: On ROS Hydro.
2020-06-23 09:09:01 -0500	received badge	● Good Question (source)
2018-01-30 21:31:50 -0500	marked best answer	terminate called after throwing an instance of 'openni_wrapper::OpenNIException' Tried the 3D Visualisation tutorial for the turtlebot. I'm having a hard time launching the kinect on my turtlebot laptop. Below are the terminal logs. (note that user@eko-gateway is my turtlebot laptop) user@eko-gateway:~$ roslaunch turtlebot_bringup 3dsensor.launch ... logging to /home/user/.ros/log/8a2a9104-1c4a-11e4-9db6-48d2241d08a9/roslaunch-eko-gateway-9515.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://10.42.0.1:34058/ SUMMARY ======== PARAMETERS * /camera/camera_nodelet_manager/num_worker_threads * /camera/depth_rectify_depth/interpolation * /camera/depth_registered_rectify_depth/interpolation * /camera/disparity_depth/max_range * /camera/disparity_depth/min_range * /camera/disparity_registered_hw/max_range * /camera/disparity_registered_hw/min_range * /camera/disparity_registered_sw/max_range * /camera/disparity_registered_sw/min_range * /camera/driver/depth_camera_info_url * /camera/driver/depth_frame_id * /camera/driver/depth_registration * /camera/driver/device_id * /camera/driver/rgb_camera_info_url * /camera/driver/rgb_frame_id * /depthimage_to_laserscan/output_frame_id * /depthimage_to_laserscan/range_min * /depthimage_to_laserscan/scan_height * /rosdistro * /rosversion NODES /camera/ camera_nodelet_manager (nodelet/nodelet) debayer (nodelet/nodelet) depth_metric (nodelet/nodelet) depth_metric_rect (nodelet/nodelet) depth_points (nodelet/nodelet) depth_rectify_depth (nodelet/nodelet) depth_registered_rectify_depth (nodelet/nodelet) disparity_depth (nodelet/nodelet) disparity_registered_hw (nodelet/nodelet) disparity_registered_sw (nodelet/nodelet) driver (nodelet/nodelet) points_xyzrgb_hw_registered (nodelet/nodelet) points_xyzrgb_sw_registered (nodelet/nodelet) rectify_color (nodelet/nodelet) rectify_ir (nodelet/nodelet) rectify_mono (nodelet/nodelet) register_depth_rgb (nodelet/nodelet) / depthimage_to_laserscan (nodelet/nodelet) ROS_MASTER_URI=http://10.42.0.1:11311 core service [/rosout] found process[camera/camera_nodelet_manager-1]: started with pid [9533] [ INFO] [1407210380.835627720]: Initializing nodelet with 4 worker threads. process[camera/driver-2]: started with pid [9555] process[camera/debayer-3]: started with pid [9576] process[camera/rectify_mono-4]: started with pid [9591] [ INFO] [1407210384.245259146]: Number devices connected: 1 [ INFO] [1407210384.247759899]: 1. device on bus 001:77 is a SensorV2 (2ae) from PrimeSense (45e) with serial id 'A00364A15558132A' [ INFO] [1407210384.256431370]: Searching for device with index = 1 [ INFO] [1407210384.380931401]: Opened 'SensorV2' on bus 1:77 with serial number 'A00364A15558132A' process[camera/rectify_color-5]: started with pid [9633] process[camera/rectify_ir-6]: started with pid [9672] process[camera/depth_rectify_depth-7]: started with pid [9695] [ INFO] [1407210387.201221214]: rgb_frame_id = '/camera_rgb_optical_frame' [ INFO] [1407210387.201518310]: depth_frame_id = '/camera_depth_optical_frame' [ WARN] [1407210387.253713214]: Camera calibration file /home/user/.ros/camera_info/rgb_A00364A15558132A.yaml not found. [ WARN] [1407210387.255078906]: Using default parameters for RGB camera calibration. [ WARN] [1407210387.256739764]: Camera calibration file /home/user/.ros/camera_info/depth_A00364A15558132A.yaml not found. [ WARN] [1407210387.259620976]: Using default parameters for IR camera calibration. process[camera/depth_metric_rect-8]: started with pid [9767] process[camera/depth_metric-9]: started with pid [9862] process[camera/depth_points-10]: started with pid [9950] process[camera/register_depth_rgb-11]: started with pid [10021] process[camera/points_xyzrgb_sw_registered-12]: started with pid [10090] process[camera/depth_registered_rectify_depth-13]: started with pid [10174] process[camera/points_xyzrgb_hw_registered-14]: started with pid [10249] process[camera/disparity_depth-15]: started with pid [10310] process[camera/disparity_registered_sw-16]: started with pid [10358] process[camera/disparity_registered_hw-17]: started with pid [10391] process[depthimage_to_laserscan-18]: started with pid [10438] terminate called after throwing an instance of 'openni_wrapper::OpenNIException' what(): virtual void openni_wrapper::OpenNIDevice::startImageStream() @ /tmp/buildd/ros-hydro-openni-camera-1.9.2-0precise-20140720-0559/src/openni_device.cpp @ 224 : starting image stream failed. Reason: Failed to send a USB control request! [camera/camera_nodelet_manager-1] process has died [pid 9533, exit code -6, cmd /opt/ros/hydro/lib/nodelet/nodelet manager __name:=camera_nodelet_manager ... (more)
2018-01-04 16:55:00 -0500	received badge	● Good Question (source)
2016-06-30 04:01:11 -0500	received badge	● Nice Question (source)
2016-06-11 21:14:31 -0500	received badge	● Nice Question (source)
2016-05-08 15:41:18 -0500	marked best answer	frontier_exploration with turtlebot I'm trying to get the frontier_exploration package to work with my TurtleBot. But so far it's not working. The launch file <launch> <node pkg="gmapping" type="slam_gmapping" name="slam_gmapping" output="screen"> <remap from="scan" to="/scan2" /> <rosparam> occ_thresh: 0.25 odom_frame: odom map_update_interval: 5.0 maxUrange: 6.0 maxRange: 8.0 sigma: 0.05 kernelSize: 1 lstep: 0.05 astep: 0.05 iterations: 5 lsigma: 0.075 ogain: 1.0 lskip: 0 srr: 0.01 srt: 0.02 str: 0.01 stt: 0.02 linearUpdate: 0.5 angularUpdate: 0.436 temporalUpdate: -1.0 resampleThreshold: 0.5 particles: 80 xmin: -1.0 ymin: -1.0 xmax: 1.0 ymax: 1.0 delta: 0.05 llsamplerange: 0.01 llsamplestep: 0.01 lasamplerange: 0.005 lasamplestep: 0.005 base_frame: base_link </rosparam> </node> <node name="rviz" pkg="rviz" type="rviz"> </node> <include file="$(find turtlebot_navigation)/launch/includes/velocity_smoother.launch.xml"/> <include file="$(find turtlebot_navigation)/launch/includes/safety_controller.launch.xml"/> <arg name="odom_topic" default="odom" /> <node pkg="move_base" type="move_base" respawn="false" name="move_base" output="screen"> <rosparam file="$(find turtlebot_navigation)/param/costmap_common_params.yaml" command="load" ns="global_costmap" /> <rosparam file="$(find turtlebot_navigation)/param/costmap_common_params.yaml" command="load" ns="local_costmap" /> <rosparam file="$(find turtlebot_navigation)/param/local_costmap_params.yaml" command="load" /> <rosparam file="$(find turtlebot_navigation)/param/global_costmap_params.yaml" command="load" /> <rosparam file="$(find turtlebot_navigation)/param/base_local_planner_params.yaml" command="load" /> <rosparam file="$(find turtlebot_navigation)/param/move_base_params.yaml" command="load" /> <remap from="cmd_vel" to="navigation_velocity_smoother/raw_cmd_vel"/> <remap from="odom" to="$(arg odom_topic)"/> </node> </launch> global_costmap_params.yaml `global_costmap: global_frame: /map robot_base_frame: /base_footprint update_frequency: 3.0 publish_frequency: 0.0 static_map: true transform_tolerance: 0.5` local_costmap_params.yaml `local_costmap: global_frame: /odom robot_base_frame: /base_footprint update_frequency: 5.0 publish_frequency: 2.0 static_map: false rolling_window: true width: 4.0 height: 4.0 resolution: 0.05 transform_tolerance: 0.5` Errors from the frontier_exploration terminal [ WARN] [1414574875.215553173]: Please select an initial point for exploration inside the polygon [ INFO] [1414574876.981956729]: Sending goal [ INFO] [1414574877.352866124]: Using plugin "static" [ INFO] [1414574877.621707478]: Requesting the map... [ INFO] [1414574877.775594588]: Resizing costmap to 576 X 288 at 0.050000 m/pix [ INFO] [1414574877.847249155]: Received a 576 X 288 map at 0.050000 m/pix [ INFO] [1414574877.847298258]: Subscribing to updates [ INFO] [1414574878.016550480]: Using plugin "explore_boundary" [ INFO] [1414574878.541237670]: Using plugin "sensor" [ INFO] [1414574878.664303536]: Subscribed to Topics: /scan2 [ INFO] [1414574879.327905514]: Using plugin "inflation" [ERROR] [1414574880.852823897]: Exception thrown while processing service call: Lookup would require extrapolation into the past. Requested time 1414574873.590463123 but the earliest data is at time 1414574878.157772422, when looking up transform from frame [odom] to frame [map] [ERROR] [1414574880.853237138]: Service call failed: service [/explore_server/explore_costmap/explore_boundary/update_boundary_polygon] responded with an error: Lookup would require extrapolation into the past. Requested time 1414574873.590463123 but the earliest data is at time 1414574878.157772422, when looking up transform from frame [odom] to frame [map] [ERROR] [1414574880.853397382]: Failed to set region boundary Errors from my gmapping launch file terminal `[ WARN] [1414574406.526808975]: Could not transform the global plan to the frame of the controller ...` (more)
2016-03-14 22:05:50 -0500	marked best answer	changing value 0/nan to max distance (urg/hokuyo node) Trying to map a quite big open space but some values returned from the node is 'nan' which i suspect are areas which has no obstacle or whatsoever at max distance. How can i turn this 'nan' into a defined value so gmapping can mark it as free space?
2016-02-16 01:46:25 -0500	marked best answer	RGBDSLAM V2 catkin_make error I'm trying to install the RGBDSLAM V2 using the steps that are shown here under the "Installation From Scratch" but failed and I can't figure out what's wrong with it. Base path: /home/ceastech/rgbdslam Source space: /home/ceastech/rgbdslam/src Build space: /home/ceastech/rgbdslam/build Devel space: /home/ceastech/rgbdslam/devel Install space: /home/ceastech/rgbdslam/install #### #### Running command: "make cmake_check_build_system" in "/home/ceastech/rgbdslam/build" #### #### #### Running command: "make -j4 -l4" in "/home/ceastech/rgbdslam/build" #### [ 14%] Built target siftgpu_proj [ 23%] Built target rgbdslam_generate_messages_py [ 30%] Built target rgbdslam_generate_messages_lisp [ 37%] Built target rgbdslam_generate_messages_cpp [ 37%] [ 37%] Built target rgbdslam_generate_messages Built target rgbdslam_gencpp [ 39%] [ 41%] [ 42%] [ 44%] Building CXX object rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/moc_openni_listener.o Building CXX object rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/moc_graph_manager.o Building CXX object rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/qtros.o Building CXX object rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/main.o [ 46%] Building CXX object rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/openni_listener.o /tmp/ccJWleRv.s: Assembler messages: /tmp/ccJWleRv.s:6501: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' /tmp/ccJWleRv.s:7191: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' make[2]: * [rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/moc_graph_manager.o] Error 1 make[2]: * Waiting for unfinished jobs.... /tmp/ccmwwdFs.s: Assembler messages: /tmp/ccmwwdFs.s:6316: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' /tmp/ccmwwdFs.s:7006: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' make[2]: * [rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/moc_openni_listener.o] Error 1 /tmp/ccemUxBv.s: Assembler messages: /tmp/ccemUxBv.s:9379: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' /tmp/ccemUxBv.s:10069: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' make[2]: * [rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/main.o] Error 1 /tmp/cci4xF2j.s: Assembler messages: /tmp/cci4xF2j.s:211470: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' /tmp/cci4xF2j.s:212160: Error: no such instruction: `vfmadd312ss (%ecx),%xmm0,%xmm1' make[2]: * [rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/src/openni_listener.o] Error 1 make[1]: * [rgbdslam_v2-hydro/CMakeFiles/rgbdslam.dir/all] Error 2 make: *** [all] Error 2 Invoking "make" failed
2015-11-12 11:26:42 -0500	received badge	● Famous Question (source)
2015-07-22 05:17:24 -0500	received badge	● Notable Question (source)
2015-05-06 04:33:35 -0500	commented question	frontier_exploration with turtlebot ...the one i've uploaded was mainly about gmapping & move_base. i think i should update my Q.
2015-05-06 04:32:47 -0500	commented question	frontier_exploration with turtlebot Almost all of it are the same. I've increased the transform tolerance, update_frequency, publish_frequency and changed robot_base_frame to base_link on the global costmap params and frontier's launch file. I think they must be the same. Check your launch file....
2015-05-06 01:09:27 -0500	commented question	frontier_exploration with turtlebot i really can't pin down the exact problem. sometimes it works, sometimes it doesn't. even with the clock synced properly and i also set the openni publish transform to false to fix the kinect's tf issues. we've moved on from mapping to olfaction recently so I can't help you much for the time being.
2015-04-21 15:47:25 -0500	received badge	● Popular Question (source)
2015-04-04 07:45:34 -0500	marked best answer	process[rosout-1] keeps repeating Followed the tutorial up till turtlebot bringup. (apparently i dont have enough karma to post links) Managed to SSH into the turtle bot laptop, then I tried the turtlebot_bringup minimal.launch and these came out on the terminal non stop `process[rosout-1]: started with pid [7331] terminate called after throwing an instance of 'std::runtime_error' what(): locale::facet::_S_create_c_locale name not valid` Help? Workstation is running ROS Indigo while the turtlebot laptop is running ROS hydro. Will different version of ROS complicate things? Or did I messed up somewhere during the installation?
2015-04-04 07:45:31 -0500	received badge	● Famous Question (source)
2015-03-22 17:36:17 -0500	received badge	● Famous Question (source)
2015-03-05 01:57:17 -0500	commented question	Octomap Self-filtering where's the error message?
2015-03-03 08:37:19 -0500	asked a question	Debugging OctoMap Running gmapping, octomap with the turtlebot. Fixed frame in rviz is "map" The launch file frame id is also "map" `<!-- fixed map frame (set to 'map' if SLAM or localization running!) --> <param name="frame_id" type="string" value="map" />` But no voxels are coming out on rviz. Quick change from map to base_footprint on both rviz and launch file fixed it but the 3D map is not good. I've learned that octomap_server needs a fixed frame id and a tf transform of the input PointCloud2 into this frame. and the frame needs to be "map" to produce a good 3D map. But something is wrong because nothing is coming out. So I rosrun rqt_console to debug. It shows `MessageFilter [target=map ]: The majority of dropped messages were due to messages growing older than the TF cache time. The last message's timestamp was: 1425390282.550442, and the last frame_id was: /camera_rgb_optical_frame` Where should I look first to correct this?
2015-03-03 06:21:31 -0500	commented answer	tf tree is invalide because it contains a loop worked for me too! thank you :)
2015-02-26 21:29:35 -0500	marked best answer	tf tree is invalide because it contains a loop I am trying to display my laserscan on rviz but its status flickers between Status:Ok and Status:Error because of Transform. Transform [sender=/depthimage_to_laserscan] For frame [camera_depth_frame]: No transform to fixed frame [base_footprint]. TF error: [The tf tree is invalid because it contains a loop. Frame camera_rgb_optical_frame exists with parent camera_rgb_frame. Frame camera_rgb_frame exists with parent base_link. Frame base_footprint exists with parent odom. Frame base_link exists with parent base_footprint. Frame left_cliff_sensor_link exists with parent base_link. Frame leftfront_cliff_sensor_link exists with parent base_link. Frame right_cliff_sensor_link exists with parent base_link. Frame rightfront_cliff_sensor_link exists with parent base_link. Frame wall_sensor_link exists with parent base_link. Frame camera_depth_frame exists with parent camera_rgb_frame. Frame camera_depth_optical_frame exists with parent camera_depth_frame. Frame camera_link exists with parent camera_rgb_frame. Frame front_wheel_link exists with parent base_link. Frame gyro_link exists with parent base_link. Frame base_laser_link exists with parent base_link. Frame laser exists with parent base_link. Frame plate_0_link exists with parent base_link. Frame plate_1_link exists with parent plate_0_link. Frame plate_2_link exists with parent plate_1_link. Frame plate_3_link exists with parent plate_2_link. Frame rear_wheel_link exists with parent base_link. Frame spacer_0_link exists with parent base_link. Frame spacer_1_link exists with parent base_link. Frame spacer_2_link exists with parent base_link. Frame spacer_3_link exists with parent base_link. Frame standoff_2in_0_link exists with parent base_link. Frame standoff_2in_1_link exists with parent base_link. Frame standoff_2in_2_link exists with parent base_link. Frame standoff_2in_3_link exists with parent base_link. Frame standoff_2in_4_link exists with parent standoff_2in_0_link. Frame standoff_2in_5_link exists with parent standoff_2in_1_link. Frame standoff_2in_6_link exists with parent standoff_2in_2_link. Frame standoff_2in_7_link exists with parent standoff_2in_3_link. Frame standoff_8in_0_link exists with parent standoff_2in_4_link. Frame standoff_8in_1_link exists with parent standoff_2in_5_link. Frame standoff_8in_2_link exists with parent standoff_2in_6_link. Frame standoff_8in_3_link exists with parent standoff_2in_7_link. Frame standoff_kinect_0_link exists with parent plate_2_link. Frame standoff_kinect_1_link exists with parent plate_2_link. Frame left_wheel_link exists with parent base_link. Frame right_wheel_link exists with parent base_link. Frame scan1 exists with parent cart_frame. Frame scan2 exists with parent cart_frame. ] How do I get rid of the error? EDIT: tf frames
2015-02-12 08:52:00 -0500	received badge	● Famous Question (source)
2015-01-16 22:34:19 -0500	received badge	● Notable Question (source)
2015-01-11 22:14:53 -0500	commented question	cannot connected kinect when use openni__node.launch under Hydro on ubuntu12.04 what does it say on the terminal?
2015-01-11 22:14:34 -0500	answered a question	cannot connected kinect when use openni__node.launch under Hydro on ubuntu12.04 edit: wasn't intending to write as an answer but as a comment. deleted.