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

Use Kaldi GrammarFST on the fly decoding #1

Open
mathquis opened this issue Jan 1, 2020 · 0 comments
Open

Use Kaldi GrammarFST on the fly decoding #1

mathquis opened this issue Jan 1, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@mathquis
Copy link

mathquis commented Jan 1, 2020

To avoid the language model being biased by unbalanced intents with multiple slots and help reduce Kaldi decoder resource usage, the implementation of Kaldi's GrammarFST approach seems like a good solution.
https://kaldi-asr.org/doc/grammar.html

Slots should be compiled as separate wFST and the intents are compiled as another wFST. Everything is stitched up at runtime by the Kaldi decoder so the resource usage is reduced (only the intents graph is loaded, the slots graphs are loaded on the fly).

Using this means that the weight of play music by (ARTIST) will be the same for any value in the artists slot and should greatly help avoiding incorrect graph paths due to 3-grams model issues.
See: synesthesiam/rhasspy#82

@koenvervloesem koenvervloesem added the enhancement New feature or request label Jan 3, 2020
@koenvervloesem koenvervloesem changed the title [Feature] Use Kaldi GrammarFST on the fly decoding Use Kaldi GrammarFST on the fly decoding Jan 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants