Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.kaldi bob.kaldi
  • 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.kaldibob.kaldi
  • Issues
  • #2
Closed
Open
Issue created Apr 19, 2017 by Milos CERNAK@milos.cernakMaintainer

Kaldi metadata

Kaldi requires metadata to run advanced algorithms. The metadata consists of several text file lists, such as the list of train/test/dev utterances (sorted key utterance pairs), speaker to utterance file spk2utt (speaker utterances lists) and utterance to speaker file utt2spk (utterance speakers lists). The idea is to add this metadata to prospective databases that could be used with Kaldi, such as AMI, NIST and so far.

Assignee
Assign to
Time tracking