summaryrefslogtreecommitdiff
path: root/decoder/hg.cc
diff options
context:
space:
mode:
authorgraehl <graehl@ec762483-ff6d-05da-a07a-a48fb63a330f>2010-07-05 18:53:00 +0000
committergraehl <graehl@ec762483-ff6d-05da-a07a-a48fb63a330f>2010-07-05 18:53:00 +0000
commit4955a3d76a535fad2a3f9e504f2eeeefc0a266fd (patch)
tree66fa07cf018d36e0a8745568488a4025c8961684 /decoder/hg.cc
parent36778292e0e98d9b5307a38104f1e99aad7c3aa4 (diff)
comment unused var names, todo
git-svn-id: https://ws10smt.googlecode.com/svn/trunk@133 ec762483-ff6d-05da-a07a-a48fb63a330f
Diffstat (limited to 'decoder/hg.cc')
-rw-r--r--decoder/hg.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/decoder/hg.cc b/decoder/hg.cc
index e57f7807..70511c07 100644
--- a/decoder/hg.cc
+++ b/decoder/hg.cc
@@ -1,4 +1,4 @@
-//TODO: lazily generate feature vectors for hyperarcs (because some of them will be pruned). this means 1) storing ref to rule for those features 2) providing ff interface for regenerating its feature vector from hyperedge+states and probably 3) still caching feat. vect on hyperedge once it's been generated. ff would normally just contribute its weighted score and result state, not component features.
+//TODO: lazily generate feature vectors for hyperarcs (because some of them will be pruned). this means 1) storing ref to rule for those features 2) providing ff interface for regenerating its feature vector from hyperedge+states and probably 3) still caching feat. vect on hyperedge once it's been generated. ff would normally just contribute its weighted score and result state, not component features. however, the hypergraph drops the state used by ffs after rescoring is done, so recomputation would have to start at the leaves and work bottom up. question: which takes more space, feature id+value, or state?
#include "hg.h"