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

question about specifications of evaluation #43

Closed
seonhoon1002 opened this issue Jul 19, 2022 · 7 comments
Closed

question about specifications of evaluation #43

seonhoon1002 opened this issue Jul 19, 2022 · 7 comments

Comments

@seonhoon1002
Copy link

seonhoon1002 commented Jul 19, 2022

I had an exciting time to travel your codes the last few weeks, and I finally got the below results.

image

but I have a question about Waymo evaluation code.

How could I check the configuration of these metrics such as "Does it use bev or 3D, does it use @11 or @40 for mAP"

Because in KITTI, there is an option for choosing 'bev' or '3D', but I can't find it in waymo, except "compute_detection_metrics_main" created by binary file.

Summary: How could I check configurations of metrics on Waymo evaluation.

@Abyssaledge
Copy link
Collaborator

Thanks for your using.
compute_detection_metrics_main calculates 3D IoU@(0.7/0.5/0.5) for Vehicle/Pedestrain/Cyclist.
There is no concepts like R11 or R40 in Waymo. Different from the way in KITTI or COCO, Waymo uses score cutoff to sample data points on the PR curve. Specifically, Waymo samples a data point every 0.01 score from the PR curve (0.99, 0.98, ..., 0.01, 0). So it is more like a "R100" strategy.
BTW, which config did you use to get the results above? The results seem a little strange.

@seonhoon1002
Copy link
Author

"There is no concepts like R11 or R40 in Waymo. Different from the way in KITTI or COCO, Waymo uses score cutoff to sample data points on the PR curve. Specifically, Waymo samples a data point every 0.01 score from the PR curve (0.99, 0.98, ..., 0.01, 0). So it is more like a "R100" strategy. " --> Thank you for answer.

BTW, which config did you use to get the results above? The results seem a little strange. --> I test "configs>sst>sst_waymoD1_2x_3class_8heads_1f" which little modify your "configs>sst>sst_waymoD1_2x_3class_8heads_3f". And could you tell me what's wrong with the above results? if you are weird about form, it copies from "onenote" which I clean up my results. So It could be a little different from console form.

@Abyssaledge
Copy link
Collaborator

In your results, the performance of vehicle and pedestrian is a little bit lower (~1AP) while the cyclist has a higher number (~1AP).
I believe your results are basically correctly, but I recommend to use the center version in sst_refactor which is simpler and better.

@seonhoon1002
Copy link
Author

I want to check your code on the same setting in your paper, so I use the old version. But I agree with your advice. Next time I will use the latest version. Thanks.

@Abyssaledge
Copy link
Collaborator

Abyssaledge commented Jul 19, 2022

In fact, the code we used in our paper is not totally consistent with the code here. The performances are slightly different. For example, follow this repo, you may get 1 AP lower in Vehicle and 2 AP higher in Pedestrian. @seonhoon1002

@seonhoon1002
Copy link
Author

So if you don't mind, could you tell me more detail about the differences between the code and your paper? @Abyssaledge

@Abyssaledge
Copy link
Collaborator

I am going to update the old config in couple of days.

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