Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use SensorBase class as base class for sensors #28

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

YoheiKakiuchi
Copy link

I would like to use sensor descriptions on urdf_model.
So, I added SensorBase class as base class for sensors including VisionSensor.

@isucan
Copy link
Contributor

isucan commented Feb 16, 2014

@YoheiKakiuchi this is definitely interesting and I think a direction we need to pursue. However, the URDF is used by a number of people and we can't make any changes to the parser before they are made in the spec (http://wiki.ros.org/urdf/XML). I propose starting a discussion from http://wiki.ros.org/urdf/XML/sensor/; Perhaps we can create a new page with a proposal (link to ../sensor/ and and link from ../sensor/) and put up a description of the updated tag. Once that is there, we should send an e-mail to ros-users and have people comment on the proposal. Once we agree to the format, we can proceed to making changes in the parser. Does this sound reasonable?
Attn: @hsu @wjwwood @davetcoleman @jbohren @k-okada @sachinchitta @nkoenig @ipa-fxm @ipa-mdl

@sachinchitta
Copy link

I support the idea of having general sensors included in the URDF. I think it would be good if we looked at what Gazebo is doing and maybe just adopt that convention for most of the common sensor types (Gazebo currently parses sensors inside a special sensor tag).

@davetcoleman
Copy link
Contributor

+1 adopting Gazebo's conventions

@YoheiKakiuchi
Copy link
Author

In addition to Gazebo, I hope to consider sensors used in OpenHRP3 and OpenRAVE.
They are similar, but there are some difference.
Sensors used in each program are listed.

Gazebo(sdf) http://gazebosim.org/sdf/dev.html
camera, depth, multicamera, contact, gps, imu, ir and ray

OpenHRP3(vrml) http://www.openrtp.jp/openhrp3/en/create_model.html
AccelerationSensor, GyroSensor, VisonSensor, ForceSensor, RangeSensor

OpenRAVE(collada) http://openrave.org/docs/latest_stable/collada_robot_extensions/
base_pinhole_camera, base_stereo_camera, base_laser2d, base_laser3d,
base_flash_laser, base_encoder, base_force6d, base_imu, base_odometry

@YoheiKakiuchi
Copy link
Author

It's too late.
I added proposal page of sensor, please check them.
http://wiki.ros.org/urdf/XML/sensor
http://wiki.ros.org/urdf/XML/sensor/proposals

@davetcoleman
Copy link
Contributor

Better link for latest SDFormat sensor model: http://sdformat.org/spec?ver=1.5&elem=sensor

@EnricoMingo
Copy link

Hi,
this is a very interesting topic to have sensors inside the urdf. From my personal experience an important aspect is the possibility to have a reference frame associated to the lecture of the sensor. For instance: if I have a force/torque sensor attached to my robot I will define it in a certain link and in a certain pose w.r.t the joint axis (similar as the origin tag in the urdf for the com parameter). I expect that the lecture from the sensor come w.r.t this pose therefore I would like to have a reference frame in that pose so I can transform lecture in other reference frames. Same as for IMU. What do you think?

@sachinchitta
Copy link

@YoheiKakiuchi - could you fill in the rest of the sensor information as well based on what the SDFormat has - if it works for Gazebo (and has been out for a while), there's no reason it can't work for ROS too. It would also be great to have a library of named sensors (with model numbers) so we can just reference them easily in our robot descriptions.

@traversaro
Copy link
Contributor

The URDF is currently used in several software projects, some of which are outside the traditional ROS ecosystem, such as Drake, Phobos, SimulationConstructionSet, Morse, V-REP and probably many others. Many of this projects are already developing their own (mutually-incompatible) extensions of the URDF for supporting sensors.

Considering this it could make sense to give more visibility to this discussion?
For example we could open a proper issue to discuss the proposal, and send an email to ROS-Users to alert people that could be interested in this topic but are not following the urdfdom repo.

This was referenced Mar 13, 2016
traversaro added a commit to robotology/simmechanics-to-urdf that referenced this pull request Jun 29, 2016
In addition to the already-supported Gazebo format.
As the discussion on how to support format in URDF is not progressing
(see ros/urdfdom#28) for now support the dialect
used in iDynTree, as documented in https://github.com/robotology/idyntree/blob/master/doc/model_loading.md .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants