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

Monocular Localization against map created with RGB-D with very poor performance #1395

Open
jsreveal opened this issue Dec 3, 2024 · 2 comments

Comments

@jsreveal
Copy link

jsreveal commented Dec 3, 2024

Hi guys,

I have created with success a map with Intel RealSense D455. I am trying now to do localization in that map using a different camera, monocular RGB camera, however most of the frames are not correctly localized even though I am l looking into the same place as when creating the map.

Is this use case possible to work well at all?

What settings could be changed to try to improve localization?

@matlabbe
Copy link
Member

matlabbe commented Dec 4, 2024

I think the big difference is the "different camera". Is the field of view similar to D455? Is the resolution similar?

You can compare by feeding the same RGB topic used for mapping from the D455 (simulating a monocular camera without the depth).

If FOV and resolution are very different, you may want to use SIFT features for localization (Kp/DetectorStrategy=1).

@borongyuan
Copy link
Contributor

I have tested using OAK-D W to build the map in the first session and OAK-D S2 in the second session, and localization can be triggered normally. So the camera FOV actually has little impact. You may need further examination.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants