Tom, I made those changes.
Now, instead of editing kMaxOrder in max_order.hh, there is a new flag to pass to bjam at compile time, --max-kenlm-order. So to set this value to 12, do the following: ./bjam --max-kenlm-order=12 I added max_order.cc in order to quickly determine, at runtime, what value was specified for --max-kenlm-order at compile time. This file compiles into bin/kenlm_max_order. Running this will tell you the value passed at compile time. For example, if you compile with 12 as shown above: $ bin/kenlm_max_order KenLM was compiled with a maximum n-gram order set to 12. Cheers, Lane On Fri, Aug 10, 2012 at 7:25 AM, Tom Hoar <[email protected]> wrote: > Ken, > > I see that a recent update removed max_order.hh and adds a new max_order.cc. > > I was editing the kMaxOrder value in max_order.hh and running language > models as high as 12 grams. Do I need to do anything with the new versions > to support higher kMaxOrder values? > > Tom > > > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support > -- When a place gets crowded enough to require ID's, social collapse is not far away. It is time to go elsewhere. The best thing about space travel is that it made it possible to go elsewhere. -- R.A. Heinlein, "Time Enough For Love" _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
