fix: the stopping speed judgments of freespace_planner and mission_planner #7859
+5
−2
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.
… are consistent, taking into account the speed in xyz direction
Description
The stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction
Related links
#7834
How was this PR tested?
None
Notes for reviewers
This is an accidental bug. The conditions for judging the end of a task are looser than the conditions for judging the completion of a task are used by the mission_planner, which occasionally causes the freespace_planner to judge that the task is completed, but the mission_planner to judge that the task is not completed.
Interface changes
None.
Effects on system behavior
None.