-
Notifications
You must be signed in to change notification settings - Fork 35
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
I used the original vinsmono and got different results from your paper. Why is that? #2
Comments
The OpenLORIS-market-1 dataset is as same as yours |
Hi,
The error reported is without scale correction ie we do only SE3 alignment,
since VINS is expected to estimate the correct metric scale.
…On Wed, Apr 14, 2021, 19:59 HuangChen ***@***.***> wrote:
The OpenLORIS-market-1 dataset is as same as yours
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADARGK7V24PF7BU3XAPCBSTTIWRFPANCNFSM425QI3SQ>
.
|
Even without scale correction the error might not exactly be the same as
reported in the paper due to RANSAC, and other OS related delays. But the
error from RP-VIO should still be lesser than VINS-Mono.
…On Wed, Apr 14, 2021, 20:29 Karnik Ram ***@***.***> wrote:
Hi,
The error reported is without scale correction ie we do only SE3
alignment, since VINS is expected to estimate the correct metric scale.
On Wed, Apr 14, 2021, 19:59 HuangChen ***@***.***> wrote:
> The OpenLORIS-market-1 dataset is as same as yours
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#2 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADARGK7V24PF7BU3XAPCBSTTIWRFPANCNFSM425QI3SQ>
> .
>
|
Hi, bro I get rmse = 1.128904 Then I run rpvio with I get rmse = 1.242076 why the error from VINS-Mono still be lesser than RP-VIO? same ol_market_config.yaml and computer |
Hi, The config file which you've used is specific to RP-VIO and differs from the default VINS-Mono parameters. I just noticed that I haven't uploaded the config file that we used for evaluating VINS-Mono. Here it is for the OL sequence - RP-VIO needs different parameters (provided in Thanks for reporting and please let me know about your results with this updated config file. I will also try including the VINS-Mono evaluation scripts that we used in the repo. |
Hi, |
Have you run the segmentation part ? from RecoverPlane import RecoverPlane Have you met this error before? |
I run the segmentation part,but I didn't get this error |
How to run the segmentation part? could you please give me some advices? What is your OS ? |
There is no need to run segmentation part separately, because the segmentation part is in the datasets, just download the author’s datasets and follow the command provided by the author to run |
Yeah, but I wanna to use it on my dataset |
I used the ol_market1_config.yaml file of your rp-vio project to directly run VINS-MONO on the OpenLORIS-market-1 dataset, and got a higher accuracy than your paper (paper is 2.45, but I got Absolute Trajectory RMSE = 0.88). Why?
The evaluation tool I use is EVO, and the link is [https://github.com/MichaelGrupp/evo]
The command is
evo_ape tum groundtruth.txt vins_result_no_loop.txt -va -p --plot_mode=xyz --align --correct_scale
Looking forward to your answer
The text was updated successfully, but these errors were encountered: