-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Deprecation timeline for RigidBodyTree and attic #12158
Comments
This comment has been minimized.
This comment has been minimized.
Given the above PRs and a few more PRs currently in flight, as of this week all code inside Drake that uses the The only remaining question on timing for removal of |
We have surveyed most known users, and the following timeline seems suitable. Please let us know of any difficulties: Proposed dates (approximate):
|
FYI For the new APIs, see
MultibodyPlant<T>
documentation.If you have questions or need help converting to
MultibodyPlant
please use https://drake.mit.edu/getting_help.html. If there are missing features that could block your workflow, please let us know NOW by commenting on this issue.We are wondering if it's time to finally remove the
RigidBodyTree
,RigidBodyPlant
, and related attic code and examples from Drake master.We would like to understand the useful timeline for keeping them -- what issues with MultibodyPlant do we need to solve first, how long do users need to finish their transition to MultibodyPlant, and therefore what is a good target date for removing the code.
We are hoping for a removal date in early 2020.
I'd like to ask any users who would like to influence this timeline to speak up here, or on
#dynamics
slack.Known possible blockers:
Feature request buckets:
See also #9783 for past work on the attic.
The text was updated successfully, but these errors were encountered: