You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the new feature you would like to see
A go to home/safe position mission that is always scheduled as the last mission of the mission queue if the mission queue is not empty, or there is an ongoing mission. The mission should always be the last one in the queue, even if new missions are scheduled. The desired behavior of the robot when an ongoing mission is completed will then be: if mission queue not empty -> run next mission. else -> go to home/safe position.
Describe the solution you'd like
If you have an idea of how to implement the feature please describe it here.
How will this feature affect the current Threat Model?
Leave blank for maintainers to fill out if you are uncertain about this.
The text was updated successfully, but these errors were encountered:
It could be nice to make it easier to schedule a go to safe position mission, but I am not sure if we always want this to be queued up by default. For instance if a mission fails and we quickly want to rerun it.
Related to #851#921 and to some extent #917. If a discussion is needed here, it should start with a definition of the intended end user. Are we devolving a product to be used by dev team members, or by field operators?
Describe the new feature you would like to see
A go to home/safe position mission that is always scheduled as the last mission of the mission queue if the mission queue is not empty, or there is an ongoing mission. The mission should always be the last one in the queue, even if new missions are scheduled. The desired behavior of the robot when an ongoing mission is completed will then be: if mission queue not empty -> run next mission. else -> go to home/safe position.
Describe the solution you'd like
If you have an idea of how to implement the feature please describe it here.
How will this feature affect the current Threat Model?
Leave blank for maintainers to fill out if you are uncertain about this.
The text was updated successfully, but these errors were encountered: