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

Camera intrinsic matrixes cam2imgs not adapted to the input size in get_lidar_coor(...) #342

Open
dyou-dev opened this issue Apr 23, 2024 · 3 comments

Comments

@dyou-dev
Copy link

In class LSSViewTransformer -> def get_lidar_coor(...), the camera intrinsic matrixes cam2imgs is of the src size (900, 1600), not of the input size (256, 704).

Reproduction

  1. Add the following code in class LSSViewTransformer -> def get_lidar_coor(...).
    print(self.frustum.shape)
    print(self.frustum[0, -1, -1, ...].to(int))
    print(cam2imgs.to(int))
    quit()

  2. Run the test.
    python3 tools/test.py configs/bevdet/bevdet-r50.py ../bevdet-r50.pth --format-only --eval-options jsonfile_prefix=out

  3. Get the log.
    torch.Size([59, 16, 44, 3])
    tensor([703, 255, 1])
    tensor([[[[1257, 0, 827],
    [ 0, 1257, 450],
    [ 0, 0, 1]],

It shows that the (u, v) of input size (256, 704) will be operated with the camera intrinsic matrix of src size (900, 1600).
It looks like an issue, or is there any special consideration here?

@dyou-dev
Copy link
Author

The issue was found with the branch dev2.0, commit 2ae6a02. I haven't checked other branches yet.

@441599828
Copy link

hi. i have the same question, any explanation?

@BozhouZha
Copy link

The resize ratio seems to be blended into post_rot already, which was also applied to frustum points.

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