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

Feature add outcome to feedback #89

Merged

Conversation

howardcochran
Copy link
Contributor

Implements #77 "Improvements to ExePathFeedback
(and MoveBaseFeedback)"

@spuetz
Copy link
Member

spuetz commented Oct 2, 2018

@howardcochran Would be cool if you do the changes I've suggested. After that we could merge that. :)

Howard Cochran added 3 commits October 3, 2018 22:21
These fields will allow external entity to understand why a MoveBase or
ExePath action is currently failing before it actually gives up.
This can enable an external monitor to understand why the controller is
failing before the MoveBase or ExePath action gives up on the goal.

This makes it possible for external logic to decide when to trigger a recovery
behavior, for example.
@howardcochran howardcochran force-pushed the feature-add-outcome-to-feedback branch from 14e11b9 to 84e79d7 Compare October 4, 2018 02:24
@howardcochran
Copy link
Contributor Author

Thanks for the feedback, @spuetz. I have rewritten the commits with the requested changes and rebased the branch on 0.2.1.

@spuetz spuetz merged commit 37670d0 into naturerobots:master Oct 8, 2018
@howardcochran howardcochran deleted the feature-add-outcome-to-feedback branch October 12, 2018 18:05
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

Successfully merging this pull request may close these issues.

2 participants