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

Segmentation action modified with a new array of surfaces #2

Merged
merged 5 commits into from Nov 3, 2017

Conversation

pengy25
Copy link
Collaborator

@pengy25 pengy25 commented Nov 1, 2017

See the contribution checklist.

One-line description of pull request:
A surface array added for surface segmentation

Detailed description of pull request:
SegmentSurfaces.action now has an additional array for collision surfaces as result of an action. This allows surface_segmentation_action to add detected collision surfaces in the result. Although current development of surface_segmentation_action only adds one collision surface, this pull request enables potential of surface_segmentation_action to add multiple collision surfaces.

How was this PR tested?
Tested by demo video: https://drive.google.com/open?id=0B5qgkEBlR0dXVkNUZWhSVExyUm8

@@ -1,5 +1,6 @@
bool save_cloud # True if the point cloud should be saved
---
rapid_pbd_msgs/Landmark[] landmarks
moveit_msgs/CollisionObject[] surfaces
Copy link
Owner

Choose a reason for hiding this comment

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

This should be a new message type, rapid_pbd_msgs/Surface surface:

geometry_msgs/PoseStamped pose_stamped # The pose of center of the table. Should be specified in the base frame.
geometry_msgs/Vector3 dimensions # Dimensions of the table, in meters

The fact that we are using MoveIt is an internal detail and should not be part of this API.

There should also only be one surface. If we detect multiple surfaces in the future, we can change this.

msg/Surface.msg Outdated
@@ -0,0 +1,3 @@
# Information of a collision surface for collision object construction
Copy link
Owner

Choose a reason for hiding this comment

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

Again, the purpose of the Surface is just to represent a surface. It may be used as a collision object, but it could also be used for visualization. So this comment should just say:

# Represents a surface found when detecting surface objects.

@jstnhuang jstnhuang merged commit 37408bd into indigo-devel Nov 3, 2017
@jstnhuang jstnhuang deleted the surfaceCollisionObjectAction branch November 3, 2017 01:44
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.

None yet

2 participants