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
Describe the new feature you would like to see
Instead of using Decks to understand where a robot can traverse in a mission, we should instead define a list of Areas, as this takes into account moving between floors in a mission.
Describe the solution you'd like
The easiest implementation would be a list of areas, but a more advanced implementation might store a graph of areas. The important part is that a robot is able to traverse the entire area, and that there is at least one Docking station/defaultLocalisationPose within the InspectionArea. We do not have to call it "InspectionArea" either, but it should be distinct from Area and Deck. We should then link mission definitions to InspectionAreas, as opposed to decks or areas. Deck will still be useful for visualisation in the frontend, but can otherwise be ignored on the backend.
How will this feature affect the current Threat Model?
N/A
The text was updated successfully, but these errors were encountered:
Describe the new feature you would like to see
Instead of using Decks to understand where a robot can traverse in a mission, we should instead define a list of Areas, as this takes into account moving between floors in a mission.
Describe the solution you'd like
The easiest implementation would be a list of areas, but a more advanced implementation might store a graph of areas. The important part is that a robot is able to traverse the entire area, and that there is at least one Docking station/defaultLocalisationPose within the InspectionArea. We do not have to call it "InspectionArea" either, but it should be distinct from Area and Deck. We should then link mission definitions to InspectionAreas, as opposed to decks or areas. Deck will still be useful for visualisation in the frontend, but can otherwise be ignored on the backend.
How will this feature affect the current Threat Model?
N/A
The text was updated successfully, but these errors were encountered: