kaldi-lstm

by dophist

dophist / kaldi-lstm

C++ implementation of LSTM (Long Short Term Memory), in Kaldi's nnet1 framework. Used for automatic...

197 Stars 104 Forks Last release: Not found 74 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

LSTM-projected BPTT in Kaldi nnet1

Diagram

Diagram

Notes:

  • peephole connection(purple) are diagonal
  • output-gate peephole is not recursive
  • dashed arrows: adaptive weight, i.e activations of (input gate, forget gate, output gate)

Currently implementation includes two versions: * standard * google

Go to sub-directory to get more details.

FAQ

Q1. How to decode with LSTM?

  • Standard version: exactly the same as DNN, feed LSTM nnet into nnet-forward as AM scorer, remember nnet-forward doesn't have a mechanism to delay target, so "time-shift" component is needed to do this.
  • Google version:
    • convert binary nnet into text format via nnet-copy, and open text nnet with your text editor
    • change "Transmit" component to "TimeShift", keep your setup consistent with "--targets-delay" used in nnet-train-lstm-streams
    • edit "LstmProjectedStreams" to "LstmProjected", remove "NumStream" tag, now the "google version" is converted to "standard version", and you can perform AM scoring via nnet-forward, e.g:
       40 40  5
       512 40  800 [ ...
       16624 512  1  1  0  [ ...
       16624 16624
      
      

Q2. How do I stack more than one layer of LSTM?

In google's paper, two layers of medium-sized LSTM is the best setup to beat DNN on WER. You can do this by text level editing: * use some of your training data to train one layer LSTM nnet * convert it into text format with nnet-copy with "--binary=false" * insert a pre-initialized LSTM component text between softmax and your pretrained LSTM, and you can feed all your training data to the stacked LSTM, e.g:

 40 40
 512 40  800  4  [ ...
 512 512  800  4  [ ...
 16624 512  1  1  0  [ ...
 16624 16624

Q3. How do I know when to use "Transmit" or "TimeShift"?

The key is how you apply "target-delay".
* standard version: the nnet should be trained with "TimeShift" because default nnet1 training tool (nnet-train-frame-shuf & nnet-train-perutt) doesn't provide target delay. * google version: due to the complexity of multi-stream training, the training tool "nnet-train-lstm-streams" provides an option "--target-delay", so in multi-stream training, a dummy "Transmit" component is used for a trivial reason related to how nnet1 calls Backpropagate(). But in testing time, the google version is first converted to standard version, so the "transmit" should also be switched to "TimeShift" during the conversion.

Q4. Why are the "dropout" codes commented out?

I implemented the "forward-connection droping out" according another paper from google, but later I didn't implement dropout retention, so the effects of dropout are not tested at all, and I leave it commented out.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.