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

acoustic-sclae option in kaldi decoder #6

Open
armusc opened this issue Nov 2, 2023 · 1 comment
Open

acoustic-sclae option in kaldi decoder #6

armusc opened this issue Nov 2, 2023 · 1 comment

Comments

@armusc
Copy link

armusc commented Nov 2, 2023

Hi

is there a specific reason why the acoustic-scale option from kaldi decode-faster has not been exported as well?
using kaldi decoding with icefall models allows to use some desirable properties like fst memory mapping with const fst but I have not been able to get same performance (in terms of WER) than icefall 1 best decoding (I observe higher deletion, for example)
in icefall playing with the hlg-scale option seems to make same difference (like 10% relative from 0.2 to 0.8, for example) and I was wondering if I could observe the same difference by playing with the acoustic-scale option with kaldi decoder, but it is absent (it looks to me they are supposed to both play on the relative weight of graph and model scores during best path computation, isn't it?)
I actually commented here
k2-fsa/icefall#1287 (comment)
but exporting a lattice decoder seems way more complicated, if possible at all

@FredSRichardson
Copy link

I wanted to second this. It can also be really useful to add a "length penalty" (actually a bonus when you have high deletion rates). Some decoders add costs for "space" any maybe word insertions as well. I don't know if these can all be thrown into the FST without violating "ring" constraints.

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