OpenFst Extensions

The following extensions to OpenFst are available. These are built only if the configure flags are provided as below. Also provided are the include files and the libraries to be used in client code.

Compact FSTs

configure include lib
--enable-compact-fsts <fst/compact-fst.h> fst/libfstcompact.{a,so}

Compact FSTs use space-efficient representations of specialized FSTs such as acceptors, strings or unweighted FSTS. This extension has libraries that register CompactFst for uint8, uint16, and uint64 representable total arcs. CompactFst for uint32 is registered in libfst.{a,so}. See here for more details, including how to load dynamically.

Const FSTs

configure include lib
--enable-const-fsts <fst/const-fst.h> fst/libfstconst.{a,so}

A ConstFst is a general-purpose immutable FST. This extension has libraries that register ConstFst for uint8, uint16, and uint64 representable total arcs. ConstFst for uint32 is registered in libfst.{a,so}. See here for more details, including how to load dynamically.

FST Archives (FARs)

configure include lib
--enable-far <fst/extensions/far/farlib.h> fst/libfstfar.{a,so}

A finite-state archive (FAR) is used to store an indexable collection of FSTs in a single file. Utilities are provided to create FARs from FSTs, to iterate over FARs, and to extract specific FSTs from FARs. See the source code for additional information.

Look-Ahead FSTs

A look-ahead FST is an immutable FST that has a lookahead matcher, selected for more efficient composition in a particular application. When used in composition, no special options need to be passed; the appropriate matcher and filter are selected automatically. This extension has libraries that register label and transition lookahead FSTs. See here for more details, including how to load dynamically.

configure include lib
--enable-lookahead-fsts <fst/matcher-fst.h> fst/libfstlookahead.{a,so}

Push-down Transducers (PDTs)

configure include
--enable-pdt <fst/extensions/pdt/pdtlib.h>

This is an experimental push-down transducer (PDT) library. A PDT is encoded as an FST, where some transitions are labeled with open or close parentheses. To be interpreted as a PDT, the parentheses must balance on a path. See the header files for additional information.

Topic revision: r6 - 01 Feb 2011 - 23:00:27 - MichaelRiley
 
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback