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

Definition of Miss Rate #1135

Closed
a-pru opened this issue Jan 22, 2025 · 2 comments
Closed

Definition of Miss Rate #1135

a-pru opened this issue Jan 22, 2025 · 2 comments

Comments

@a-pru
Copy link

a-pru commented Jan 22, 2025

Hi,

In your prediction evaluation code, a prediction is deemed a miss if the maximum distance between any predicted trajectory and the ground truth at any time t exceeds the defined threshold.

In contrast, Argoverse and WOMD use the following definitions:
Argoverse 1/2: The number of scenarios where none of the forecasted trajectories are within 2.0 meters of ground truth according to endpoint error.
WOMD: A miss is defined as the state when none of the individual K predictions for an object are within a given lateral and longitudinal threshold of the ground truth trajectory at a given time T.

Could you elaborate on the rationale of using maximum displacement instead of minimum displacement to compute the miss rate?
My intuition aligns rather with AV1/2 and WOMD: diverse trajectories are desirable (not all predictions should collapse to the same mode), and if at least one predicted trajectory matches the ground truth, I would typically not consider it a miss.

Thank you and all the best,
Alex

@whyekit-motional
Copy link
Collaborator

@a-pru if you take the max over the last two dimensions of an array of shape [num_modes, horizon_length, state_dim], then the resulting array will have shape [num_modes]:

import numpy as np


stacked_trajs = np.random.rand(5, 4, 3)
stacked_ground_truth = np.random.rand(5, 4, 3)
result = np.max(np.linalg.norm(stacked_trajs - stacked_ground_truth, axis=-1), axis=-1)
print(result.shape)  # (5,)

So the max is over the horizon length (and not the modes)

@a-pru
Copy link
Author

a-pru commented Feb 10, 2025

Of course, you're right—thanks for the clarification and sorry for the confusion.

@a-pru a-pru closed this as completed Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants