search for: parse_params

...t; Each scheme already has a human-readable name, and Xapian::Registry > > 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). > > 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...

...I wonder if you meant the same method? That's the default implementation - each subclass overrides that with an actual implementation (at least if it wants to work with remote databases). > > The code in omega would just be: > > > > enq.set_weighting_scheme(Xapian::Weight::parse_params(scheme)); > > I wonder if we could do something more like: > > enq.set_weighting_scheme(Xapian::Registry::get_weighting_scheme(name).parse_params(params)); > > where, Xapian::Registry::get_weighting_scheme(name) returns a weighting scheme > object e.g. BM25Weight object and...

> Each scheme already has a human-readable name, and Xapian::Registry > 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). 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...

...ight belong in the API instead. Each scheme already has a human-readable name, and Xapian::Registry 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

> 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

On Thu, Sep 3, 2015 at 6:45 PM, Kostya Serebryany <kcc at google.com> wrote: > Did you build the Postgres code with -fsanitize-coverage=... ? Yes: CC = clang CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -g -O0 -fsanitize=address

I'm almost certain I installed Wine correctly, but when I try to get a Windows program working it doesn't happen. The program I'm trying to install is Arena 10 (a simulation program). I've attached some screen shots. The first one is when I completed the wine install, 2 through 6 show when I tried to install the program. If you could tell me what steps to take to fix these

Looks correct. Can you post the output of libFuzzer here? Something like #0 READ cov: 0 bits: 0 units: 97701 exec/s: 0 #1 pulse cov: 732 bits: 0 units: 97701 exec/s: 0 #2 pulse cov: 737 bits: 0 units: 97701 exec/s: 1 #4 pulse cov: 858 bits: 0 units: 97701 exec/s: 2 #8 pulse cov: 880 bits: 0 units: 97701 exec/s: 4 On Thu, Sep 3, 2015 at 10:50 AM, Greg Stark

This patch series introduces the tapback daemon, the user space daemon that acts as a device''s back-end, essentially most of blkback in user space. The daemon is responsible for coordinating the front-end and tapdisk. It creates tapdisk process as needed, instructs them to connect to/disconnect from the shared ring, and manages the state of the back-end. The shared ring between the

Hello all, I was trying to install Wine on my MacBook via the Terminal. These are my system specs: odel Name: MacBook Model Identifier: MacBook2,1 Processor Name: Intel Core 2 Duo Processor Speed: 2 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache (per processor): 4 MB Memory: 1 GB Bus Speed: 667 MHz Boot ROM Version: MB21.00A5.B07 SMC Version: 1.13f3 Serial Number: BLAHBLABLAH