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

Remove defaultLocalisationPose from the database and stop sending startPose #1876

Closed
andchiind opened this issue Dec 12, 2024 · 1 comment · Fixed by #2012
Closed

Remove defaultLocalisationPose from the database and stop sending startPose #1876

andchiind opened this issue Dec 12, 2024 · 1 comment · Fixed by #2012
Assignees
Labels
backend Backend related functionality breaking-change A breaking change which introduces changes to the public APIs database-change Will require migration improvement Improvement to existing functionality

Comments

@andchiind
Copy link
Contributor

Describe the improvement you would like to see
Once ISAR is able to handle navigating to its own docking stations, we no longer need to store these locations in Flotilla. It is possible we may want to still display these poses, but then they should be set based on the values sent from MQTT. In either case, we no longer need to send startPoses to the robot, and we also do not need to send "dock" and "undock" flags as ISAR can understand whether or not they are docked.

How will this change existing functionality?
It will further move dock/return home logic to ISAR from Flotilla.

How will this improvement affect the current Threat Model?
N/A

@andchiind andchiind added backend Backend related functionality breaking-change A breaking change which introduces changes to the public APIs database-change Will require migration improvement Improvement to existing functionality labels Dec 12, 2024
@Eddasol
Copy link
Contributor

Eddasol commented Feb 6, 2025

Step one is solved here: #2011

@Eddasol Eddasol self-assigned this Feb 6, 2025
@Eddasol Eddasol linked a pull request Feb 6, 2025 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality breaking-change A breaking change which introduces changes to the public APIs database-change Will require migration improvement Improvement to existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants