Serious problem in overlap part of one poind cloud

[JiaruiWang-Jill]

Hi, @gaoxiang12 . Thanks a lot for providing this useful tool.

I use orb slam2 with kinect v1 to reconstruction 3D point cloud. Here is one work result.

I got quite confused because there is a serious problem in overlapping part. I think calibration should not be the first reason. But I fail to think out other resolutions.

Any suggestions? Thx a lot in advance!

[gaoxiang12]

This is probably due to the drift in the estimated trajectory. I'm not sure if your orb-slam2 find this loop closure, if so you can rebuild the map after loop closing so that you get the right pose.

[JiaruiWang-Jill]

Thanks a lot for your reply!

I am little confused of the concept " rebuild the map ". Why do we need to rebuild the map? Shouldn't we only need to concentrate on rgb+depth+pose? Besides, how to rebuild the map?

Sorry to ask if it is a stupid question.

[RahmanMifta]

@JillWangJill Hello.
Have you found any solution to your problem? I am also facing same problem.

[JiaruiWang-Jill]

Hi, it was long time ago. I remembered that some serious drift can be killed by moving your device more horizontally, instead of sticking it to one point and circling it. Also, the R,T of key frames will change after matching the same place. Therefore, when generating the mesh/point cloud. As for other aspects, I fail to find a proper solution. Hope these can help.

…

On Thu, Jan 17, 2019, 5:20 PM Miftahur Rahman ***@***.*** wrote: @JillWangJill <https://github.com/JillWangJill> Hello. Have you found any solution to your problem? I am also facing same problem. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AnRW-Blc33WYHES1fF4YJtLs4YecKQtNks5vEEBygaJpZM4WDQFO> .