similar to: Letor: returning MSet after re-ranking

Displaying 20 results from an estimated 1000 matches similar to: "Letor: returning MSet after re-ranking"

2016 Jul 31
2
Letor: returning MSet after re-ranking
On Sun, Jul 31, 2016 at 12:44:16AM +0100, Olly Betts wrote: > Would a method which swapped two elements of an MSet provide what you > need? That would provide a more generic way to adjust the ranking of > an MSet which for example could be used to implement a diversification > feature or something like SQL "GROUP BY". Isn't the most common use going to be that the
2016 Jun 29
2
xapian-letor: FeatureVector discussion
> > > > The approach I was thinking 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 >
2018 Feb 25
3
GSOC 2018: Diversification of Search Results
Hello, I am Uppinder Chugh (irc nick: icebyte), a senior year undergraduate student majoring in Computer Science and Engineering at Indian Institute of Technology, Guwahati. I'm interested to work on the idea of adding the functionality of search result diversification to Xapian. After having brief conversations with mentors on IRC, I would like to compile the discussions and further discuss
2014 May 21
2
Some questions about Letor project
Hi all, Thank you for giving me the opportunity to work with Xapian :) I am Jiarong Wei, a third year undergraduate student in Zhejiang University, China. In GSoC 2014, I will work on Letor module with Hanxiao Sun. Here are some questions I encountered these days, 1. In letor.cc, we have two parts of functions: the training part and the ranking part. I?ll use SVMRanker as an example. The
2023 Aug 18
1
does Xapian::Enquire hold an MVCC revision?
On Thu, Aug 17, 2023 at 09:28:26PM +0000, Eric Wong wrote: > In other words, is it possible to avoid duplicates if new > documents are inserted into the DB by another process in-between > ->get_mset calls when reusing Xapian::Enquire objects? The Database object itself effectively does (it works in a snapshot of the state of the database when you open it, or last called reopen() which
2023 Aug 17
1
does Xapian::Enquire hold an MVCC revision?
In other words, is it possible to avoid duplicates if new documents are inserted into the DB by another process in-between ->get_mset calls when reusing Xapian::Enquire objects? I do some expensive processing on each mset window, so I always limit the results to limit heap usage even if I'm planning on going through a big chunk of the DB: $mset = $enq->get_mset(0, 1000);
2018 Apr 27
3
GSOC 2018: Diversification of Search Results
We are equally excited about working with you over summer. I think you missed reply by Olly on IRC, you can find it in logs here: https://botbot.me/freenode/xapian/2018-04-24/?msg=99336093&page=1 - olly icebyte[m]: i think that probably needs to go through SFC ( https://sfconservancy.org/) as the "legal entity" - 2:05 am
2023 Aug 28
1
DatabaseModifiedError while iterating on mset
Olly Betts <olly at survex.com> wrote: > On Wed, Aug 23, 2023 at 01:53:27PM +0000, Eric Wong wrote: > > I'm already retrying the ->get_mset operations; but now I'm > > wondering where I'd hit DatabaseModifiedErrors while inside a > > Xapian::MSetIterator loop. > > > > I assume ->get_document is a place where it gets thrown; > > but
2016 Mar 20
2
GSoC 2016 Letor Stabilisation
Hello, I'm Ayush from New Delhi, India. I am interested in Letor Stabilisation project for GSoC. I have a good background in machine learning. Sorry for getting in so late, university exams were holding me back. I'll try to cover as much as I can in the coming week. I am following the plan of attack suggested on the project page. Following are the things that I have completed: 1.
2014 Aug 07
2
Global number of matches
Hi, is there a way to get the number of all possible matches for a specific query? Some api call like Xapian::doccount Xapian::Enquire::get_number_of_matches(); Best wishes Wilm
2017 Mar 21
2
GSoC 2017: Letor Click Data Mining
Hi Olly. Thanks for your reply to the previous email. To have an appropriate subject I've started this new thread for further discussions. > There's a $log{} command available in Omega templates. We can't log from > the result page template, as the clicks happen after that is used, but we > could make result links redirect via a second Omega template which does > the
2009 Jan 27
1
Segmentation fault in MSetIterator get_weight
Hi, I'm using xapian with c# and mono and i'm having a segfault in get_weight. When i print the index variable, the value is clearly too high. I think something write over it. Do you have any idea on how i could trace the beginning of the segmentation fault ? Thanks, -- Yann
2012 Jul 27
1
A Little Help
Hi Rishabh, I think its better not to expose RankiList to Letor.h and make it better user friendly. So my suggestion is to convert RankList to the following statement in this method. std::map<Xapian::docid, double> letor_score(const Xapian::MSet & mset); So just convert the RankList in std::map<Xapian::docid, double> format in the methods where you need to return. Parth. On
2016 Mar 08
2
Error while building from git - xapian-letor
Hi all, While building from git with xapian-letor not ignored in bootstrap, I am getting the following make error: In function `main': /home/ayush/Desktop/xapian/xapian-letor/bin/xapian-letor-update.cc:98: undefined reference to `Xapian::Internal::str(unsigned int)' /home/ayush/Desktop/xapian/xapian-letor/bin/xapian-letor-update.cc:99: undefined reference to
2014 Mar 10
2
A few more question about LETOR
1.Could you explain why are these libraries included in all the xapian-letor headers? #include<xapian/intrusive_ptr.h> #include<xapian/types.h> #include<xapian/visibility.h> Or just provide me with the documentation of these header. I looked into these header files but couldn't anything substantial. 2.
2013 Jul 03
2
Potential memory leak when assigning MSetItem values
I've traced a memory leak to a statement which assigns the values from an MSetItem to a dictionary which is then appended to a list in python. We're running python 2.7.3, xapian-core 1.2.15 and xapian-bindings 1.2.15. I've provided an example which reproduces the behavior below. The example prints the PID and has a few statements waiting for input to make observing the behavior easier.
2023 Aug 27
1
DatabaseModifiedError while iterating on mset
On Wed, Aug 23, 2023 at 01:53:27PM +0000, Eric Wong wrote: > I'm already retrying the ->get_mset operations; but now I'm > wondering where I'd hit DatabaseModifiedErrors while inside a > Xapian::MSetIterator loop. > > I assume ->get_document is a place where it gets thrown; > but once a document is retrieved, can iterating through > terms in one document
2016 May 14
2
GSoC 2016 Letor dataset discussion
Hello, I wanted to decide the dataset that should be used for Letor stabilisation project. I think 2009 INEX Wikipedia Collection <http://www.mpi-inf.mpg.de/departments/databases-and-information-systems/software/inex/> should work fine. It's a collection of 2,666,190 XML articles, 115 topics <http://inex.mmci.uni-saarland.de/protected/adhoc/2009-topics.zip>, 50,275 qrel
2016 Jun 27
2
xapian-letor: FeatureVector discussion
Hello James, Parth, Following our discussion on IRC and on code review, the way FeatureVector class works needs some discussion. Presently, the FeatureVector class is defined as follows, with a fixed number of feature count (19): class FeatureVector::Internal : public Xapian::Internal::intrusive_base{ friend class FeatureVector; double label; double score;
2016 Aug 08
2
Letor: Feature sub-classes question
Hello James, I am working on breaking down Features into sub-classes. Should each of the features get their own sub-class, or should the grouping be done according to type? i.e. query-document pair dependent, query-dependent and document dependent sub-classes. Using this approach makes more sense if we plan to add support for user to include query-dependent and document-dependent features in