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

The waymo_detzero_track.yaml configuration file was used in the tracking stage, and the POINT THRESHOLD of the SECOND STAGE was modified to [3, 1, 1], which was consistent with the paper, but no trace was captured. #31

Open
Winston-Lii opened this issue Nov 1, 2023 · 2 comments

Comments

@Winston-Lii
Copy link

Error as described above, default setting of POINT THRESHOLD is [0, 0, 0] in github code, which is inconsist with paper and unreasonable, This results in a large number of Bboxes with no internal point cloud. But when change it to [3, 1, 1], there is no track be tracked.

@PrinceVictor
Copy link
Collaborator

  • The default setting of POINT THRESHOLD = [0, 0, 0] is to avoid computing numbers of points within detection boxes, which would consume a significant amount of time.
  • If you set POINT THRESHOLD to [3, 1, 1], please uncomment the line 12 in waymo_dataset.yaml to enable preprocess module 'points_in_box'.

@Winston-Lii
Copy link
Author

  • The default setting of POINT THRESHOLD = [0, 0, 0] is to avoid computing numbers of points within detection boxes, which would consume a significant amount of time.
  • If you set POINT THRESHOLD to [3, 1, 1], please uncomment the line 12 in waymo_dataset.yaml to enable preprocess module 'points_in_box'.

OK, thank you for your reply.

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

2 participants