Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mismatch features: 40 expected but 13 given #230

Open
chaoticz044 opened this issue Apr 23, 2020 · 1 comment
Open

Mismatch features: 40 expected but 13 given #230

chaoticz044 opened this issue Apr 23, 2020 · 1 comment

Comments

@chaoticz044
Copy link

Hi Devs,
I made an acoustic and language model using the scripts from steps and utils folder copied from wsj and used the nnet2 to train pnorm. I successfully made completed the training and decoding. I tried moving it to kaldi gstreamer but when I run the streaming decode result. I got logs from workers that feature dimensions are not the same. Expected is 40 but got 13. I used the same config in training locally. Do I need to convert the nnet2 model to online? If yes, how would I convert it and run it on gstreamer since I matched the configs in the yaml file and set the config files to the yaml file.

This is my yaml file:

use-nnet2: True
decoder:
    use-threaded-decoder: True
    nnet-mode: 2
    model : /opt/models/final.mdl
    word-syms : /opt/models/fst/words.txt
    fst : /opt/models/fst/HCLG.fst
    mfcc-config : /opt/models/mfcc.conf
    max-active: 7000
    beam: 25.0
    lattice-beam: 13.0
    acoustic-scale: 0.1
    do-endpointing : true
    endpoint.silence-phones: 1:2:3:4:5:6:7:8:9:10
    traceback-period-in-secs: 1.5
    chunk-length-in-secs: 0.1
    num-nbest: 3

    word-boundary-file: /opt/models/fst/word_boundary.int

out-dir: tmp

and my config file is:

--use-energy=false
--num-ceps=13

I already used the

steps/online/nnet2/prepare_online_decoding.sh

but not solved.

Please guide me on how to solve it. I used 13 mfcc and 3 steps/train_deltas.sh and lda.

Thanks a lot!

@svenha
Copy link

svenha commented Aug 14, 2020

Your mfcc.conf might be the problem. Do you have other files matching the pattern `mfcc*conf?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants