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

Closed
Open
Opened Oct 28, 2016 by Manuel Günther@mguenther0 of 3 tasks completed0/3 tasks
  • Report abuse
  • New issue
Report abuse New issue

Four and Five column format must be specified by the user, although it could be automatically estimated

So far, the user has two different functions to load/process score files, depending on the format. On the other hand, @amohammadi has implemented a way of automatically estimating the score file format: https://gitlab.idiap.ch/bob/bob.measure/blob/master/bob/measure/load.py#L315, so that the user does not need to specify the format anymore. I think, we should provide generic functions for similar tasks, too, i.e., having:

  • bob.measure.load.scores(filename, ncolumns=None)
  • bob.measure.load.split(filename, ncolumns=None)
  • bob.measure.load.cmc(filename, ncolumns=None)

These functions should use the same way of handling ncolumns=None.

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#21