kaldi-asr / kaldi-asr/kaldi

kaldi [Lengths are /tmp/kaldi.ljtb/utts=4620 versus /tmp/kaldi.ljtb/utts.utt2dur=5607]

Open
#4,650 10 comments 0 reactions 0 assignees View on GitHub
bug stale
Dominant language
Shell
Stars
15.5k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

I have a big bug,can you help me?

local/timit_data_prep.sh: TIMIT data preparation succeeded
steps/make_mfcc.sh --cmd run.pl --nj 8 data/train exp/make_mfcc/train mfcc
steps/make_mfcc.sh: moving data/train/feats.scp to data/train/.backup
fix_data_dir.sh: no utterances remained: not proceeding further.
utils/validate_data_dir.sh: Error: in data/train, utterance-ids extracted from utt2spk and utt2dur file
utils/validate_data_dir.sh: differ, partial diff is:
--- /tmp/kaldi.ljtb/utts 2021-10-25 09:36:31.713458090 +0800
+++ /tmp/kaldi.ljtb/utts.utt2dur 2021-10-25 09:36:31.845456523 +0800
@@ -1,4620 +1,5607 @@
-SP0001W00
-SP0001W01
-SP0001W02
...
+SP0462W04-0000-0246
+SP0462W05-0000-0256
+SP0462W06-0000-0391
+SP0462W07-0000-0374
+SP0462W08-0013-0234
+SP0462W09-0000-0314
[Lengths are /tmp/kaldi.ljtb/utts=4620 versus /tmp/kaldi.ljtb/utts.utt2dur=5607]

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with local/timit_data_prep.sh, steps/make_mfcc.sh, and utils/validate_data_dir.sh, using the reported validation output as the first reproduction point. Trace why data/train produces different utterance-id sets in utt2spk and utt2dur; done means the TIMIT preparation and MFCC command complete without the validation error.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
data-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.