Open ngoel17 opened 9 years ago
If unthreaded is used, this issue does not happen.
yes i'm also getting the same, but it throw some warnings
WARNING (LatticeWordAligner():word-align-lattice.cc:263) [Lattice has input epsilons and/or is not input-deterministic (in Mohri sense)]-- i.e. lattice is not deterministic. Word-alignment may be slow and-or blow up in memory. WARNING (OutputArcForce():word-align-lattice.cc:567) Invalid word at end of lattice [partial lattice, forced out?]
I came across a possible solution for this issue.
The old socket-based recognition server in the Kaldi trunk runs DeterminizeLatticePruned
before getting a word alignment:
Adding that to my fork of this repository got rid of the warning.
@maxhawkins Can you recommend where to add DeterminizeLatticePruned to this repo? Thanks in advance.
I think it should go here, right before WordAlignLattice
Thanks!
Sometimes (not always) when using threaded decoder, and creating both word and phone alignments, word alignment is not created although phone alignment is created. The plugin does not crash or create a warning in the logs for this issue.