search for: unserialise

...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 it to > create the correct Weight object (broadly similar to how unserialise() > is handled). Hi Olly -- the following piece of tested code in omega/weight.cc hopefully achieves what we intend to do. It works fine for all tests. Please let me know what you think. if (startswith(scheme, "pl2")) { const char *p = scheme.c_str() + 3; if (*p == '\...

...amplar" 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 it to > > create the correct Weight object (broadly similar to how unserialise() > > is handled). > > If I followed correctly, since the set_weighting_scheme method in > omega/weight.cc already does exactly that, do you suggest adding a > parse_params method in each weighting scheme class to create the specific > object? -- in which case the set_weightin...

Hi, I have added support for Piv normalization in Tf-Idf weighting scheme as a intermediate step to implementing the support for Piv+ normalization. All tests pass. But I'm running into some issues with Piv+ normalization. In the Piv+ formula , there are two parameters (s and delta) that control the weight assigned. I think the way I'm serialising and unserialising these parameters has

...g in the > right header file (it's in common/serialise-double.h I believe). Thanks, fixed those errors. > I can't tell for sure without seeing the diff. You may mean just > `ptr++`? But it could be something else, depending on what you're > trying to do. I'm trying to unserialise normalization strings (e.g. "nfn", "nbsl" etc.) along with the new double parameters (s and delta) but it isn't turning out to be smooth because there's no method for unserialising strings in serialise-double.h Although, doing just const string normals = ptr++; or, co...

On Mon, Apr 10, 2017 at 11:47:36PM +0530, Vivek Pal wrote: > > No, use Xapian::Registry to find the weighting scheme from the name > > like how Weight::unserialise() does (otherwise every caller would need > > code similar to that above). > > Okay, I looked into Xapian::Registry and it seems you are referring to using > the get_weighting_scheme method? (which expects a string e.g. "bm25" i.e. the > name of a weighting scheme.) Ye...

...ry 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 it to create the correct Weight object (broadly similar to how unserialise() is handled). Then we can document the available schemes and the parameters they take in one place and refer to that from omega, quest and the evaluation module. Cheers, Olly

...On Fri, Jul 29, 2016 at 12:35:57AM +0530, Vivek Pal wrote: > > > > I can't tell for sure without seeing the diff. You may mean just > > > `ptr++`? But it could be something else, depending on what you're > > > trying to do. > > > > I'm trying to unserialise normalization strings (e.g. "nfn", "nbsl" > etc.) > > along with the new double parameters (s and delta) but > > it isn't turning out to be smooth because there's no method for > > unserialising strings in serialise-double.h > > Serialising it...

Hi all, We've struck a problem when using remote queries and hoping someone can offer some guidance. I haven't managed to get a C++ reproduction in the test suite, but I have got a demo that fails using Python: import xapian db = xapian.remote_open('localhost', 8100) qp = xapian.QueryParser() qp.set_database(db) query = qp.parse_query('test') enq =

Hi, Do the serialise method of Document and Query produce a valid utf8 string? My problem is with the Node.JS binding. I serialise an object, convert the string to a javascript string, convert the javascript string to a std string and then try to unserialise. The error I get from Xapian is "Bad encoded length: no data". Thanks, Marius -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20120806/6ab5880f/attachment.html>

Ok, but suppose I have a complex query, something like "(a OR b) AND NOT c OR ##". Do I have to parse the query by myself? > Date: Mon, 4 May 2015 03:03:24 +0100 > From: olly at survex.com > To: lautaromedrano at hotmail.com > CC: xapian-discuss at lists.xapian.org > Subject: Re: [Xapian-discuss] Make Xapian accept all characters > > On Sun, May 03, 2015 at

> 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

.../root/pwlib/lib/libpt_linux_x86_r.so: undefined reference to `PVideoInputDevice::GetDeviceNames() const' /root/pwlib/lib/libpt_linux_x86_r.so: undefined reference to `PVideoOutputDevicePPM::Open(PString const&, int)' /root/pwlib/lib/libpt_linux_x86_r.so: undefined reference to `PObject::UnSerialise(PUnSerialiser&)' /root/pwlib/lib/libpt_linux_x86_r.so: undefined reference to `PQoS::bestEffortDSCP' /root/pwlib/lib/libpt_linux_x86_r.so: undefined reference to `PVideoOutputDeviceNULL::Open(PString const&, int)' /root/pwlib/lib/libpt_linux_x86_r.so: undefined reference to `PVi...

...single create call to RouteController. When I call Route.from_xml(xmlString) it is not returning an object - it''s leaving the object (@route) nil, but not erroring. Any ideas? Here''s some code: RoutesController: def create @route = nil; if params[:requestXML] # unserialise from XML using ROXML @route = Route.from_xml(params[:requestXML]); else @route = Route.new(params[:route]) end respond_to do |format| #The following line unsurprisingly fails, as @route is nil if @route.save flash[:notice] = ''Route was succ...

...erl_grok_hex 0.03% /mnt/btr/public libpthread-2.28.so [.] __pthread_getspecific 0.03% /mnt/btr/public perl [.] Perl_pp_uc 0.03% perl perl [.] Perl_runops_standard 0.03% script/public-i libxapian.so.30.8.0 [.] Glass::RootInfo::unserialise 0.03% /mnt/btr/public perl [.] Perl_ck_length 0.03% script/public-i HiRes.so [.] XS_Time__HiRes_clock_gettime 0.03% script/public-i perl [.] stadtx_hash_with_state.constprop.7 0.03% script/public-i libsqlite3.so.0.8.6 [.] 0x00...

Going back to the "prioritizing aggregated DBs" thread from February 2020, I've got 390 Xapian shards for 130 public inboxes I want to search against(*). There's more on the horizon (we're expecting tens of thousands of public inboxes). After bumping RLIMIT_NOFILE and running ->add_database a bunch, the actual queries seem to be taking ~30s (not good :x). Now I'm