- Following are the results of dataset 2 optimization just using manhattan constraints.
Created
August 31, 2019 23:50
-
-
Save UditSinghParihar/f5ce292b62b22c8e78186f6dddeb2419 to your computer and use it in GitHub Desktop.
Dataset 2 g2o optimization using manhattan constraints
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dense ground truth trajectory:
Dense noisy trajectory:
Manhattan sparse trajectory:
Transformation of all the nodes with respect to the first node in above manhattan trajectory is caculated and given as loop closing constraints. It can be seen as overlying 3rd image constraints over 2nd image dense noisy trajectory.
Before g2o optimiztion:
After g2o optmization:
Note that left rackspaces are shifted upwards, this is due to drift in manhattan constraints itself which were given as constraints. So there is scope of inprovement using ICP or incremental manhattan formulation.
Comparison of noisy, optimized and ground truth trajectory:
As all the constraints are consistenly given from manhattan graph only, so there is no hardcoding involved. And as the manhattan is close to ground truth so we can always extract relative transfomtion between 2 nodes when MLP say two nodes are same (instead of del_x=0.2, del_y=0.2)