8000 About Vloc methods used in the supplmentary table? · Issue #219 · naver/dust3r · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
About Vloc methods used in the supplmentary table? #219
Open
@Jinjing98

Description

@Jinjing98

Thanks for the great work! While I have a bit confusion when reading your paper:

It is a bit unclear to me regarding the discussion and tables in supplmentary about Vloc tasks: accroding to the Tab.6, the performance degradation seems to come from the absence of GT intrinsics, wheras in the discussion it looks to point toward the sparsity of Cambridge SfM model?

Continue on the above question, have you tried the evalutaion with estimated instrinsics following "2D-matching" based loc method? A bit curious how that deveriate from the reported ones given GT intrinsics :D I would assume on 7scenes, roughly same performance based on "scaled rel-pose" method can be expected in theory?

From the code point of view
I would assume the implementation in dust3r/visloc.py is for "2D matching" based method. If so, can I understand below line of code as a "correction" of 2D projection based on GT intrinsics of query image?

# rescale coordinates

Do you mind also providing the implementation for "scaled rel pose" based loc solution?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0