-
Notifications
You must be signed in to change notification settings - Fork 249
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
add Sim(2) #201
add Sim(2) #201
Conversation
argoverse/utils/sim2.py
Outdated
sRt = -Rt @ (self.s_ * self.t_) | ||
return Sim2(Rt, sRt, 1.0 / self.s_) | ||
|
||
def transformFrom(self, point_cloud: np.ndarray) -> np.ndarray: |
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 imagine this naming is by convention, but I personally get confused by it. What would be positive / negatives of something like to_target
or to_target_frame
vs transformFrom
?
Additionally, depending on the discussion above, should we consider conforming to snake case?
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.
Just switched to snake case -- thanks.
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.
Looks good, John. I had a few thoughts regarding overall structure in the code base moving forward. Definitely curious on your thoughts.
argoverse/utils/sim2.py
Outdated
|
||
Refs: | ||
http://ethaneade.com/lie_groups.pdf | ||
https://github.com/borglab/gtsam/blob/develop/gtsam_unstable/geometry/Similarity3.h |
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.
This link gives me a 404.
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.
good catch -- i just updated it with the correct link
LGTM 👍 |
Add support for 2d rigid body transformations with scaling, e.g. Similarity(2), instead of just SE(2) transformations. SE(2) functionality is already implemented in
argoverse-api
here