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

nav_core2 #11

Closed
reinzor opened this issue Nov 21, 2017 · 5 comments
Closed

nav_core2 #11

reinzor opened this issue Nov 21, 2017 · 5 comments
Labels

Comments

@reinzor
Copy link
Contributor

reinzor commented Nov 21, 2017

Are you planning to be compatible with https://github.com/locusrobotics/robot_navigation/tree/master/nav_core2 ?

@corot corot added the question label Nov 22, 2017
@corot
Copy link
Collaborator

corot commented Nov 22, 2017

Not by now, but we support nav_core-based pluggins, so I suppose we can load too nav_core2 plugins using the https://github.com/locusrobotics/robot_navigation/tree/master/nav_core_adapter package.

@reinzor
Copy link
Contributor Author

reinzor commented Nov 27, 2017 via email

@reinzor
Copy link
Contributor Author

reinzor commented Nov 28, 2017

Thanks for your answer @corot. I have been looking at the abstraction you have created for the controller and the planner (https://github.com/magazino/move_base_flex/blob/master/move_base_flex_core/include/move_base_flex_core/abstract_local_planner.h https://github.com/magazino/move_base_flex/blob/master/move_base_flex_core/include/move_base_flex_core/abstract_global_planner.h). I also looked at the ones defined here in the nav_core2 interface (https://github.com/locusrobotics/robot_navigation/blob/master/nav_core2/include/nav_core2/global_planner.h https://github.com/locusrobotics/robot_navigation/blob/master/nav_core2/include/nav_core2/local_planner.h).

I think the interfaces you defined are nice, except for the interfaces in the local planner for computing the velocity and the isGoalReached method. Because the state used in this method is not an input argument but magically obtained via the TF listener or an odom subscriber. In the nav_core2 interface, this has been changed. What do you think about this?

@corot
Copy link
Collaborator

corot commented Nov 28, 2017

I agree; #17

@reinzor
Copy link
Contributor Author

reinzor commented Nov 28, 2017

Okay, I will close this issue

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

No branches or pull requests

2 participants