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

VertexSE3Expmap vertex number must greater than 1? #583

Open
dwindy opened this issue Apr 4, 2022 · 2 comments
Open

VertexSE3Expmap vertex number must greater than 1? #583

dwindy opened this issue Apr 4, 2022 · 2 comments
Labels

Comments

@dwindy
Copy link

dwindy commented Apr 4, 2022

Hi gusy,

I set a demo that contains:
some VertexSBAPointXYZ vertex (landmarks)
some VertexSE3Expmap vertex (camera pose)
and some EdgeStereoSE3ProjectXYZ edge (the observation that connects the two types of vertexes above)

While I find out if I just add ONE VertexSE3Expmap to the optimizer, there will be a runtime error like the below:

ORBG2O2: /home/xin/Desktop/playground/ORBG2O/Thirdparty/g2o/g2o/core/block_solver.hpp:75: void g2o::BlockSolver::resize(int*, int, int*, int, int) [with Traits = g2o::BlockSolverTraits<6, 3>]: Assertion `_sizePoses > 0 && "allocating with wrong size"' failed.

When I increase the VertexSE3Expmap to TWO and more, the g2o works fine.

Theroyicaly that I could optimize only one camera pose right?
So it might be because I used the wrong type of vertex?

any idea or tips for this?
Thanks in advance

@RainerKuemmerle
Copy link
Owner

In principle yes. The assert here guards memory allocation that otherwise would allocate zero elements.
Potentially, the Schur complement implementation can be refactored to allow for 0 poses as well.

Copy link

github-actions bot commented Jan 2, 2025

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 2, 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

2 participants