mohakbhardwaj's profile - activity

overview network karma followed questions activity

2018-10-23 20:37:23 -0500	received badge	● Student (source)
2017-02-23 05:00:19 -0500	received badge	● Famous Question (source)
2016-09-20 13:31:18 -0500	received badge	● Notable Question (source)
2016-07-14 13:34:35 -0500	received badge	● Scholar (source)
2016-07-14 13:34:32 -0500	commented answer	robot_localization does not produce odom->base_link transform Thanks! It is now publishing the transform. I have one confusion thought, is there anything in the parameters file that I am missing for the robot_localization package to compute x,y,z position from the rates and accelerations only? It is constantly publishing the x,y,z position as zero
2016-07-14 03:34:29 -0500	received badge	● Famous Question (source)
2016-07-13 16:52:02 -0500	commented question	robot_localization does not produce odom->base_link transform @Arwen: Yes that seems very unnatural to me as well. I have included links the launch files in my original post now. I have a data_publisher package which has the responsibility of publishing the imu data (only rotation rates and linear accelerations in my case) as a sensor_msgs/Imu message
2016-07-13 16:49:47 -0500	received badge	● Editor (source)
2016-07-13 12:49:01 -0500	commented question	robot_localization does not produce odom->base_link transform @Arwen I have edited the answer to include an image of the tf tree. It shows the odom frame being published as not connected to any other frame but as a floating frame. The static transform publisher is used to publish the transform from the location where the imu is mounted on the system to the bas
2016-07-13 12:32:40 -0500	received badge	● Notable Question (source)
2016-07-11 22:15:55 -0500	received badge	● Popular Question (source)
2016-07-10 23:16:07 -0500	asked a question	robot_localization does not produce odom->base_link transform Hello everyone, I have been searching for a long time for my problem but still have not found a solution. I am using robot_localization with IMU data. My imu data is published to a topic `/inertial_data` with `frame_id = "imu"`. The following is my configuration file frequency: 30 sensor_timeout: 0.1 transform_time_offset: 0.0 two_d_mode: false print_diagnostics: true debug: false debug_out_file: /home/mohak/catkin_ws/debug_file.txt map_frame: map odom_frame: odom base_link_frame: base world_frame: odom use_control: true stamped_control: false control_timeout: 0.2 control_config: [true, false, false, false, false, true] acceleration_limits: [1.3, 0.0, 0.0, 0.0, 0.0, 3.4] deceleration_limits: [1.3, 0.0, 0.0, 0.0, 0.0, 4.5] acceleration_gains: [0.8, 0.0, 0.0, 0.0, 0.0, 0.9] deceleration_gains: [1.0, 0.0, 0.0, 0.0, 0.0, 1.0] imu0: /inertial_data imu0_config: [false, false, false, false, false, false, false, false, false, true, true, true, true, true, true] imu0_nodelay: false imu0_queue_size: 5 imu0_pose_rejection_threshold: 0.8 imu0_twist_rejection_threshold: 0.8 imu0_linear_acceleration_rejection_threshold: 0.8 process_noise_covariance: [0.05, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.05, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.06, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.03, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.03, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.06, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.025, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.025, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.04, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.02, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.01, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.015] initial_estimate_covariance: [1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1e-9, 0, 0, 0, 0, 0, 0, 0 ... (more)
2016-06-29 13:20:49 -0500	received badge	● Popular Question (source)
2016-06-29 13:20:49 -0500	received badge	● Popular Question (source)
2016-06-29 00:41:01 -0500	received badge	● Enthusiast
2016-06-28 20:41:05 -0500	asked a question	Time synchronization when using multiple cameras with image_transport Hello, I am using multiple USB cameras for a project and am facing problems with time synchronization. I am currently using image_transport library's subscribeCamera function to subscribe to camera_info and image_rect_color published by image_proc. While one of my cameras is working fine, the second camera is dropping frames due to camera_info being published at a lower rate than the image messages. The following is the warning I am receiving: `[ WARN] [1467164006.770029982]: [image_transport] Topics '/usb_cam_2/image_rect_color' and '/usb_cam_2/camera_info' do not appear to be synchronized. In the last 10s: Image messages received: 120 CameraInfo messages received: 94 Synchronized pairs: 6` I have seen a few related answers such as this one link: http://answers.ros.org/question/69925... but in my case one of the cameras is working fine with just subscribeCamera. I was wondering what the reason could be specially for the camera_info being published at a lower rate than the image messages and whether this is something that I can rectify without ApproximateTime message filters as suggested in the answer in the link. Thanks in advance!
2016-03-18 16:05:08 -0500	received badge	● Famous Question (source)
2015-12-31 02:31:29 -0500	received badge	● Notable Question (source)
2015-11-17 01:49:27 -0500	received badge	● Popular Question (source)
2015-11-16 10:19:01 -0500	asked a question	Xaxxon Oculus Prime Platform: using a different SBC than the one sold by manufacturer I am using the kit version Oculus Prime Mobile Platform sold by Xaxxon for a project and was planning to use and Odroid XU4 running ROS. But, the problem I faced was that the Odroid XU4 has a 32bit processor whereas the server application and ROS packages written for Oculus Prime run only on 64bit. Here are the links for the documentation and server application: Documentation - http://www.xaxxon.com/documentation/v... Server Application - https://www.xaxxon.com/oculusprime/do... Could anyone tell me if: There is a 32-bit variant or any other way to run the server application and ROS packages on the Odroid. Will any single board computer with a 64-bit architecture be able to run the required packages or is there any special configuration in the motherboard that they sell. (is this the case with all such platforms in general) Which single board computers would be ideal for this situation so that I can purchase them? Thanks
2015-11-11 10:39:35 -0500	commented question	ros-pcl and vtk error I had the libraries except libvtk6. I installed it using synaptic, but the error still persists. I tried to find a way to use ccmake to set the path for libvtk6 but couldn't figure that out as well
2015-11-11 06:15:24 -0500	received badge	● Popular Question (source)
2015-11-09 06:19:52 -0500	asked a question	ros-pcl and vtk error Hi, For my project I have to use Kinect with ROS-pcl and openni. My machine has ROS-Indigo on it. While trying to run the cylinder_segmentation tutorial from point cloud library, after I run the `make` command after having run `cmake .` the following error occurs: Linking CXX executable cylinder_segmentation/usr/bin/ld: cannot find -lvtkGUISupportQtSQL /usr/bin/ld: cannot find -lvtkIOSQL /usr/bin/ld: cannot find -lvtkIOCore /usr/bin/ld: cannot find -lvtkCommonDataModel /usr/bin/ld: cannot find -lvtkCommonMath /usr/bin/ld: cannot find -lvtkCommonCore /usr/bin/ld: cannot find -lvtkCommonMisc /usr/bin/ld: cannot find -lvtkCommonSystem /usr/bin/ld: cannot find -lvtkCommonTransforms /usr/bin/ld: cannot find -lvtkCommonExecutionModel /usr/bin/ld: cannot find -lvtksqlite /usr/bin/ld: cannot find -lvtkIOXMLParser /usr/bin/ld: cannot find -lvtkPythonInterpreter /usr/bin/ld: cannot find -lvtkImagingStencil /usr/bin/ld: cannot find -lvtkCommonComputationalGeometry /usr/bin/ld: cannot find -lvtkImagingCore /usr/bin/ld: cannot find -lvtkIOODBC /usr/bin/ld: cannot find -lvtkGUISupportQtWebkit /usr/bin/ld: cannot find -lvtkViewsQt /usr/bin/ld: cannot find -lvtkGUISupportQt /usr/bin/ld: cannot find -lvtkInteractionStyle /usr/bin/ld: cannot find -lvtkRenderingCore /usr/bin/ld: cannot find -lvtkFiltersExtraction /usr/bin/ld: cannot find -lvtkFiltersCore /usr/bin/ld: cannot find -lvtkFiltersGeneral /usr/bin/ld: cannot find -lvtkFiltersStatistics /usr/bin/ld: cannot find -lvtkImagingFourier /usr/bin/ld: cannot find -lvtkFiltersGeometry /usr/bin/ld: cannot find -lvtkFiltersSources /usr/bin/ld: cannot find -lvtkIOImage /usr/bin/ld: cannot find -lvtkRenderingOpenGL /usr/bin/ld: cannot find -lvtkImagingHybrid /usr/bin/ld: cannot find -lvtkViewsInfovis /usr/bin/ld: cannot find -lvtkFiltersImaging /usr/bin/ld: cannot find -lvtkImagingGeneral /usr/bin/ld: cannot find -lvtkImagingSources /usr/bin/ld: cannot find -lvtkFiltersModeling /usr/bin/ld: cannot find -lvtkInfovisLayout /usr/bin/ld: cannot find -lvtkInfovisCore /usr/bin/ld: cannot find -lvtkRenderingContext2D /usr/bin/ld: cannot find -lvtkRenderingFreeType /usr/bin/ld: cannot find -lvtkRenderingLabel /usr/bin/ld: cannot find -lvtkViewsCore /usr/bin/ld: cannot find -lvtkInteractionWidgets /usr/bin/ld: cannot find -lvtkFiltersHybrid /usr/bin/ld: cannot find -lvtkRenderingAnnotation /usr/bin/ld: cannot find -lvtkImagingColor /usr/bin/ld: cannot find -lvtkRenderingVolume /usr/bin/ld: cannot find -lvtkIONetCDF /usr/bin/ld: cannot find -lvtkNetCDF /usr/bin/ld: cannot find -lvtkNetCDF_cxx /usr/bin/ld: cannot find -lvtkFiltersCosmo /usr/bin/ld: cannot find -lvtkParallelCore /usr/bin/ld: cannot find -lvtkIOLegacy /usr/bin/ld: cannot find -lvtkIOXML /usr/bin/ld: cannot find -lvtkIOGeometry /usr/bin/ld: cannot find -lvtkImagingMath /usr/bin/ld: cannot find -lvtkRenderingGL2PS /usr/bin/ld: cannot find -lvtkDomainsChemistry /usr/bin/ld: cannot find -lvtkChartsCore /usr/bin/ld: cannot find -lvtkCommonColor /usr/bin/ld: cannot find -lvtkRenderingFreeTypeOpenGL /usr/bin/ld: cannot find -lvtkIOPLY /usr/bin/ld: cannot find -lvtkFiltersTexture /usr/bin/ld: cannot find -lvtkImagingMorphological /usr/bin/ld: cannot find -lvtkParallelMPI /usr/bin/ld: cannot find -lvtkTestingGenericBridge /usr/bin/ld: cannot find -lvtkRenderingVolumeOpenGL /usr/bin/ld: cannot find -lvtkFiltersParallelFlowPaths /usr/bin/ld: cannot find -lvtkFiltersAMR /usr/bin/ld: cannot find -lvtkFiltersFlowPaths /usr/bin/ld: cannot find -lvtkxdmf2 /usr/bin/ld: cannot find -lvtkIOEnSight /usr/bin/ld: cannot find -lvtkRenderingHybridOpenGL /usr/bin/ld: cannot find -lvtkLocalExample /usr/bin ... (more)