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

Recovery handling #4

Open
A-make opened this issue Oct 16, 2019 · 1 comment
Open

Recovery handling #4

A-make opened this issue Oct 16, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@A-make
Copy link
Contributor

A-make commented Oct 16, 2019

The Cyborg will get stuck or lose localization at some point, and without human intervention it will not move when this happens. As discussed in Section 3.5 in Aregs report, some form of recovery behavior or notification to an administrator, would be preferable to have.

@A-make A-make added the enhancement New feature or request label Oct 16, 2019
@goncz
Copy link
Contributor

goncz commented Nov 13, 2019

This will be solved with the new navigation stack. Comprehensive testing required.

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

No branches or pull requests

2 participants