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

Show in the frontend whether the robot is probably not localised #1707

Open
andchiind opened this issue Aug 6, 2024 · 3 comments
Open

Show in the frontend whether the robot is probably not localised #1707

andchiind opened this issue Aug 6, 2024 · 3 comments
Assignees
Labels
backend Backend related functionality feature New feature or request frontend Frontend related functionality stale This issue or pull request already exists ux Issue needs input from UX designer

Comments

@andchiind
Copy link
Contributor

Describe the new feature you would like to see
If the robot is not running a mission and it is available in ISAR, the status of the robot should indicate whether we believe it returned to docking position. When we hover over this it would also be nice to provide info to the operator that they need to teleoperate it back to its docking location.

Describe the solution you'd like
I suggest we make a new robotFlotilla status which is diplayed instead of robotStatus.Available if it is set to something other that robotFlotillaStatus.Normal. Then the operator knows that no mission is running and that a mission can theoretically be run, but the robot is potentially not at home since the last return to home mission did not succeed. This should appear as a mild warning, not as an aggressive icon in my opinion.

How will this feature affect the current Threat Model?
N/A

@andchiind andchiind added feature New feature or request backend Backend related functionality frontend Frontend related functionality ux Issue needs input from UX designer labels Aug 6, 2024
@mrica-equinor mrica-equinor self-assigned this Aug 7, 2024
@mrica-equinor
Copy link
Contributor

I don't agree with creating a new robot status, I think it should be based on wheather or not the robot current area is null

@andchiind
Copy link
Contributor Author

andchiind commented Aug 29, 2024

I don't agree with creating a new robot status, I think it should be based on wheather or not the robot current area is null

This is not enough information to know whether it returned to its docking station though. And I am not suggesting a new robot status, but a new Flotilla Robot Status, like we currently have Safezone and Recharging.

@aeshub
Copy link
Contributor

aeshub commented Nov 1, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Nov 1, 2024
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 stale This issue or pull request already exists ux Issue needs input from UX designer
Projects
None yet
Development

No branches or pull requests

3 participants