Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.bio.base bob.bio.base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.bio.basebob.bio.base
  • Issues
  • #160

Databases with mutiple file extension (e.g. FRGC).

Hello, In the current CSV-based implementation of database wrappers, we specify the extension of the files to load as an argument of the sample loader.

This poses problem for example in the particular case of bob.bio.face.database.FRGC which has some images stored as .JPG while some others are stored as .jpg. Currently trying to load the latter ones raises an error, as the loader looks only for a .JPG extensions.

I think the most straightforward fix would be for the sample loader to accept a list of valid extensions and try all of them at loading time. What do you think ?

Also, I wonder if this type of situation is very niche (i.e. I will implement a custom sample loader just for FRGC), or if it would make sense to update the default CSVToSampleLoaderBiometrics to generally handle this type of case ?

Another case were it could be useful is to implement some cross-database evaluation protocols (e.g. samples from database A as models and samples from database B as probes), where we could have different extensions as well. I had to do this kind of evaluation in the past when comparing FFHQ against Syn-Multi-PIE.

ping @tiago.pereira

Edited Aug 11, 2021 by Laurent COLBOIS
Assignee
Assign to
Time tracking