Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.measure bob.measure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.measurebob.measure
  • Issues
  • #6
Closed
Open
Issue created Mar 03, 2016 by André Anjos@andre.anjos💬Owner

`bob.measure.cmc` and `bob.measure.recognition_rate` are not prepared for an open-set identification

Created by: tiagofrepereira2012

Today the functions bob.measure.cmc and bob.measure.recognition_rate does not support a decision threshold as an argument.

This constrain the scope of these functions only for closed-set identification tasks. I suggest to add an optional keyword argument called threshold for that purpose in these functions. This may impact bob.measure.cmc_four_column and bob.measure.cmc_five_column

Assignee
Assign to
Time tracking