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

Update the 50 m threshold in the performance requirements #10

Closed
mrksbrg opened this issue Feb 16, 2022 · 2 comments
Closed

Update the 50 m threshold in the performance requirements #10

mrksbrg opened this issue Feb 16, 2022 · 2 comments
Assignees

Comments

@mrksbrg
Copy link
Member

mrksbrg commented Feb 16, 2022

The 50 m threshold for pedestrian detection and recognition in the performance requirements does not match the ODD. If ego car moves at 70 km/h, a TTC of 4 s means that the pedestrian can be almost 80 m away.

@mrksbrg mrksbrg self-assigned this Feb 16, 2022
@mrksbrg
Copy link
Member Author

mrksbrg commented Feb 16, 2022

This is related to Issue #8. Since we replaced accuracy with true positive rate in SYS-PER-REQ1, SYS-PER-REQ2 is now redundant. We solve this by specifying requirements on TPR and FNR at different distances. We replace 50 m with 80 m in all cases except in SYS-PER-REQ2 where we keep 50 m. We motivate this by the presence of a driver - the driver is reponsible for braking ego car if a pedestrian shows up, thus we measure FNR closer to the vechicle.

@mrksbrg
Copy link
Member Author

mrksbrg commented Feb 16, 2022

At the same time, align ego car and ego vechicle throughout the SRS.

mrksbrg added a commit that referenced this issue Feb 16, 2022
@mrksbrg mrksbrg closed this as completed Feb 16, 2022
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