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
  • #20

Closed
Open
Opened Oct 28, 2016 by Manuel Günther@mguenther
  • Report abuse
  • New issue
Report abuse New issue

bin/bob_plot_cmc.py is not working as expected

The script to compute the open set recognition rate does not work as expected. When passing the --rank 1 option using a perfectly separable , the output of the script is:

Recognition rate for score file /mgunther/bob/bob.nightlies/src/bob.measure/bob/measure/data/scores-cmc-4col-open-set.txt is 0.00%

I think the reason is that in: https://gitlab.idiap.ch/bob/bob.measure/blob/master/bob/measure/script/plot_cmc.py#L93 we use the rankas the second parameter, while in https://gitlab.idiap.ch/bob/bob.measure/blob/master/bob/measure/__init__.py#L129 it is the third parameter. However, just using the right parameter (using keyword parameter as in https://gitlab.idiap.ch/bob/bob.measure/blob/master/bob/measure/script/plot_cmc.py#L126) does not work either.

@andre.anjos : I know that you like the docopt command line parser. I don't. I believe the argparse module is much more powerful as it automatically converts parameters to the desired data type, and automatically sets default options, if desired.

In docopt you have to specify all these by hand. Also, the handling of logging differs between other scripts (using argparse, where we have default functions to handle the logger setup in bob.bore.log) and yours, where you set the verbosity by hand (and you actually use different stages than in bob.core.log).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: bob/bob.measure#20