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

ONE PROBLEM in the evaluation method for CULane #112

Open
yoga-0125 opened this issue Jun 12, 2020 · 1 comment
Open

ONE PROBLEM in the evaluation method for CULane #112

yoga-0125 opened this issue Jun 12, 2020 · 1 comment

Comments

@yoga-0125
Copy link

Hi, I have one question regarding to the lane evaluation method. My thought may be not correct, but please read it and give me some suggestions if possible, thank you.

  • In CULane, different images may have different lane end point labelling (eg. 280, 410 ...)
  • When extracting lane points from prob maps, the number of points determine the end point of lanes (eg. m=15 points result in the end points of lanes are 310)
  • Predicted lane (310) can be shorter than ground truth (280) ["estimation is not enough"] or longer than ground truth (410) ["over estimation"]
  • As the attached figure shown, I thought lane fitting is evaluated with almost same length, but here, different length of prediction and ground truth also affects on false positive and false negative

Capture

@XingangPan
Copy link
Owner

@yoga-0125 Your understanding is correct. We believe that predicting the length accurately is also important for lane detection, thus length is considered in the evaluation metric.

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