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

[hrpsys_ros_bridge] chage RTC name of RangeROSBridge and PointCloudROSBridge #1059

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

YoheiKakiuchi
Copy link
Member

Currently name of RangeROSBridge component is RangeROSBridge0.rtc.
By this PR, the name of component is the same name as ROS nodename.

@YoheiKakiuchi YoheiKakiuchi force-pushed the fix_rtc_name2 branch 2 times, most recently from 832d0e6 to 8ca178f Compare January 30, 2019 09:34
Copy link
Member

@mmurooka mmurooka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By this PR, the name of component is the same name as ROS nodename.

I haven't use this component, and I'm not familiar with it.
Could you explain why it is necessary, please?

Copy link
Member

@k-okada k-okada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@YoheiKakiuchi
Copy link
Member Author

These components work for converting point cloud/lidar message from OpenRTM to ROS.
For the current implementation, RTC name of these components is PointCluoudRosBridge0, PointCluoudRosBridge1 ..., like that.
It is difficult to use if there are several components.

By this PR, RTC name is set as the same of ROS nodename.
So, we can change RTC name which is understandable, such as HEAD_DEPTH, FRONT_LIDER etc.
ImageSensorRosBridge does the same behavior as this PR.

Copy link
Member

@mmurooka mmurooka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for explanation. In which robot or environment, does this rtc used? In choreonoid simulation?

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.

3 participants