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

Use AccumulatedRangeDataCallback for trajectory states #556

Closed
wants to merge 1 commit into from
Closed

Use AccumulatedRangeDataCallback for trajectory states #556

wants to merge 1 commit into from

Conversation

ojura
Copy link
Contributor

@ojura ojura commented Oct 25, 2017

last_range_data->returns,
(last_constant_data->local_pose
// THIS IS CURRENTLY BROKEN FOR 3D. THE FOLLOWING MULTIPLICATION
// SHOULD BE APPLIED ONLY FOR 2D!
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As noted in the code comment. The range data in 2D and 3D does not currently have the same relationship with last_constant_data->local_pose.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bad idea. The only reason for the existence of the gravity aligned frame is that it is necessary to express certain rigid transforms using Rigid2. Other than that, it should not be used.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am aware it is bad idea, we need to discuss what to change in libcartographer to resolve this.

@ojura ojura closed this Nov 10, 2017
wally-the-cartographer pushed a commit that referenced this pull request Nov 16, 2017
Replaces #556.
Use `LocalSlamResultCallback` cartographer-project/cartographer#574 instead of `PoseEstimate`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants