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

Localization overhaul #950

Closed
4 tasks done
oysand opened this issue Aug 8, 2023 · 1 comment
Closed
4 tasks done

Localization overhaul #950

oysand opened this issue Aug 8, 2023 · 1 comment
Assignees
Labels
backend Backend related functionality breaking-change A breaking change which introduces changes to the public APIs epic feature New feature or request frontend Frontend related functionality ux Issue needs input from UX designer

Comments

@oysand
Copy link
Contributor

oysand commented Aug 8, 2023

Describe the new feature you would like to see
Localization should be an "invisible" feature. When scheduling a set of missions Flotilla should have a prompt that asks the user to confirm which deck the robot have been placed on. Each deck shall have a single localization spot where the robot have been placed. The missions to be scheduled can only occur on a single deck at the time.

When starting a new batch of missions Flotilla will as ISAR to localize at the defined localization spot for the deck. Then when a mission in the batch finishes Flotilla shall check if there are more missions in the batch. Between missions in the batch there should not be any localization action. After the last mission of the batch Flotilla will schedule a mission to ISAR telling it to return to the defined localization spot for the deck.

If the missions are interupted/stopped then the mission queue should be cleared.

Describe the solution you'd like
The current localization feature should be simplified to the description above. Input from UX is needed to see how this should look in the frontend.

How will this feature affect the current Threat Model?
Leave blank for maintainers to fill out if you are uncertain about this.

@oysand
Copy link
Contributor Author

oysand commented Aug 23, 2023

#987

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality breaking-change A breaking change which introduces changes to the public APIs epic feature New feature or request frontend Frontend related functionality ux Issue needs input from UX designer
Projects
None yet
Development

No branches or pull requests

3 participants