search for: featuremanag

...would look something like this: > > * instead of Features, which is really a namespace implemented as a > class, we separate out the calculation of the different features > into distinct subclasses of Feature, whose only job is to calculate > a single feature. Currently the FeatureManager calls these (via > FeatureManager::Internal::transform) with the correct arguments, > things like document statistics or tf or idf caches. This is > analogous to how Weight objects can request various statistics, and > the Enquire process then makes them available. So we c...

On Thu, Dec 04, 2014 at 08:28:32PM -0500, Manu Gupta wrote: > I was trying to build Han's code and was stuck here. It seems to me that > his code is trying to generate pdf for them. > > Is it possible to modify the make files to stop building the documentation. You can run the top-level configure with --disable-documentation. Cheers, Olly

As Olly has already pointed out the 2012 branch is not merged. I think there are some compilation errors in the branch. The code in branch is better refactored. The Ranker and FeatureManager classes are well defined and implemented. Parth. On Wed, Sep 25, 2013 at 9:02 AM, Olly Betts <olly at survex.com> wrote: > On Tue, Sep 24, 2013 at 08:34:10PM +0800, jiangwen jiang wrote: > > There's xapian-letor folder in current master trunk, is this code merged > in &g...

...cursive] Error 1 > make[2]: Leaving directory `/home/manugupt1/han/xapian/xapian-letor' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/home/manugupt1/han/xapian/xapian-letor' > > > and gsoc2014-evaluation branch has: > > emanager.cc -fPIC -DPIC -o .libs/featuremanager.o > featuremanager.cc:89:1: error: unused parameter 'did1' > [-Werror=unused-parameter] > cc1plus: all warnings being treated as errors > make[3]: *** [featuremanager.lo] Error 1 > make[3]: Leaving directory `/home/manugupt1/han/xapian/xapian-letor' > make[2]: *** [a...

...his own feature calculation class and call letor module to use it. I just think it?s not that convenient to extend features. In GSoC 2014, I also need to implement a feature selection algorithm so this part I think it?s kind of important, I mean the extensibility of features. 6. For FeatureManager, it will set the context for feature calculation, like set Database, set query and what kinds of features we want. It provides some basic information like term frequency and inverse document frequency etc. Also it will have function update_mset to touch feature information to MSet....

Hello everyone, I have completed introducing some code from v-hasu's branch into mine, mainly for Features, FeatureVector and FeatureManager classes. I have pushed the changes to https://github.com/ayshtmr/xapian/tree/letor-update. I am now proceeding to write unit tests for feature modules. There are a few things that I wanted to clarify: 1. I have introduced a lot of code in a single commit ( https://github.com/ayshtmr/xapian/comm...

...few things that I plan to do in coming few days: 1. Revise the timeline. There are some portions that I had kept for the first and second week of coding which have already been done (except writing tests). So, I'd like to adjust the timeline according to it. 2. Ensuring that features (mainly FeatureManager, FeatureVector and Features classes) are stable and no code is left that is to be introduced from v-hasu's branch into mine. Once done, proceed to write tests for this portion. 3. Discussion about which dataset to use. Regards, Ayush -------------- next part -------------- An HTML attachmen...

HI, Parth: Thanks for your reply. There's xapian-letor folder in current master trunk, is this code merged in 2011? the letor code of 2012 is not merged to the trunk? Regards 2013/9/23 Parth Gupta <pargup8 at gmail.com> > Dear Jiangwen Jiang, > > The current state of the project can be reached from the repo: > http://trac.xapian.org/wiki/GSoC2012/LTR > > I would