summaryrefslogtreecommitdiff
path: root/graehl
diff options
context:
space:
mode:
authorgraehl <graehl@ec762483-ff6d-05da-a07a-a48fb63a330f>2010-09-23 00:10:52 +0000
committergraehl <graehl@ec762483-ff6d-05da-a07a-a48fb63a330f>2010-09-23 00:10:52 +0000
commitf8915e0bd1627167b72ca350b82ad31f8cb1fdeb (patch)
treee7ca29aa771db26630cc02f2bd61c2441c475f38 /graehl
parent46c1d1c56535cdaf71e920b12f1cbdcbd1bd9d4f (diff)
pausing earley best-first fsa work
git-svn-id: https://ws10smt.googlecode.com/svn/trunk@656 ec762483-ff6d-05da-a07a-a48fb63a330f
Diffstat (limited to 'graehl')
-rwxr-xr-xgraehl/NOTES.earley4
1 files changed, 4 insertions, 0 deletions
diff --git a/graehl/NOTES.earley b/graehl/NOTES.earley
index 4156063a..0953708c 100755
--- a/graehl/NOTES.earley
+++ b/graehl/NOTES.earley
@@ -105,3 +105,7 @@ vs.
3) * -> x . *
with 3, we predict all sorts of useless items - that won't give us our goal A and may not partcipate in any parse. this is not a good option at all.
+
+======
+
+-LM forest may have many in-edges per V. (many rules per NT lhs). so instead of generating all successors for scan/predict, i wanted to have them in sorted (admissable) -LM cost order and postpone once the prefix+rule part is more expensive than something else in the agenda. question: how many such postponed successor things