Skip to content
This repository has been archived by the owner on Mar 2, 2018. It is now read-only.

Motion tracking accuracy #46

Open
higerra opened this issue Oct 22, 2015 · 0 comments
Open

Motion tracking accuracy #46

higerra opened this issue Oct 22, 2015 · 0 comments

Comments

@higerra
Copy link

higerra commented Oct 22, 2015

Hi, everyone,

I'm using project tango for 3D reconstruction project. I'm curious about the accuracy of motion tracking. I know that tango combines both visual features and IMU data, and I expect pixel accuracy. By pixel accuracy, I mean the reprojection error. However, In practice I found the drift among frames is fairly large. More specifically:

1.When the motion is purely translational in xy plane, the tracking error is pretty large. I expect that in feature based SLAM system, this error should be small.
2. When the motion is purely translational along z axis, the motion tracking is terrible. This is reasonable to me.
3. When the motion is purely rotational around y axis (rotate horizontally), the error is relatively small. I think this might thank to IMU sensor.

I also tried to perform ICP after getting all point clouds, but this doesn't help much. Because the depth resolution is pretty low, small error in 3D space will easily cause more than 20 pixels reprojection error on image.

The way I'm using the pose data is that I recorded the timestamp of each frame, and query their poses using mTango.getPoseAtTime() API at the end.

So I'm curious about whether I'm doing the right thing. And are there any suggestions about how to improve motion tracking?

Thanks all!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant