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

Target frame optional #217

Merged

Conversation

efernandez
Copy link
Collaborator

On top of #216, this also makes the target frame parameters optional.

If not set, the target frame parameters default to empty(). In that case not transformation is performed. In this implementation, I actually fallback to the message header.frame_id, because it looks cleaner, but we could also consider bigger changes to factorize things out.

@efernandez efernandez self-assigned this Dec 8, 2020
@efernandez efernandez added the question Further information is requested label Dec 8, 2020
@svwilliams
Copy link
Contributor

This PR now needs a rebase. I really wish git would handle these squash-and-merge cases more gracefully.

@efernandez
Copy link
Collaborator Author

That's ok. Indeed, in this case three 3-way merges got applied when I rebased it, so I guess that prevents github from running an automatic rebase/merge itself. At least in this case, my experience tells me that's better to review the result of the the rebase/3-way merge. That's what I've done and I believe things are fine.

@efernandez
Copy link
Collaborator Author

I've just sent a commit to remove the optional target_frame parameters in the fuse_optimizers tests.

@svwilliams svwilliams merged commit 34840fc into locusrobotics:devel Dec 15, 2020
@efernandez efernandez deleted the target-frame-optional branch December 15, 2020 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Development

Successfully merging this pull request may close these issues.

3 participants