-
Notifications
You must be signed in to change notification settings - Fork 104
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
[skinDynLib] Add linkName and frameName to dynContact and skinContact, and forceTorqueEstimateConfidence to skinContact #462
Closed
Closed
Changes from 7 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f59c0ca
Add serialization-deserialization tests to skinDynLib
traversaro 4c7e4c9
Enable compiling and running the tests in Travis
traversaro 9bb9ed1
[skinDynLib] Add linkName and frameName to dynContact and skinContact
traversaro 848c50f
[skinDynLib] Deprecate toVector/fromVector
traversaro 2f370f6
[skinDynLib] Add forceTorqueEstimateConfidence
traversaro 01d715f
[skinDynLib] Fix serialization of strings
traversaro fdeacb9
[skinDynLib] Fix serialization of dynContact/skinContact
traversaro 29681cc
[iCubSim] Add support for linkName and frameName in skin simulation
traversaro c4b1450
[skinManager] Add support for linkName and frameName in skinContact
traversaro 518075c
Update release notes
traversaro File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
iCub 1.10.0 (UNRELEASED) Release Notes | ||
======================== | ||
|
||
New Features | ||
------------ | ||
|
||
### Libraries | ||
|
||
#### `skinDynLib` | ||
Add `linkName` and `frameName` attributes to `iCub::skinDynLib::dynContact` and `iCub::skinDynLib::skinContact`, to simplify | ||
interfacing with software in which link and frames are identified by names, such as software that load the robot description | ||
from file formats like URDF and SDF. This attributes have been also added to the on-wire representation of this class, creating | ||
an incompatibility between versions of iCub before 1.8 and version after 1.10 , meaning that a module compiled with iCub 1.8 will | ||
not be able to communicate with a module compiled with iCub 1.10 . Recompiling all your software with iCub 1.10 (without any modification | ||
to the source code) should be sufficient to ensure that everything works fine. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Am I wrong or going to a newline in markdown has no effect? I think that writing paragraphs on a single line is the best choice, and new line behavior should be handled by the soft wrap configuration of the editor the user uses.
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.
There are several reasons why I prefer to break paragraph in raw Markdown, even if this has no effect on the rendered document: