-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add Haptic Glove Module #72
Conversation
kouroshD
commented
Oct 7, 2021
•
edited
Loading
edited
- I still have to add README file to the module
- I have to fix the configuration files
- I have to check the possible changes outside the scope of this PR on other modules and remove those changes if are unnecessary
- After the latest changes, I have to run the code with the robot.
10c2474
to
4bc993f
Compare
139ae79
to
37029ee
Compare
e077eea
to
d7d5f1b
Compare
The PR is ready to be reviewed, except the points mentioned in the first comment. |
cbc64d2
to
ba407e7
Compare
I have tested many times during these days the code, and I applied bug fixes as well as updates on the configuration file. All the features are implemented. The only remaining point is the ReadMe documentation, that I may do it later. In any case, the PR is ready to be reviewed. I have also updated the CI, so that has dependency into wearables as well. Now, in fact, it compiles haptic glove module in all OS. |
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.
Some preliminary feedback
app/robots/iCubGazeboV2_5/leftFingersHapticRetargetingParams.ini
Outdated
Show resolved
Hide resolved
Given the size of the PR, if @S-Dafarra is already reviewing it I would remove myself from the reviewers. If there is any specific point on which you need my input @kouroshD feel free to point it out, thanks! |
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 mostly skimmed through the code. Most of the comments are simply suggestions
With this fc89789, I have modified the |
another thing is that in the |
Co-authored-by: Stefano Dafarra <[email protected]>
…ific member method
9746ce3
to
fd5f5f9
Compare
@S-Dafarra let me know if the responses are OK, if it needs further declarations/modifications. |
I think it is OK to me! I would just suggest opening an issue to remove hardcoded numbers when setting a haptic feedback |
Before merging, I ran once the code in order to be sure it is running after changing the requested code changes, and I found a bug indeed related to those changes: leftHandREtargetingForPR-2022-01-17_15.24.06.mp4 |
I guess you can also remove that line. By default it should be |
It is not. Look at here: |
Ah nice catch. It seems that it enables it when writing to multiple joints. I guess this is to make sure that the commands sent to all the joints is coherent in time 🤔 . |
e995d14
to
ab05a12
Compare
ab05a12
to
e94eb10
Compare
Yes, writeStrict is necessary for all the commands that require multiple messages for different joints, otherwise tipically the last one would be the only one considered. |
So then, maybe it is worth leaving it with the default behavior 🤔 |
@traversaro What do you mean by |
Let's say that for some reason you are sending velocity reference joint-by-joint with: https://github.com/robotology/yarp/blob/165a46c6e034fc27b90cc0bd80b35419679b22c3/src/devices/RemoteControlBoard/RemoteControlBoard.cpp#L1914 . In that case, if you do not have writeStrict, only the last command will be considered. |
As I see in that snippet, it sends the joint |
@S-Dafarra @traversaro If you do not have other comments or suggestion, I will merge the PR. Thanks. I will keep the history of PR as it is. |
Sure on my side, see #72 (comment) ! |
GO also for me! |