Repository navigation
Let a run say how long the bridge waits for a task - #2
Merged
Merged
Conversation
180 seconds is the right wait for a fleet that answers. For watching what one that stops answering does to a mission it is three minutes of nothing, and the wait has to be longer than the task takes uncut or what the run measures is the clock rather than the cut.
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.
180 seconds is the right wait for a fleet that answers. For watching what one that stops answering does to a mission it is three minutes of nothing, so
task_timeout:is now a launch argument.It exists because of an experiment that cuts the fleet adapter mid-mission and measures what the epistemic half does with what it already knew. Two runs over the office fleet, with the wait set to 60 s:
unreported, and the bridge gave up after 60 s. The action failed withRMF task timed out, the mission failed, andmission_checkreported the state as it stood: nothing known, nobody spoken toThe wait has to exceed what the task takes uncut — about 38 s to the office in this building — or what the run measures is the bridge's clock rather than the cut. That is the whole reason this is an argument rather than a constant.
The experiment itself lives with the thesis rather than here, since it produces measurements rather than tests.