Skip to content

Why doesn't the reprojection error residual use normalized units? #4453

Description

@ronald3511

First of all, thank you for this wonderful software!

It looks like the global BA pipeline uses ReprojErrorCostFunctor, which computes residuals in pixel units.

But when filtering outliers in GlobalMapper::GlobalPositioning(), the points are filtered based on the normalized reprojection distances (distances on the normalized image plane).

I'd like to ask why does ReprojErrorCostFunctor compute the residual in pixel units instead of using the normalized reprojection error like the point-filtering method does?

If there are 2 cameras, CamA with the resolution 640x480 px, and CamB with 3840x2160 px, then reprojection error of 1 px is more severe for CamA than for CamB. Doesn't the lack of normalized reprojection error introduce bias into the optimization?

The distortion is also computed in the normalized image plane, so why not the reprojection error too?

I'm sure you had a very good reason to choose not to normalize the residual in ReprojErrorCostFunctor, but I can't figure out why is it better than using the normalized error. In my mind, the normalized error would make the error independent of cameras' resolution, which would remove bias.

Thanks!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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