-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Javascript FST results are different from the plain FST results #144
Comments
Current test web page is here: https://wincentbalin.github.io/BabyFST |
@mhulden, is it possible to debug a (rather large) FST state-by-state using for example |
The error was on my side: The output of
with Because of different outputs I will not close this issue. |
Note that there is a bug in |
Dear @dhdaines, I have seen your solution already, and I will test it in a couple of days. |
When testing the FST in the file
babyfst-2020.foma
from the repository https://github.com/asahala/BabyFST the suggested test casesreturn when running
flookup babyfst-2020.foma < input.txt
Instead, after converting the file
babyfst-2020.foma
to Javascript using commandpython3 ./foma2js.py -n BabyFST babyfst-2020.fomabin > babyfst.js
and creating a web page withbabyfst.js
andfoma_apply_down.js
, runningfoma_apply_down(BabyFST, 'iddin')
results in an empty array.A file converted using the original Perl script
foma2js.perl
yielded the same result.The text was updated successfully, but these errors were encountered: