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

Low overlap stereo cameras #22

Open
mateosss opened this issue Jun 14, 2022 · 2 comments
Open

Low overlap stereo cameras #22

mateosss opened this issue Jun 14, 2022 · 2 comments
Labels
algo-performance Issues related to the accuracy or CPU consumption of the method

Comments

@mateosss
Copy link

Hello, I have a pair of stereo cameras from a VR headset that point at different angles. I've been able to get HybVIO to track stereo features only with -useRectification, but even then it doesn't seem possible for HybVIO to track features on the non-overlapping areas of the images.

  1. Is there a way to avoid having to prerectify the images in this case?
  2. Is it possible to track non-overlapping features in HybVIO?

Below is a stereo frame example obtained by running this command:

./main -i=../data/benchmark/ody-easy -p -c -s -windowResolution=640 -useSlam -useStereo -displayStereoMatching -useRectification

Over this HybVIO-formatted dataset. The original EuRoC-formatted dataset can be found here.

2022-06-14-135018_1284x521_scrot

@oseiskar
Copy link
Member

Hello! Your findings are consistent with our understanding of the capabilities of the current HybVIO code

  1. Sometimes rectification is needed in practice or the left-to-right LK tracking fails (even though it "should not"). The current rectification implementation is very slow, which could be worked around by rectifying manually with, e.g, OpenCV before feeding the data to HybVIO (this also needs to be reflected in the calibration in parameters.txt). There are currently no work-arounds for the need for rectification in this case, except fixing/modifying the stereo LK-tracking implementation
  2. The current code does not have the capability of tracking non-overlapping features in the case of -useStereo. It should be possible to extend the algorithm to support them

@mateosss
Copy link
Author

I see, thank you!

@oseiskar oseiskar added the algo-performance Issues related to the accuracy or CPU consumption of the method label Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
algo-performance Issues related to the accuracy or CPU consumption of the method
Projects
None yet
Development

No branches or pull requests

2 participants