Skip to content
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

Future of control directory #50

Open
mauricefallon opened this issue Feb 3, 2016 · 1 comment
Open

Future of control directory #50

mauricefallon opened this issue Feb 3, 2016 · 1 comment

Comments

@mauricefallon
Copy link
Contributor

@rdeits has been pulling the InstQP into drake and making it C++. Is there a future for the 'control' directory? A lot of its is stale matlab and quite a bit of it hasn't been touched since the Trials.

We had talked about this briefly at the DRC. @rdeits : Is it possible to simple ditch it going forward?

For example @MarcoCar has started (in his branch) a separate directory for motion planning (using Drake) which never had a specific home.

@rdeits
Copy link
Contributor

rdeits commented Feb 3, 2016

Yes, my goal is to get rid of the control folder and move all of the useful parts of it into drake. I'm currently stuck on RobotLocomotion/drake#1672 but I think most of the scary controller reorganization is done, and the rest is just cleaning up interfaces and putting it all together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants