Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.db.xm2vts bob.db.xm2vts
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • 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.db.xm2vtsbob.db.xm2vts
  • Issues
  • #1
Closed
Open
Issue created Sep 20, 2012 by André Anjos@andre.anjos💬Owner

Data organization

Created by: laurentes

There are two distinct problems:

  1. The current API only allows the user to deal with still images of the database.
  2. The current API assumes that the data of the database is stored in subdirectories, one for each identity. It would be better to organize data in the same way as it is currently shipped when you order the database.

To solve both problems, this would require me to have the original CDs/DVDs of the database or at least to know the directory structure and the files contained in each subdirectory. Unfortunately, this is not the case, as the data we have at Idiap have very likely been reorganized over the years.

Could anyone provides me the file hierarchy for both image and/or audio data, in order to fix this issue? Thanks in advance.

Assignee
Assign to
Time tracking