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

Levenberg Algorithm for EdgeSE3ProjectXYZOnlyPose class working poorly with big scales #336

Closed
Roysorus opened this issue Jan 2, 2019 · 4 comments
Labels

Comments

@Roysorus
Copy link

Roysorus commented Jan 2, 2019

Hello,

I have a 3D points cloud that I'm tracking thoughout a video. I'm using g2o for Pose Opitmization as in PoseOptimization to optimize the pose by minimizing the reprojection error of the points.
The problem is that, for the same video, g2o seems to work really bad for very big values of the 3D coordinates of the points(big values of the SE3 pose to optimize). However, when I rescaled the 3D coordinates of the points to be really smaller(small values of the SE3 pose to optimize), g2o seems to be working just fine.
I was wondering if there were another way to make Pose Optimization with g2o's implementation of Levenberg algorithm work on big scales?

@Roysorus Roysorus changed the title Levenberg Algorithm for EdgeSE3ProjectXYZOnlyPose class working poorly Levenberg Algorithm for EdgeSE3ProjectXYZOnlyPose class working poorly with big scales Jan 2, 2019
@ferreram
Copy link

Hi there,
If you have many 3D points which can be considered as being at infinity optimization you can try using an inverse depth parametrization (you can have a look at the example ba_anchored_inverse_depth).

@MarceloContreras
Copy link

I found another solution that may help you. I was having the same problem as soon as I was inserting points w.r.t world position that were triangulated in forward camera poses. Try to set as the pose estimate the pose from world frame w.r.t camera frame (Tcw) just like in ORB-SLAM 2 PoseOptimization (src/Optimizer.cc) method

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label Jan 13, 2025
Copy link

github-actions bot commented Feb 5, 2025

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants