-
Notifications
You must be signed in to change notification settings - Fork 37
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 localization as part of a mission #1277
Conversation
The localization procedure is now implemented and will run as part of regular mission scheduling. If the queue is empty a localization mission will be started for the current deck. This assumes that the operator has confirmed that the robot is on the deck of the mission that has been scheduled. If there is an existing mission the system will check if a new mission is in the same deck as that mission and if so schedule it. If not it will be rejected. If the last mission finishes a return to home mission will be scheduled which puts the robot back at the default localization pose. If a mission is scheduled in between the return to home mission another localization will not be required.
🔔 Changes in database folder detected 🔔 |
🔔 Migrations changes detected 🔔 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/UpdateDatabase |
👀 Running migration command... 👀 |
❌ Migration failed, please see action log below for details ❌ |
/UpdateDatabase |
👀 Running migration command... 👀 |
✨ Successfully ran migration command! ✨ |
No description provided.