That sounds good.<br><br>Parth.<br><br><div class="gmail_quote">On Mon, Mar 25, 2013 at 8:17 PM, Mudit Gupta <span dir="ltr"><<a href="mailto:mudit.raaj.gupta@gmail.com" target="_blank">mudit.raaj.gupta@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Guys,<br><br>Thank you for your time and input.<br><br>I just saw the updated description of the project. It seems that the GSoC work can be divided into thee major part. Firstly, writing API for the Xapian Letor module. Then, writing a Test suite for Xapian-Letor. Finally, try to incorporate 1-2 feature selection algorithms. I think it would also be useful if 1-2 detailed examples of API usage are incorporated in the project. <br>
<br>I will fork Rishab's branch and try to play with the code. I will go through resources about feature selection algorithm and update on the mailing list. I haven't looked into Rishab's code in detail, but I am guessing it might need some more refactoring. Also, I will share the API design. <br>
<div class="im HOEnZb">
<br>Best Regards,<br><br>Mudit Raj Gupta<br><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_quote">On Mon, Mar 25, 2013 at 5:20 PM, Parth Gupta <span dir="ltr"><<a href="mailto:pargup8@gmail.com" target="_blank">pargup8@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mudit,<br><br>As Olly has pointed out, this year we are not planning to build up more or on new ranking algorithms. Rather, we will consolidate the project with the present ranking algorithms. Rather it would be interesting to incorporate some/one feature selection algorithms. See the Learning to Rank updated project description on ideas pages.<br>
<br>If you are interested in working on this project, it would be great start to fork Rishabh's branch and debug the code. That would give you much more insight of the project and help you better formulate your application.<br>
<br>Regards,<br>Parth.<br><br><div class="gmail_quote"><div><div>On Fri, Mar 22, 2013 at 6:37 AM, Olly Betts <span dir="ltr"><<a href="mailto:olly@survex.com" target="_blank">olly@survex.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div>On Thu, Mar 21, 2013 at 06:58:41PM +0530, Mudit Gupta wrote:<br>
> I am interested in "Learning To Rank" project. If I am not wrong, I found<br>
> the framework incorporated by Parth in the cloned code. It needed some<br>
> refactoring in order to incorporate more algorithms and was done by Rishabh<br>
> and available in his git repo (<a href="https://github.com/rishabhmehrotra/xapian" target="_blank">https://github.com/rishabhmehrotra/xapian</a>)<br>
> but is still not merged. So, I assume I should think of additions to the<br>
> code in Rishbh's repo.<br>
<br>
</div>Yes, I think that's the best starting point.<br>
<div><br>
> Moreover, I noticed that SVM-rank, ListMLE and<br>
> ListNet is already present in the code. I am interested in addition of a<br>
> random forest approach and looking for appropriate libraries. I would be<br>
> great to get input by the Xapian community in terms of preference of<br>
> algorithms and open source libraries. It would also be great to know the<br>
> priority of the Letor project to the Xapian community.<br>
<br>
</div>Parth and I talked this over recently, and we concluded that this year a<br>
major focus should be on consolidating the existing work. That doesn't<br>
necessarily mean that new features can't be looked at, but one of the<br>
deliverables should really be a xapian-letor module which we're happy to<br>
tag as a stable release. A project which adds more algorithms is<br>
interesting, but if the end result isn't useful to Xapian users, there's<br>
much less benefit to be had from it.<br>
<br>
One of the major things missing is a testsuite. Without any automated<br>
tests, it's hard to have much confidence that the code works, and it<br>
makes it much harder to make changes to the code in the future without<br>
introducing new bugs. So I think adding a testsuite is important.<br>
The harness from xapian-core is suitable, but testcases need writing,<br>
and the bugs that actually writing testcases will inevitably uncover<br>
need fixing.<br>
<br>
We should also look at what features are missing from xapian-core<br>
which would be useful for xapian-letor, and consider implementing them -<br>
especially if they have other potential uses. Two that I'm aware of<br>
are:<br>
<br>
* Fundamentally, xapian-letor wants to take a Xapian::MSet object and<br>
reorder it, so an API which allows that would be handy - then the<br>
output of xapian-letor can be an Xapian::MSet object, allowing it to<br>
be cleanly slotted into existing applications using the Xapian API.<br>
An MSet reordering API also has other potential uses - for example,<br>
clustering results.<br>
<br>
* Field-related features currently have to be calculated specially by<br>
xapian-letor, but these would also be useful to have for other uses<br>
(e.g. implementing BM25f) so tracking them in the database backend<br>
in xapian-core is worth investigating.<br>
<br>
I'll update the entry on the project ideas page with the above shortly.<br>
<br>
Cheers,<br>
Olly<br>
<br></div></div>
_______________________________________________<br>
Xapian-devel mailing list<br>
<a href="mailto:Xapian-devel@lists.xapian.org" target="_blank">Xapian-devel@lists.xapian.org</a><br>
<a href="http://lists.xapian.org/mailman/listinfo/xapian-devel" target="_blank">http://lists.xapian.org/mailman/listinfo/xapian-devel</a><br>
</blockquote></div><br>
</blockquote></div><br>
</div></div></blockquote></div><br>