-
Notifications
You must be signed in to change notification settings - Fork 21
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
Review for alternative to #169 #189
Closed
ted-miller
wants to merge
6
commits into
Yaskawa-Global:main
from
gavanderhoorn:warn_about_missing_calib
Closed
Review for alternative to #169 #189
ted-miller
wants to merge
6
commits into
Yaskawa-Global:main
from
gavanderhoorn:warn_about_missing_calib
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow user to disable raising an alarm in case a multi-group system has not been calibrated, but TF broadcast is still enabled (in which case group origins will be wrong).
We'll use it to not have to count the nr of Robot groups later (they're not expected to change after initialisation).
Note: as mentioned in the comments, it's perfectly OK for multi-group systems to not have been calibrated. Whether or not calibration succeeded to load is therefore not taken into account when determining whether controller initialisation was successful or not (`bInitOk`). But, in case TF broadcasts are enabled, uncalibrated groups (specifically: robots) will have their origins coincident, which will (most likely) not be representative of their physical configuration (ie: in case those groups are different manipulators, those will not occupy the same physical space). In those cases an alarm is raised to notify the user of this potential misconfiguration. But only if the alarm hasn't been disabled by user configuration.
Initial set to encode assumptions.
ted-miller
commented
Nov 15, 2023
Thanks for the review @ted-miller. I'll update the original #169 and close this one. We can continue there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm just creating this PR as a way to review an alternate fork/branch to #169.
This is in response to: #169 (comment)