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

3D MOT code #139

Open
chumpblocckami opened this issue Oct 26, 2023 · 2 comments
Open

3D MOT code #139

chumpblocckami opened this issue Oct 26, 2023 · 2 comments

Comments

@chumpblocckami
Copy link

In the official website is referencing multiple times the 3D MOT, which essentially runs the evaluation using x,y,z coordinates instead of bounding boxes.

After inspecting the repo, i found no evidence of the 3D MOT evaluation script, nor anything related to x,y,z coordinates in MOT challenge.

Can you please reference me to the point where x,y,z coordinates are used in a way that i can evaluate my world coordinates tracker?

Thanks a lot!

Happy coding

@michael-hoss
Copy link

This would indeed be nice.

The docs recommend to convert own data to the MOTChallenge format. When I dig deeper, I find:

Similarly, the bounding boxes are ignored for the 3D challenge.

But then, the code here only supports the 2D Box:

dataset_list = [trackeval.datasets.MotChallenge2DBox(dataset_config)]

@michael-hoss
Copy link

It also looks like #71 would enable 3D evaluation.

But I also just read that at least the official KITTI 3D Object Detection benchmark still requires you to submit 2D bounding boxes in the image plane

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