psammut's profile - activity

I have a similar problem and opted to import these from a settings json defined by a thrift file. I can iterate over the

I have a similar problem and opted to import these from a settings json defined by a thrift file. I can iterate over the

I just lost 2 hours of my life because of this. How did you learn about this?

How did you know to add OpenCV? Are there docs on this?

Did the proposed answer by Dirk Thomas work for you?

Hi! Where you able to do this?

Hello, I have a robot that is having issues getting stuck. In a lot of situations, a simple reverse operation would un stick it. Rotate recovery doesn't work well because my robot's turning center is offset from its body. Before I get to writing one from scratch, is there any reversing type recovery behavior i could get move_base to use?

Thanks!

Hello, first of all thanks to Mathieu Labbe for all his hard work on rtabmap and for bringing it to ROS!

I would like to use two stereo cameras to aid in SLAM and also path planning. I have been experimenting with one camera and I found that if I point it forward, SLAM works well but the path planner doesn't because it is guessing about obstacles at the feet of the robot. If I point the camera down path planning works well but mapping suffers.

Id like to use two stereo cameras increase path planner obstacle detection accuracy and maintain good map building abilities.

Question is, what is the best way of doing this? rtabmap seems to be written to subscribe to only one stereo camera. Should I combine the point clouds generated by stereo_image_proc?

Also I'm unsure as to how I should use my wheel odometry in this setup. It looks like rtab can only use one odometry source. Should I just do visual odometry if it works well enough and pipe that into rtab? I'm experimenting right now with wheel odometry data and one stereo camera with rtab and I'm slightly unsure on how I should connect these systems together.

Thanks!

My question is: When using the robot_localization package, should the IMU chirality obey the standard right hand rule, or left hand rule? I think there is a discrepancy in the docs.

From the docs of the robot_localization package a section about IMU data states the following:

• Adherence to specifications: As with odometry, be sure your data adheres to REP-103 and the sensor_msgs/Imu specification.

• Acceleration: Be careful with acceleration data. The state estimation nodes in robot_localization assume that an IMU that is placed in its neutral right-side-up position on a flat surface will:

  • Measure +9.81 meters per second squared for the Z axis.
  • If the sensor is rolled +90 degrees (left side up), the acceleration should be +9.81 meters per second squared for the Y axis.
  • If the sensor is pitched +90 degrees (front side down), it should read -9.81 meters per second squared for the X axis.

Problem: this documentation says two things. It says the data should adhere to REP-103, which says "All systems are right handed. This means they comply with the right hand rule.". Then it describes an example that could only work on a left hand system. Am I missing something?

This is a camera problem and not a ros driver issue. You can confirm this by using a dedicated viewer such as guvcview o

Hi! first step when messing is to make sure that the issue lays with ROS/libuvc driver and not the camera. To do this,

I'm also running into this issue. All my source that uses opencv3 is no longer compiling!

@Felix Widmaier did you ever get this work for you? Mine still leaves fantom obstacles. :(

oh man this is this awesome. Thanks David!!!! Lu!

Yup. I also have the same exact question. This parameter is broken. Setting it to 0 does not only keep keep the most rec

robot_localization IMU coordinate frame. My question is: When using the robot_localization package, should the IMU chira

robot_localization IMU coordinate frame. My question is: Should the IMU chirality obey the standard right hand rule, or

I found it helpful 5 years later :)

Are you going to be using a virtual machine or real install? A real install is recommended because Rviz and Gazebo will

how do you calculate the projection_matrix from rectification matrix? I don't know :( You should really look into doing

camera_name is simply the frame_id of your camera if you defined it in the URDF file of your robot. This allows you to a

A matlab monocular camera calibration is stored in the format of a cameraParameters object. In ROS, the calibration pa

I highly recommend these tutorials on youtube: https://www.youtube.com/watch?v=8ckSl4MbZLg&list=PLTEmcYHVE7dPWixFnzk

What you can do is download the source of the packages in question, put them in your catkin workspace and compile them,

A matlab monocular camera calibration is stored in the format of a cameraParameters object. In ROS, the calibration pa

Can you post a sample .mat cal file? A .yaml camera calibration file is nothing special, and simply contains the same in

Can you post a sample .mat cal file? A .yaml camera calibration file is nothing special, and simply contains the same in

Can you post a sample .mat file? A .yaml camera calibration file is nothing special, and simply contains the same inform