-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature/implement grasp detector in grab #1239
base: master
Are you sure you want to change the base?
Changes from 17 commits
6642e75
802f766
0d35c55
2be6ad1
6d53e0f
1461fa4
f79701c
78798df
97150dd
e86de40
c466380
66232e5
8c17a90
b277700
7d91602
a763de0
b56e24f
5bacddf
f31614e
dca7493
b893518
7631ff9
c6d2d77
a6b42fe
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,7 +14,7 @@ class ActiveGraspDetector(smach.State): | |
REQUIRED_ARM_PROPERTIES = {"required_gripper_types": [GripperTypes.GRASPING], } | ||
|
||
def __init__(self, robot: Robot, arm_designator: ArmDesignator, threshold_difference: float = 0.075, | ||
minimum_position: float = -0.82, max_torque: float = 0.15) -> None: | ||
minimum_position: float = -0.75, max_torque: float = 0.15) -> None: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These are still very much magic numbers. They have the downside that they need to be tuned constantly. But I think that may be for another time There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Make this an issue. If we need keep changing this, this is something we need to work on with high priority. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I created an issue to look into the grasp position detector robot part #1248 . It does not have high priority though. So I don't think we need to add a deadline |
||
""" | ||
State for detecting whether the robot is holding something using the gripper position. | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does a
gripper_position_detector
do? We already know where the gripper is with the joint_states/TF.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It reads the joint state of the gripper
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So how open the fingers are?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. And upon further inspection we can use the get_joint_states function of the robot object for this but this allows us to already specify which joint corresponds to the fingers. That is something that can potentially be improved. But for now we want to see if this gives us the desired behaviour. Lets not do premature optimization.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a different can of worms and not for this project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
handover_detector
can be ignored in this project, butgripper_position_detector
should be modelled correctly. It doesn't mean it should be done correctly right now in this PR. But it should be done correctly soon.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#stopdeverloederingvanonzecode
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should create an issue about this. With a deadline this should be fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created an issue to look into the grasp position detector robot part #1248 . It does not have high priority though. So I don't think we need to add a deadline