lukasvst / dm-vio

Source code for the paper DM-VIO: Delayed Marginalization Visual-Inertial Odometry
GNU General Public License v3.0
1.07k stars 187 forks source link

Program runs without result #12

Closed HappyB1rthday closed 2 years ago

HappyB1rthday commented 2 years ago

QQ图片20220511220140 Hi, The program is running, but there is no graphic or dot on Pangolin. The dataset is TUM-VI slides1. The resultsPrefix file exists but without anything. Is that normal? Or is there something wrong with the format of my input? Thanks for your help.

lukasvst commented 2 years ago

No, this is not normal, you should see the images in the bottom left of the Pangolin window and the system should make it past the initialization phase. The command looks ok at first glance.

Can you please post the full commandline output (especially the part before what's shown in the screenshot) so I can check if there is anything wrong with it?

HappyB1rthday commented 2 years ago

J3K%O7YE{6MOP`Z)WCGDIUF KPM$X{(4B8@9I1K~0HT7D{E Could you please check it for me

HappyB1rthday commented 2 years ago

The following output are all ‘InitTimeBetweenFrame’ and 'GTData distance'.

lukasvst commented 2 years ago

I don't see anything wrong in the output before it not initializing. I think there is something wrong with the installation, but it is a bit tricky to debug from a distance.

lukasvst commented 2 years ago

One more thing: Could you try to set mode=1 in the commandline arguments? As the images don't seem to arrive, the input to the photometric calibration could be wrong and this will disable it.

lukasvst commented 2 years ago

Do you have an update on this, were you able to resolve the issue? Otherwise I will close the issue in a week.

For future reference: My best guess is that the problem was that the images were somehow loaded as 8bit instead of 16bit. In this case a different pcalib file would need to be passed, otherwise the behavior is similar to what the @HappyB1rthday reported. For quickly testing this it is best to try to set mode=1as this mode does not use the pcalib file.

GeJintian commented 1 year ago

Do you have an update on this, were you able to resolve the issue? Otherwise I will close the issue in a week.

For future reference: My best guess is that the problem was that the images were somehow loaded as 8bit instead of 16bit. In this case a different pcalib file would need to be passed, otherwise the behavior is similar to what the @HappyB1rthday reported. For quickly testing this it is best to try to set mode=1as this mode does not use the pcalib file.

I meet exactly the same problem, and setting mode=1 solves this problem. Thanks a lot.

lukasvst commented 1 year ago

Thanks for letting me know!

One thing to note is that mode=1 disables the photometric calibration which will slightly reduce the accuracy. (But it's great to try for debugging.)

So you could try using mode=0 and passing gamma=PATH_TO_DMVIO/configs/pcalib_linear_8bit.txt which should hopefully work a bit better.

The explanation for this is that 8 bit images need a different pcalib (camera response calibration) file than 16 bit images, and in your case it seems like the images are loaded as 8bit.