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

nnet3 acoustic model score fusion #2451

Open
hhadian opened this issue May 25, 2018 · 3 comments
Open

nnet3 acoustic model score fusion #2451

hhadian opened this issue May 25, 2018 · 3 comments
Labels
stale Stale bot on the loose

Comments

@hhadian
Copy link
Contributor

hhadian commented May 25, 2018

I was thinking that it could be useful to have support for system combination at nnet output level. For e.g. we can use this feature to combine 2 chain models (e.g. TDNN-F and TDNN-LSTM) which use the same tree for combined decoding. Currently, it seems that there are no scripts/binaries for this.

One way to do this is to use the existing class DecodableSum() or something like that to write a new decoder.

Another possibility is to create a neural net that outputs the
average of the outputs of 2 nnets.
It would be possible by renaming the 2 inputs to have different
suffixes, and then messing with the input and output nodes. That would
allow us to use the same decoding code.

Anyone interested?

@teinhonglo
Copy link
Contributor

Hi
I am interested in how to implement on nnet3.
Do you have any progress in score fusion?

Tien Hong

@kkm000
Copy link
Contributor

kkm000 commented Apr 8, 2019

I'm wondering (just thinking aloud) what prevents someone from assembling a single network from two models. Outputs should be trivial to sum. May be more efficient to compute at runtime, and would use the existing nnet3 computation mechanics to consume just the right amount of the (combied, longest) left/right context for each internal subnetwork. Looped decode would trivially work for TDNN too, so no special decoder needed.

@stale
Copy link

stale bot commented Jun 19, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale bot on the loose label Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale bot on the loose
Projects
None yet
Development

No branches or pull requests

3 participants