snowfall icon indicating copy to clipboard operation
snowfall copied to clipboard

issues/doubts about the current L.fst

Open csukuangfj opened this issue 4 years ago • 6 comments

Some issues and doubts about the current method to generate L.fst:

  • ~Since there is no G, do we still need the disambiguation symbols?~

  • What is the purpose of adding optional silence at the end of each word? Only OOV words are mapped to the silence phone SIL and I am afraid there is not enough training data for SIL.

  • ~There is no blank symbol at all. Why is it not used? It is common to add a blank symbol to the topology in the literature, I think.~

  • No test code.

csukuangfj avatar Dec 18 '20 07:12 csukuangfj

RE 1 and 3.

  • We use L.fst for training, there's no diambig symbols in it.
  • we add self-loops (blank) in training and decoding.

qindazhu avatar Dec 18 '20 07:12 qindazhu

And another issue:

  • Any reason to NOT change the topology to support repeated symbols?

csukuangfj avatar Dec 18 '20 07:12 csukuangfj

  • For the optional silence, we'll have to see if it's helpful in any scenario. I think once we start using LF_MMI as part of the objective function it will become useful.
  • RE changing the topology to support repeated symbols, there isn't a particular reason, you could go ahead and try it.

danpovey avatar Dec 18 '20 09:12 danpovey

thanks, will try it.

csukuangfj avatar Dec 18 '20 09:12 csukuangfj

I am pretty sure that the disambiguation symbols in the phone symbol table are also present in the acoustic model output layer, as my changes didn't address that yet. I am not sure if them being present in the phone symbol table means that they are also present in L.

pzelasko avatar Dec 18 '20 14:12 pzelasko

In graph.py this line LG.labels[LG.labels >= labels_disambig_id_start] = 0 takes care of it.

danpovey avatar Dec 18 '20 15:12 danpovey