-
Notifications
You must be signed in to change notification settings - Fork 432
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
--Articulated Object Attributes/Managers support #2178
Conversation
0785836
to
501f3d7
Compare
As with all JSON configs, the asset filepath is expected to be relative to the config's location on disk.
501f3d7
to
af22cfd
Compare
--This specifies how to render the AO - using its skin, primitives, both or neither.
--We want to fail on load of attributes configs if certain criteria are not met.
Retain boolean "fixed base" query for now, but this will be removed in favor of only having the enum-backed value.
Remove confusion with functions that add actual instances of objects.
There's a couple linking errors in a few of the tests that I have to chase down, but functionally this is complete. Yay! |
bcf811b
to
b5de5dc
Compare
Also python bindings
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.
Thanks! Looks good overall. Noted some minor typos and small refactor requests.
925bb95
to
c4609d0
Compare
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.
LGTM, thanks!
Motivation and Context
This PR adds support for articulated object configurations as Attributes, and their management via an AttributeManager, in the same way that Object Attributes, Stage Attributes, etc, are managed.
We allowed for articulated object json files already, to describe habitat-specific fields as well as certain overrides, but they were not integrated into the Metadata system and so were of limited usefulness.
This is currently a WIP.This PR is now ready to go!The handling of configs, either loaded directly if specified with .json extension, or built on the fly if specified filename is the source URDF file, currently works, and these configs are being used explicitly during AO instantiation to reference the URDF file and build the articulated objects.
How Has This Been Tested
All existing c and python tests pass.
More tests will be added to test the AO Attributes and Managers' functionality directly.
Types of changes
Checklist