Unhammer: Created page with "==Alternate implementation methods== Trimming while reading the XML file might have lower memory usage (who knows, untested), but seems like more work, since pardefs are read ..."

2014-02-11T08:36:27Z

Created page with "==Alternate implementation methods== Trimming while reading the XML file might have lower memory usage (who knows, untested), but seems like more work, since pardefs are read ..."

New page

==Alternate implementation methods==
Trimming while reading the XML file might have lower memory usage (who knows, untested), but seems like more work, since pardefs are read and turned into FST's before we get to an "initial" state and then attached at the end of regular entries.

[[Image:Product-automaton-intersection.png|thumb|400px|right|product automaton for intersection]]
The '''product automaton''' for intersection, marks as final only state-pairs where both parts of the state-pair are final in the original automata. Minimisation removes unreachable state-pairs. However, this quickly blows up in memory usage since it creates ''all'' possible state pairs first (cartesian product), not just the useful ones.

https://github.com/unhammer/lttoolbox/branches has some experiments, see e.g. branches product-intersection and df-intersection (the latter is the currently used implementation)

<br clear="all" />

Talk:Lt-trim - Revision history

Unhammer: Created page with "==Alternate implementation methods== Trimming while reading the XML file might have lower memory usage (who knows, untested), but seems like more work, since pardefs are read ..."