-
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 #1071
Conversation
🔔 Migrations changes detected 🔔 |
39c80d0
to
eacd5f0
Compare
177e68a
to
921d2ae
Compare
42a00c8
to
e1bbd87
Compare
235acd8
to
6ede7d6
Compare
🔔 Changes in database folder detected 🔔 |
6ede7d6
to
bff7038
Compare
bff7038
to
6b1ddca
Compare
6b1ddca
to
7ae264e
Compare
ad9ec9d
to
398c780
Compare
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.
Most of these comments are not hard requirements, but I'm just blocking the PR due to the granular access issues.
_scheduleLocalizationSemaphore.WaitOne(); | ||
|
||
string? localizationMissionRunId = null; | ||
try { localizationMissionRunId = await LocalizationService.EnsureRobotIsCorrectlyLocalized(missionRun.Robot, missionRun); } |
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.
I agree, since we don't make use of the exception that is returned anyways
7a99c91
to
355f6e3
Compare
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
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.
bfe08bd
to
7d4e999
Compare
/UpdateDatebase |
/UpdateDatabase |
⛔ Cannot update database until the Pull Request is approved! ⛔ |
Creating new PR to manage migrations |
No description provided.