-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
triangulation with know poses #2327
Comments
YOu can run openMVG_main_SfMInit_ImageListingFromKnownPoses and then reun SequentialSfM 2 with the mode known poses. So run main_SfM with INCREMENTALV2 and EXISTING_POSE https://github.com/openMVG/openMVG/blob/develop/src/software/SfM/main_SfM.cpp#L286 |
Thanks for your explaination!
However, the evaluation of these 4 expriments have something in common. The errors compared with GT poses is large at the begin and end of the trajectory, and errors decrease at the middle section.
Sorry for the late reply. Hope you can give me some advices. Many thanks! |
Hi
Thanks for the gread work!
Since i already have prior poses with real scale that lack of accuracy in autodriving scene, I prefer to appIy triagulation with those prior poses and then run ba to obatain more accurate extrinsic paramters with real scale.
I have noticed that there are several ways to run with prior known poses, such as using GPS prior in image EXIF, or using openMVG_main_SfMInit_ImageListingFromKnownPoses to load prior poses. However, using the first method, the prior pose only constrian the translation which will cause a random angle error compared with INS (mainly in roll in vehicle coordinate). Besides, i tried to use openMVG_main_SfMInit_ImageListingFromKnownPoses with ETH_3D format which poses are camera2world, if i use openMVG_main_ComputeStructureFromKnownPoses func, the BA process run only 1 iter that is not enough; if i use openMVG_main_SfM INCREMENTAL func, the scale seems to be eliminated.
I would be really appreciate it if you could give some advise on it.
Many thanks
The text was updated successfully, but these errors were encountered: