Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.sp bob.sp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.spbob.sp
  • Issues
  • #1
Closed
Open
Issue created Aug 18, 2015 by André Anjos@andre.anjos💬Owner

bob.sp.Quantization has weird border handling

Created by: tiagofrepereira2012

Copying the issue from here (https://github.com/idiap/bob/issues/184)

##################### By chance, I had a look at the bob.sp.Quantization class. It seems that this class has several issues, especially in border cases:

  1. the call function returns 0 in two cases: when the element is in the first range, or when the element is below the lowest threshold
  2. the call function returns the highest index in two cases: when the element is in the last range, or when the element is above the highest threshold

In fact, point (2) cannot even be distinguished in the C++ implementation of the function since the highest threshold in not even stored in the range of thresholds. Usually, when there are 4 ranges, it requires 5 thresholds, but this class holds only 4.

Assignee
Assign to
Time tracking