similar to: Implementation of substring search in omegascript

Hello :-) We have Xapian and Omega working nicely. Now we would like more functionality at the browser UI, such as being able to specify date ranges and being able to search the file name including looking only for, say, .odt files. Question is whether the best choice for this would be to develop a template using OmegaScript or to switch to C++ or some other language. Availability of skills

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

Hello everyone, My name is Ayush Tomar. I'll be working on Learning to Rank stabilisation project over the summers. Here are a 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.

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

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.

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

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

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

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

> Hi, Vivek — there isn't any particular reason that I'm aware of. It's > probably worth pointing (in the omegascript documentation) to the part of > the getting started guide which talks about the different weighting schemes If there isn't any reason then I'd like to send in a patch adding support for those weighting schemes in weight.cc and I agree omegascript

Folks, Is it possible to query a document value (doc.set_value(i, val)) as part of the Omega query. I know how to do it from code. Is there a query markup to use for Omega? ...Thanks, ...Ken

I've been inspired to look at the R source code by some strange timing results that I wrote about on my blog at radfordneal.wordpress.com (see the posts on "Speeding up parentheses..." and "Two surprising things...". I discovered that the strange speed advantage of curly brackets over parentheses is partially explained by an inefficiency in the evalList and

> It may be worth splitting that part of the $set documentation out into its > own section somehow, because it's getting a bit long - Undoubtedly; $set command has the longest section on the documentation page :) But it would be hard splitting that up because the documentation is organised in a way that each command is really contained in its own specific section. > and the details

Hello devs! Could you please expand on the project idea of integration of xapian in a framework with an example. I did not fully understand the requirements of this project. Also I want to discuss an idea of my own. Xapian doesn't have an auto complete feature. It is quite common for an search engine to have an auto complete feature. What I propose is a API that is totally separate from

> The log command will be executed wherever it is in the template. > By "current system user", what do you mean? There'll need to be > write permission for the CGI process, which is probably the same > identity as the web server process. I basically changed the ownership of the /var/log/omega directory to the current user using: sudo chown `whoami` /var/log/omega But I

On Fri, Apr 08, 2016 at 09:57:16AM -0400, Richhiey Thomas wrote: > Sorry to take so much time on this. Was down with coursework because the > semester end is nearing. Not a problem -- that sort of thing is affecting a lot of people at the moment! > I used the latest development version which is 1.3.5 for this patch. > I have implemented the $match function and it works fine when I

> > I'm not clear on what the OFFSET really represents. Could you > > please explain a bit? > > Omega paginates results (as does Xapian's MSet, internally). So if > you're displaying the second page of results, you'll need to know > that when building training data. It's affected by TOPDOC and also > by the <>[# CGI variables, but internally to

Hi James, > ID: some identifier for each query > QUERY: text of the query (when the query is run) > URLs: every URL displayed (or alternatively, the Xapian docid — this > might be easier) > OFFSET: otherwise you'll have difficulty coping with result pages other > than the first page (when this happens, the query ID should probably > remain the same, and when you aggregate

On Mar 29, 2016 4:49 PM, "Olly Betts" <olly at survex.com> wrote: > > On Tue, Mar 29, 2016 at 11:41:02AM +0100, James Aylett wrote: > > It's probably helpful to create a ticket and claim it (and update the > > project ideas list to link to it), so other people don't try to work > > on it as well. (I have a feeling that it might have been among the

Hi, I have submitted a draft proposal on the GSoC website but I also wanted to share my draft proposal through Dropbox to get your feedback quickly through it. Please review it and let me know your feedbacks as soon as possible. I haven't written much about automated testing as I haven't written any test yet ( I will learn writing automated tests before April end ). Link to my