search for: lmweight

...not wrong) which I'll try to incorporate in the same PR. Additionally, omegascript documentation will also require updating to reflect support for newer weighting schemes in $set command. > It doesn't cover Dir+, but it does talk about BM25+ and PL2+. Actually, Dir+ is mentioned under LMWeight weighting scheme section in the last paragraph, although in brief. Thanks, Vivek

Hello everyone! I'm Ayush Tomar, junior undergrad in Computer Science from New Delhi, India. I love C++ coding and working on machine learning and information retrieval project. I was exploring the GSoC ideas for Xapian and the project on "Adding Weighting Schemes" looked really interesting to me. I wanted to work on text mining/IR this summer and this idea seems perfect! I have

On Sun, Apr 09, 2017 at 11:34:07PM +0530, Vivek Pal wrote: > > Each scheme already has a human-readable name, and Xapian::Registry > > can map that to an "examplar" object of the right type, so we > > could take a string like "bm25 1 0.8", see the first word is "bm25" > > and get a BM25Weight object, then call parse_params("1 0.8") on

...nd PL2: 0.0752646 Here, PL2+ indeed does a better job at retrieving relevant documents although by a small margin. I believe this should produce much better results at scale in practical use. At this point, we might want to consider replacing PL2 with PL2+ in Xapian to put it in practical use. 3. LMWeight_Dirplus: 0.100168 and LMWeight_Dir: 0.100168 These results are for LMWeight with smoothing Dir and Dirplus respectively. Interestingly identical results. Ideally, LMWeight_dirplus should perform better and I'm having similar thoughts for it as for BM25+ and BM25 results. Last addtion in weigh...

Hi, In my explorations of Omega codebase, I have found that Omega is currently missing support for newer weighting schemes added in 1.4.1 (BM25+, PL2+, Dir+). I'd submit a PR addressing that but as I think I might be missing something so just wanted to check if there's a particular reason for that? P.S. Finally back after a long week. Been eagerly waiting for a weekend since the

...ghting schemes would need to support being specified with no parameters - I guess there's probably always a sane default set of parameters. > Also, regarding Xapian::Weight::parse_params(scheme) -- I thought we were to > define parse_params method in each Weight subclass e.g. BM25Weight, LMWeight > etc.? Sorry, I was misusing that name for the static "dispatcher" method as well as the virtual method implementing the parameter parsing. > > There's probably a much better name than parse_params() though. > > Yes, I agree. May be get_parameterized_weighting_schem...

...nicode/.libs/utf8itor.o weight/.libs/bb2weight.o weight/.libs/bm25plusweight.o weight/.libs/bm25weight.o weight/.libs/boolweight.o weight/.libs/coordweight.o weight/.libs/dlhweight.o weight/.libs/dphweight.o weight/.libs/ifb2weight.o weight/.libs/ineb2weight.o weight/.libs/inl2weight.o weight/.libs/lmweight.o weight/.libs/pl2plusweight.o weight/.libs/pl2weight.o weight/.libs/tfidfweight.o weight/.libs/tradweight.o weight/.libs/weight.o weight/.libs/weightinternal.o -lrpcrt4 -lz -lws2_32 -LD:/bda-ci/msys2/unstable/mingw64/lib/gcc/x86_64-w64-mingw32/6.3.0 -LD:/bda-ci/msys2/unstable/mingw64/lib/gcc/x86...