-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
lmrescore failure and missing Gr.fst when run the training/run.sh #1668
Comments
bad option
You run mkgraph_lookahead.sh script to make dynamic graph instead of static
It is ok, you can copy existing one
Accurate model requires a lot of training data, not sure how much did you use and what language was it |
hi, @nshmyrev , thanks for the quick response, but I get stucked in a cuda mismatch problem when I tried to install kaldi. I tried either 'main' or 'vosk' branches in Cuda compilation tools, release 12.6, V12.6.68 It crashes in makefiles setup all the time, while the latest official kaldi would pass, so this stands in the way of me taking the steps you suggested above. |
Hm, something with new cuda. I need to update the codebase then. |
Hi, dear authors,
I followed the training recipe in the vosk-api/training folder, I did get a trained model, but the performance is not so good.
Also I found the following errors and some mismatch in model structures from the pretrained models. I wondered if there is something I did wrong.
I used the recent official kaldi repo and installed it with cuda on successfully.
in the decode stage, steps/lmrescore_const_arpa.sh would fail, and here is the log(maybe there needs to be a specfic version of kaldi?) But there is a WER result at last. I guess just the rescored version failed.
I intended to get a model structure similar to "vosk-model-en-us-0.22-lgraph", but there is some difference. this is my exp/chain/tdnn folder.
So could you help with this? Am I missing some steps in training or there is some twist I should do after training?
Many thanks~
The text was updated successfully, but these errors were encountered: