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
backendBackend related functionalitybreaking-changeA breaking change which introduces changes to the public APIsepicfeatureNew feature or requestfrontendFrontend related functionalityuxIssue needs input from UX designer
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.
backendBackend related functionalitybreaking-changeA breaking change which introduces changes to the public APIsepicfeatureNew feature or requestfrontendFrontend related functionalityuxIssue needs input from UX designer
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.
The text was updated successfully, but these errors were encountered: