Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
bob.measure
bob.measure
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • bob
  • bob.measurebob.measure
  • Issues
  • #6

Closed
Open
Opened Mar 03, 2016 by André Anjos@andre.anjos💬
  • Report abuse
  • New issue
Report abuse New issue

`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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
enhancement
Assign labels
  • View project labels
Reference: bob/bob.measure#6