Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • 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
  • Merge requests
  • !41

Fixed issue with FAR and FRR values being exactly 1 or 0, respectively

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Manuel Günther requested to merge far_1_fix into master Oct 16, 2017
  • Overview 1
  • Commits 1
  • Pipelines 1
  • Changes 1

I found a small bug when FAR=1 was used in far_threshold, and FRR=0 in frr_threshold. This resulted in a DIR plot that had a random last value (as it accessed memory at an uninitialized location).

This fixes it. There should be no implication for any other plot done so far.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: far_1_fix