woven-planet / l5kit

L5Kit - https://woven.toyota
https://woven-planet.github.io/l5kit
858 stars 277 forks source link

Clarification about distance_ref_trajectory #308

Closed FrancescoMandru closed 3 years ago

FrancescoMandru commented 3 years ago

In your code it is written than differently from L2 displacement:

This metric will compute the distance from the predicted centroid to the closest waypoint in the reference trajectory.

What do you mean by the predicted centroid? Do you compute the center point of the trajectory and then you find the closest point to the ground truth? If so, why do you consider such metric?

Thank you!

lucabergamini commented 3 years ago

This metric does not depend on time (differently from L2).

Imagine the following situation:

L2 will trigger (because at T you're 10m off). Distance to ref won't because you're still on the ref trajectory

FrancescoMandru commented 3 years ago

Thank you. So a common case where the ref trajetcory trigger is when there are lateral deviations with respect to the annotated trajectory for example?

lucabergamini commented 3 years ago

correct!

FrancescoMandru commented 3 years ago

Last question, in Open Loop evaluation you evaluate the ADE. Is this metric similar to the L2 displacement computed in Closed Loop?