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

Error handling for when a robot does not reach it's safe zone #1596

Open
2 tasks
haakonsf opened this issue May 15, 2024 · 2 comments
Open
2 tasks

Error handling for when a robot does not reach it's safe zone #1596

haakonsf opened this issue May 15, 2024 · 2 comments
Labels
frontend Frontend related functionality improvement Improvement to existing functionality stale This issue or pull request already exists

Comments

@haakonsf
Copy link
Contributor

Describe the improvement you would like to see
Ref #1544 : It should be made more clear for the user when a robot fails to go to it's safe zone. Currently a banner is displayed stating that the mission has failed, but the status of the robot is "Safe Zone". This could potentially cause confusion. Nothing other than the banner displaying happens when the robot fails to go to a safe zone.

  • Consider adding another status to show it has not returned to safe zone
  • Consider adding error handling for situations where the robot fails to go to safe zone

How will this change existing functionality?
Improve user understanding and build on the go to safe zone feature.

How will this improvement affect the current Threat Model?

@haakonsf haakonsf added improvement Improvement to existing functionality frontend Frontend related functionality labels May 15, 2024
@tsundvoll
Copy link
Contributor

I would like this functionality to reside with ISAR.

Safe Zone ("In safe zone" or / "sideline") could be a separate state in ISAR; and it will only transition here if it has verified that it is within "Sideline" borders.

@aeshub
Copy link
Contributor

aeshub commented Jul 27, 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 Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend Frontend related functionality improvement Improvement to existing functionality stale This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants