-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Segmentation fault for SE3 case optimisation using g2o CLI #571
Comments
You need to add one Parameter to the edge. Not link a parameter as a vertex. The parameter describes an offset to apply on the pose vertex of the edge. So on your file add as first line Add it to the EDGE_SE3_TRACKXYZ: Using the noise.txt from #528 We can do the above mentioned modifications on the file as follows
|
@RainerKuemmerle thank you for the reply. Now, the above command doesn't throw an error on execution. However, I would like to know the significance of this PARAMS_SE3OFFSET variable. Can you please mention the same? |
It is not a variable of the optimization problem but a fixed offset between the pose of the vertex and the camera observing the points. |
@RainerKuemmerle Okay, I get what you are trying to say. But, is there some kind of documentation or reference available? I would like to know more about it. |
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. |
noise_old.txt
The above noise file is having a few robot noisy poses (SE3) and some landmarks (3D). In addition, odometry constraint, loop closure, and observation edge. I believe the vertex and edge format to be correct(please confirm the same). So, when I try to run the following command from the ubuntu 20.04 terminal:
I get the following output:-
But when I remove all EDGE_SE3_TRACKXYZ observation edges. It is running successfully without any issue/error.
This issue has been created because of a discussion on issue #528. @RainerKuemmerle asked to put PARAMS_SE3OFFSET in the file for optimizing using g2o CLI, as EdgeSE3PointXYZ won't work without it. However, the issue still remains the same. I don't know if I'm giving the wrong syntax for PARAMS_SE3OFFSET. But I used the following format:
where
x y z qx qy qz qw
are having the same value as the corresponding robot pose vertex has for the given edge between robot pose & landmark. Below is the updated noise file.noise.txt
However, this file is giving same output as above file.
Also, can someone please mention the correct format for giving g2o::ParameterSE3Offset to the noise file (i.e. what are the values to be written in front of PARAMS_SE3OFFSET in the noise file and what they denote) that I shared in the above chat, as I'm using g2o cli? I couldn't find it on the g2o wiki page.
The text was updated successfully, but these errors were encountered: