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

Improve TDP handling for RASR decoding #124

Open
christophmluscher opened this issue Apr 6, 2023 · 3 comments
Open

Improve TDP handling for RASR decoding #124

christophmluscher opened this issue Apr 6, 2023 · 3 comments
Assignees

Comments

@christophmluscher
Copy link
Contributor

christophmluscher commented Apr 6, 2023

It is true that for Viterbi alignment and decoding we generally use the non-normalized default tdp values, however, for full-sum training, we generally introduce normalized loop/forward values that might be even estimated from an alignment or defined based on aomse heuristics, e.g. average phoneme length. In addition to this class, we could also introduce an enum class for TdpType, out of default, heuristic, and alignment-based. For the two latter types one could also have jobs that estimate values from an alignment or from transcription. Daniel Mann has already such jobs.

Originally posted by @Marvin84 in #110 (comment)

@christophmluscher
Copy link
Contributor Author

just so we do not forget :)

@Marvin84
Copy link
Contributor

I think @DanEnergetics has jobs for estimation of tdp from both an alignment and from the transcription. Maybe we could integrate this into the tdp class?

@DanEnergetics
Copy link
Contributor

DanEnergetics commented Apr 11, 2023

A while back I found this job for estimating tdps from alignment. Maybe this can be used. I have not tested it though and perhaps it can use some updates.
I don't have an estimate-from-transcription procedure for tdps, only for the prior.

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

4 participants