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

Split up COMPAS FAB backends #361

Open
gonzalocasas opened this issue Jul 4, 2022 · 0 comments
Open

Split up COMPAS FAB backends #361

gonzalocasas opened this issue Jul 4, 2022 · 0 comments

Comments

@gonzalocasas
Copy link
Member

gonzalocasas commented Jul 4, 2022

To ease the create of new backends and simplify deployment of COMPAS FAB in general, the backends should be split into completely new packges: compas_fab_ros, compas_fab_pybullet and compas_fab_vrep (or compas_fab_coppeliasim if we update it to the latest version).

All pure-python implementations of backend features (i.e. if we add our own planner implementation at some point), should stay in this package. All implementations that require out-of-process tools to run should become its own package. The pybullet is on the verge of being ok to stay so it might be discussed.

Conda packages will also need to be split, and ideally also a combined compas_fab_backend_bundle could be created to install all backends at once.

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

1 participant