Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Go to home mission always last in mission queue #902

Closed
anetteu opened this issue Jul 20, 2023 · 4 comments
Closed

Go to home mission always last in mission queue #902

anetteu opened this issue Jul 20, 2023 · 4 comments
Labels
backend Backend related functionality feature New feature or request frontend Frontend related functionality

Comments

@anetteu
Copy link
Member

anetteu commented Jul 20, 2023

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.

@anetteu anetteu added feature New feature or request backend Backend related functionality frontend Frontend related functionality labels Jul 20, 2023
@andchiind
Copy link
Contributor

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.

@oysand
Copy link
Contributor

oysand commented Jul 31, 2023

Should have a larger discussion about return home functionality before jumping in to it

@anetteu
Copy link
Member Author

anetteu commented Aug 2, 2023

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?

@oysand
Copy link
Contributor

oysand commented Aug 8, 2023

To be handled in #950

@oysand oysand closed this as completed Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality feature New feature or request frontend Frontend related functionality
Projects
None yet
Development

No branches or pull requests

3 participants