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

Motion metrics - bbox matching threshold ? #210

Open
Fixed-Sidet opened this issue Nov 3, 2024 · 0 comments
Open

Motion metrics - bbox matching threshold ? #210

Fixed-Sidet opened this issue Nov 3, 2024 · 0 comments

Comments

@Fixed-Sidet
Copy link

Hello,

In nuscenes_e2e_dataset.py, starting at line 1196, the motion metrics are calculated 6 times.
Those calculations are done in nuscenes_eval_motion.py :

  • eval_mode="standard":
    bbox matching dist threshold: [0.5,1,2,4]
    dist_th_tp = 2.0
    Traj_dist_th = None

  • eval_mode="motion_map"
    bbox matching dist threshold: [1.0]
    dist_th_tp = 1.0
    Traj_dist_th = 2.0

  • ...

Which one of those metric results are the ones you report in the paper?

I also noticed that when using eval_mode = 'epa', self.cfg_dist_ths and self.cfg_dist_th_tp are overwritten.
In the fourth metric calculation, which uses the MotionEval class initialized with category_convert_type='detection_category',
those thresholds are not reset: I was wondering if this in intentional.

Thank you.

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

1 participant