We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Culane的generate_line()会像论文中说的,按照k-th location来做expectation of predictions,详见line 24, line 26和line 44, 其中line 44有-1是因为画图的时候图像坐标从0开始对吗?
Ultra-Fast-Lane-Detection/evaluation/eval_wrapper.py
Lines 9 to 45 in 353df10
但是在TUSimple的generate_lines()函数中,见line 72, 74, 81:
Lines 64 to 83 in 353df10
/(griding_num-1)
The text was updated successfully, but these errors were encountered:
@Goooyi 有同样的疑问,为什么两个数据集处理方式不同
Sorry, something went wrong.
No branches or pull requests
Culane的generate_line()会像论文中说的,按照k-th location来做expectation of predictions,详见line 24, line 26和line 44,
其中line 44有-1是因为画图的时候图像坐标从0开始对吗?
Ultra-Fast-Lane-Detection/evaluation/eval_wrapper.py
Lines 9 to 45 in 353df10
但是在TUSimple的generate_lines()函数中,见line 72, 74, 81:
Ultra-Fast-Lane-Detection/evaluation/eval_wrapper.py
Lines 64 to 83 in 353df10
首先72行没像culane一样+1计算出k-th location, 相当于用了每个grid格子的左端点?
然后81行+0.5是因为由于tusimple的griding_num=100所以+0.5相当于从格子左端点变成了格子的中间点?那为什么要
/(griding_num-1)
来除以区间个数呢?The text was updated successfully, but these errors were encountered: