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

Implement the robot_status interface function properly #140

Open
aeshub opened this issue Feb 8, 2023 · 1 comment
Open

Implement the robot_status interface function properly #140

aeshub opened this issue Feb 8, 2023 · 1 comment
Labels
improvement Improvement to existing functionality stale

Comments

@aeshub
Copy link
Contributor

aeshub commented Feb 8, 2023

Describe the improvement you would like to see
The robot_status interface function should not always return Available but should check the simulator to see if it is running, if the robot is busy in a mission or if the robot is idle and then report RobotStatus.Offline, RobotStatus.Busy or RobotStatus.Available accordingly.

How will this change existing functionality?
More correct information will be propagated when using the Turtlebot simulator all the way to Flotilla.

How will this improvement affect the current Threat Model?
Should not be affected.

@aeshub aeshub added the improvement Improvement to existing functionality label Feb 8, 2023
@aeshub aeshub changed the title Implement the robot_status interface function properly Implement the robot_status interface function properly Feb 8, 2023
@aeshub
Copy link
Contributor Author

aeshub commented Jun 20, 2023

This issue has automatically been marked as stale as there has been no activity for 60 days. Remove stale label or comment or this will be closed in 7 days.

@aeshub aeshub added the stale label Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement to existing functionality stale
Projects
None yet
Development

No branches or pull requests

1 participant