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

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

The script `bob_compute_perf.py` command line interface could be improved

Created by: anjos

As it is today, this script requires 2 score sets for running (dev and test).

It is possible to compute the performance using a single set.

Here are some suggestions for improvements:

  1. Make the dev score set an argument instead of an option. It is strange conceptually to have obligatory "options"
  2. Make the test score set an optional argument (this implies in allowing the analysis to run if only dev is provided
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#16