-
Notifications
You must be signed in to change notification settings - Fork 132
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
base: master
Are you sure you want to change the base?
Conversation
@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? |
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). |
+1 adopting Gazebo's conventions |
In addition to Gazebo, I hope to consider sensors used in OpenHRP3 and OpenRAVE. Gazebo(sdf) http://gazebosim.org/sdf/dev.html OpenHRP3(vrml) http://www.openrtp.jp/openhrp3/en/create_model.html OpenRAVE(collada) http://openrave.org/docs/latest_stable/collada_robot_extensions/ |
It's too late. |
Better link for latest SDFormat sensor model: http://sdformat.org/spec?ver=1.5&elem=sensor |
Hi, |
@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. |
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? |
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 .
I would like to use sensor descriptions on urdf_model.
So, I added SensorBase class as base class for sensors including VisionSensor.