Add a --start-at-departure option for dispatch_go_to_place#331
Merged
Conversation
Signed-off-by: Michael X. Grey <greyxmike@gmail.com>
2 tasks
arjo129
approved these changes
Oct 7, 2025
This file contains hidden or 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
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.
This PR is motivated by #467 which introduces the
start_at_departureoption forgo_to_placeevents.In this PR we add a
--start-at-departureflag fordispatch_go_to_placeso we can test the behavior of the new flag.To try it out, launch the hotel world:
Then in another terminal dispatch a
go_to_placetask fortinyBot_1, telling it to start at the 90s mark:The robot should start moving to the goal right away because the default behavior is to arrive at the goal by the start time.
Now if you restart the simulation and try again with the new flag, the robot should wait at its charger until the simulation reaches its 90s mark: