lyft / lyft/nuscenes-devkit

Issue with export_kitti, The Translation part of P matrix is always kept Zero which might not be correct.

Open
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
390
Forks
99
PR merge metrics
No merged PRs in 30d

Description

It happened when I am working on Lyft Dataset for 3D object detection using Frustum Pointnet.

When performing the LiDAR projection on to image and frustum is extracted. It's doesn't look same as in the original kitti dataset.

The only difference in the whole procedure is the P2 calibaration used,

May be a check's needed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the export_kitti entry point and inspect how the P2 calibration matrix is constructed, especially its translation component. Compare the exported calibration and resulting LiDAR-to-image frustum projection with the original KITTI procedure; done means determining whether the translation should be preserved and correcting the mismatch if confirmed.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
computer-vision
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.