tanasis's profile - activity

haha tpt! What you are trying to do should work. Just pasting it again for you to compare: <launch> <node pk

as far as I know, there is not. You need to specify .bag files to the rosbag play command.

It has been a while... I tried to find it but no luck, sorry. Basically if I remember the idea is to put the rosbag play

Hello,

I am a bit confused about the static_transform_publisher and the robot_state_publisher (or at least I think I am). So we are setting up a robot with sensor at all, and before we used the urdf approach we were using the static_transform_publisher to get the TF between sensors.

Now we want to use the urdf approach, i.e. robot_state_publisher. This is also publishing TF. So this should be now our source for tf, right? No need for the static_transform_publisher? (I think it will even interfere)

Thanks!

anything changed here since 2016?

Hello, any updates/solutions on this? Thx!

getOptimalNewCameraMatrix() alpha value and camera matrix While reading image_pipeline/CameraInfo documentation, in the

Thanks Pete! I will probably go down this road.

rviz_plugin_covariance Array of messages? Hello, I need to plot the 2D covariances of detected-tracked objects in rviz.

rviz_plugin_covariance Array of messages? Hello, I need to plot the 2D covariances of detected-tracked objects from . I

Hello, I am trying to develop a driver (node) for a commercial GNSS/INS unit. For that I think it is important NOT to use custom message sets, but rather standardized ones.

I have found the following:

• sensor_msgs/NavSatFix.msg for position (and GPS status)
• nav_msgs/Odometry.msg which gives position (again) and twist (velocities)
• sensor_msgs/Imu.msg IMU data
• GPSFix.msg and GPSStatus.msg from gps_common, which has a lot of types

What would be the best design approach?

Can any one with experience or not point me to the right direction? I think this would be important for people doing similar work as mine! Thanks!

EDIT 1:

After some digging, here also some extra pointers:

• Check REP 103 and REP 105
• Check ROS Robot Localization package.
• I wouldn't recommend using gps_common.

Hello,

We have a node that publishes a set of markers. Those markers are part of sensor detections. So they can appear or disappear while the node is running, which is normal.

Now after doing a recording, we would like to pause the bag. When rosbag is on pause, all markers disappear. Programmatically all markers have a lifetime, such that they can be automatically removed. Is this the reason why markers also removed while on pause?

If yes, how is the right approach to solve this issue? Do I need to remove markers manually and not rely on lifetime?

Thanks!

Hello,

looking at the sensor_msgs/CameraInfo Message and/or at the camera_calibration_parsers it seems that ROS supports only the Pinhole model for cameras (out of the box).

Is there some known way we could use the Scaramuzza model model for omnidirectional cameras?

Currently working under Indigo.

Thanks!

Hello! Are there any alternatives or similiar services as the ROS Bag Database?

Thanks!

Edit based on community answers:

• Bag Database
• Marv Robotics, by Ternaris (also presented at ROSCon16 (video))
• BotBags: Announcing BotBags, the cloud rosbag storage service

I got the same error. For me the fix was to end the topic name with "/compressed", i.e /camera/image_raw/compressed. I h

I got the same error. For me the fix was to end the topic name with "/compressed", i.e /camera/image_raw/compressed. I h

I got the same error. For me the fix was to end the topic name with "/compressed", i.e /camera/image_raw/compressed.

How was this fixed? Thx!

@gvdhoorn Have you used nodelet_rosbag? Any catch? Is it reliable? Can it really substitute rosbag? I cannot find any in

Is there a build-in tf2 functionality where we can generate a rotation matrix given an axis (tf2::Vector3) and an angle (double). E.g. Suppose you have:

tf2::Vector3 vec(2,3,4); // by axis I mean - any - axis, not just x,y,z
double angle_rads=1.57;
tf2::Matrix3x3 rotation_matrix(vec,rads); // <-- is there an easy way like this?

Thanks!