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

Options for classifier acceptance accuracy threshold #535

Open
StephenChan opened this issue Mar 24, 2024 · 0 comments
Open

Options for classifier acceptance accuracy threshold #535

StephenChan opened this issue Mar 24, 2024 · 0 comments
Milestone

Comments

@StephenChan
Copy link
Member

StephenChan commented Mar 24, 2024

Currently, any newly trained classifier is only accepted if the overall accuracy has improved at least 1% over the source's previous classifier (when both classifiers are evaluated on the latest training data).

However, there may be cases where the source owner prefers the newly trained classifier even if the accuracy didn't improve by 1%. For example, maybe the new classifier incorporates significantly more data for rare taxa, but since the accuracy is mostly influenced by common taxa, the accuracy wasn't affected much.

We can offer more flexibility by having option(s) for the acceptance threshold:

  • Be able to tweak the accuracy improvement threshold to another number - 0.5%, 2%, etc.
  • Have no accuracy improvement threshold at all, so any classifier is accepted

Remember, there's still a requirement to have 10% more confirmed images than the last training, so this issue's proposal alone won't really put us in danger of unreasonable numbers of training requests. (That's more the domain of issue #410 )

There's also the opposite idea of accepting no newly trained classifiers, essentially having an infinitely high threshold. However, it makes more sense to prevent new trainings rather than let the trainings run and not use them. So that goes in a separate issue I think.

@StephenChan StephenChan added this to the 2.0 milestone Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant