Fix false trajectory success when blocked by obstacle #579
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h goal due to obstacle, using new flags and logic in spot_wrapper
Pull Request Test Coverage Report for Build 13296454515Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Overview
Just changed some logic inside of
handle_trajectory()member function to properly handle the new flags/logic created in the correspondingspot_wrapperbranch. Going to keep this as a draft until the corresponding branch inspot_wrapperis merged to main.Testing Done
Tested on Rex in spot lab. Confirmed that it will report "Trajectory complete: failed to reach goal" if it is unable to reach the goal. Previously, it would instead say "Reached goal" and success. Trajectory duration time out fail also tested and still sends proper feedback and result.