--[BE/Bugfix]Modify creation of Articulated Object from URDF file name. #2190
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.
All AO creation is driven by ArticulatedObjectAttributes now, with the caveat that to be used, any ArticulatedObjectAttributes must reference an existing and legitimate URDF file by relative path name from which to actually build the AO. ArticulatedObjectAttributes can be created using the name of their corresponding URDF file, in which case they will reference -that- URDF, and there is no need to complain if there is no existing ArticulatedObjectAttributes matching that name, since a legal one will be created . This PR removes the erroneous and potentially misleading complaint, and proceeds silently to make a new ArticulatedObjectAttributes referencing the passed URDF file if one does not already exist.
This was peeled off this PR, to minimize topical divergence.
Motivation and Context
How Has This Been Tested
All C++ and python tests pass (it's just a message change)
Types of changes
Checklist