-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Added threshold
parameter to detector runner
#9011
Conversation
Why 0.9? Our Nuclio functions default to 0.5, and so do Roboflow/HF functions; seems like we should do the same to preserve the default behavior. |
IMHO it should be optional and default value should be |
May you update couple of docs here https://docs.cvat.ai/docs/manual/advanced/automatic-annotation/ Screenshots + describe threshold parameter |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #9011 +/- ##
===========================================
- Coverage 73.43% 73.43% -0.01%
===========================================
Files 418 418
Lines 44299 44299
Branches 3870 3870
===========================================
- Hits 32533 32532 -1
- Misses 11766 11767 +1
|
Quality Gate passedIssues Measures |
Documentation will be updated here: #8853 |
Motivation and context
Added an input field to detector runner with threshold parameter. The parameter already supported by the server.
By default the parameter is undefined and UI lets the server decide what threshold to use.
How has this been tested?
Checklist
develop
branch[ ] I have added tests to cover my changesLicense
Feel free to contact the maintainers if that's a concern.