-
Notifications
You must be signed in to change notification settings - Fork 29
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
Question about the threshold of score filter #2
Comments
Hi, what you are talking about is a very interesting question. However, I think 0.16 is a high rather than a low threshold. The reasons for choosing 0.16 are as following:
If you have any further questions, please feel free to chat with me. 😊 |
By the way, your visualization looks pretty. Is it possible to share this visual script? 😃 |
Oh, I get it. thank you for your reply. And the visual script comes from https://blog.csdn.net/qq_16137569/article/details/121066977. |
Nice! Any further questions, feel free to contact me. This issue will be closed. |
# This is the 1st commit message: add model # This is the commit message lixiaoyu2000#2: Update README.md # This is the commit message lixiaoyu2000#3: Update README.md # This is the commit message lixiaoyu2000#4: Update README.md
Hi, I find the threshold of score filter is very slow, about 0.16. And there will be many FP trajectories generated as valid trajectories. But the final evaluation indicators are still good. Why do you choose such a low threshold and why the final evaluation metric was still excellent?
The text was updated successfully, but these errors were encountered: