Allow to insert models from rod objects
#47
Merged
Conversation
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
diegoferigo
force-pushed
the
feature/insert_rod_model
branch
from
05c2b58
to
8afdcf4
Compare
flferretti
approved these changes
Aug 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change enables to bypass entirely URDF / SDF descriptions (both files and strings).
It can be extremely useful in robot learning applications where the model has to be changed programmatically. Right now, even if the application has an in-memory rod model (that is easy to modify), it has to either serialize to string or write to file before passing it to jaxsim. Now, paying the price of extra time necessary for the parsing, the rod object can be edited in-memory and passed directly to jaxsim.
This is also useful, for example, to perform domain randomization in a highly parallel simulation.