-
Notifications
You must be signed in to change notification settings - Fork 767
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
Wrap translation averaging #513
Conversation
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.
Awesome, just one small comment...
@@ -2914,6 +2914,13 @@ class BinaryMeasurement { | |||
typedef gtsam::BinaryMeasurement<gtsam::Unit3> BinaryMeasurementUnit3; | |||
typedef gtsam::BinaryMeasurement<gtsam::Rot3> BinaryMeasurementRot3; | |||
|
|||
class BinaryMeasurementsUnit3 { | |||
BinaryMeasurementsUnit3(); |
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.
All these are generic and should be just added above in BinaryMeasurement
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.
Great, I did not know that. Removed it.
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.
Actually, I apologize but I was wrong:
- I did not see this was about the vector of measurements, so my comment was wrong
- by the specialization stuff, these methods are indeed available in a pythonesque way in the python wrapper. However, I think it still needs to be here for the MATLAB wrapper. @ProfFan can confirm.
PS @ProfFan this state of affairs is really not great, even thought not necessarily in your plate: I think we should adapt the wrap language to deal with these things in a uniform and transparent way. After all, the wrap code is a code generator. Surely this should not be on the user.
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.
Yes, you still need to create theXxxVector
, XxxMap
type aliases for the MATLAB wrapper. I demonstrated this in #511 for DSFMap, you can refer to that PR @akshay-krishnan .
I agree that we should extend the wrap language to deal with this, but currently I have no bandwidth on it, and I cannot think of an idiomatic way to do this...
This PR wraps translation averaging to provide a Python interface. The included python test verifies that the interface works well.