Paul Dixon - 2013-12-15

Probably the quickest is to use ArcMap from arc-map.h to convert the
StdFst.
Although having two conversions is a bit ugly.

VectorFst<LogArc> ofst;
ArcMap(t_std, &ofst, WeightConvertMapper<StdArc, LogArc="">());

On 15 December 2013 15:47, Ondrej Platek oplatek@users.sf.net wrote:

Hi,

I want to have converted fst::VectorFst<fst::StdArc>
from kaldi::ConvertLattice :StdArc> where shortest paths
on fst and lattice are the same.
I have one example lattice where the shortest paths are different.

The conversion was done by following snippet:

kaldi::Lattice lat; // the lattice was filled somehowfst::VectorFst<fst::StdArc> t_std;ConvertLattice(lat, &t_std); // kaldi shortest path on lat and fst shortest path on t_std give// two different best paths

Is it expected behaviour? Do I need to modify the Lattice (to have certain
properties)
in order to ConvertLattice will keep the same path after conversion?

Thanks in advance

Ondra

PS: In fact, I need to convert Lattice to fst::VectorFst<fst::LogArc>
and keep the shortest path the same. Any advice for that?
(I do not want the fst in tropical semiring as in the snippet above.)
PS2: If you are interested I can somewhere upload the lattice. It is quite
small.


kaldi::ConvertLattice from Lattice to fst::VectorFst<fst::StdArc> does not
hold shortest path propertyhttps://sourceforge.net/p/kaldi/discussion/1355348/thread/52795975/?limit=25#e8ac


Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/kaldi/discussion/1355348/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/