search for: scheme

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...

On Sun, Apr 09, 2017 at 11:34:07PM +0530, Vivek Pal wrote: > > 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(&...

On Sat, Apr 08, 2017 at 09:11:22PM +0100, James Aylett wrote: > On 8 Apr 2017, at 19:15, Vivek Pal <vivekpal.dtu at gmail.com> wrote: > > >> and the details of which weighting schemes were available in which version > >> isn't a key part of the $set command itself. > > > > Do you suggest dropping that piece of information out? Since the reason behind > > adding that is unclear to me so I'm not entirely sure if it would be a good > > ide...

...everyone, I am thinking of working on the following ideas for my GSOC proposal based on my discussions with Olly and my own understanding. Rather than focusing on an entire perftest module, I have decided to focus on implementing performance tests for weighting schemes based on a wikipedia dump and in addition to that, build a framework to measure the accuracy and relevance of new and old weighting schemes. * Measuring the relevance and accuracy of weighting schemes.* - The accuracy of a weighting scheme can be measured by using the concepts of precisio...

I have seen a couple of posts about color schemes like those at the ColorBrewer site. Most recently: http://geography.uoregon.edu/datagraphics/color_scales.htm These color schemes can work very well for regions (bars, polygons, images, etc.) but are not very suitable for points and/or lines. Is anyone aware of research/suggestions for a color...

Hi, I am Abhishek Currently Xapian::Weight follows BM25 scheme, many models such as the Divergence from Randomness (DfR) family of models, Unigram Language Model and the Bi-gram Language Model implemented two years ago in GSoc 2012 yet not merged to the master. The new weighing schemes or improvement in implementing the previous models to change the default s...

The initial authors of R said?, "...we implemented the language by first writing an interpreter for a Scheme subset and then progressively mutating it to resemble S." Further on in that article they elaborated that their strategy was to create a parser that would take expressions in S-like syntax and translate them to Scheme S-expressions. Does R still work that way? Can R be made to accept Scheme...

Hi, I want to add a new password hashing scheme as plugin and provide it for the dovecot project, so that it will be included as optional plugin in future releases. Yet the plugin compiles fine and the .so file gets created. My approach is to call the functions password_scheme_register() and password_scheme_unregister() (src/auth/password-sche...

...? ?paste(x, y, z, sep="", collapse=",") > > is analogous to > > ? ?sum(x + y + z) > > > Honestly, I'd be significantly more comfortable?if > > 1:10?+ integer(0)?+ 5 > > were an error too. This is actually the recycling scheme used by mapply(): > mapply(function(x, y, z) c(x, y, z), 1:10, integer(0), 5) Error in mapply(FUN = FUN, ...) : zero-length inputs cannot be mixed with those of non-zero length AFAIK base R uses 3 different recycling schemes for n-ary operations: (1) The recycling scheme used by ar...

2016-07-31 16:39 GMT+02:00 <aki.tuomi at dovecot.fi>: > > > On July 27, 2016 at 2:08 AM Andreas Meyer <luckyfellow42 at gmail.com> > wrote: > > > > > > Hi, > > > > > > I want to add a new password hashing scheme as plugin and provide it for > > the dovecot project, so that it will be included as optional plugin in > > future releases. > > > > Yet the plugin compiles fine and the .so file gets created. > > > > My approach is to call the functions password_scheme_register(...

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New umb-scheme packages are available. Advisory ID: RHSA-2000:047-03 Issue date: 2000-08-07 Updated on: 2000-08-07 Product: Red Hat Linux Keywords: N/A Cross references: N/A --------------------------------------------------------------------- 1. Topic: New umb-scheme pac...

Beyond the general work on compiz-scheme (new wrappings, hooks, code improvements, etc), I've added a few large new things: 1. Key bindings with modifiers. This lets you from any of your scheme files/interactive prompt bind an arbitrary key + modifier to an arbitrary scheme function. So you can define new Compiz behaviors and shortcu...

> 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 documentation should also be updated to point to the weighting scheme section in the getting started guide ($set command to be specific if I'm not...

...gt; > > > > > > > On July 27, 2016 at 2:08 AM Andreas Meyer <luckyfellow42 at gmail.com> > > > wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > I want to add a new password hashing scheme as plugin and provide it for > > > > the dovecot project, so that it will be included as optional plugin in > > > > future releases. > > > > > > > > Yet the plugin compiles fine and the .so file gets created. > > > > > > > > My...

Hi all, Is there a way to get dovecot to recognize arbitrary password hash schemes when looking up a password in a database? I originally set up with #default_pass_scheme = MD5, and I would like to migrate to SHA512. Seeing as the scheme is actually stored in the password column along with the password in the format $_<scheme#>_$_<salt>_$_<passwordhash>_, it...

Hi, guys I am Wenjin from Graduate School of Chinese Academy of Science, pursing a master degree and my current research interests including using Data mining and Information retrieve technology to analysis software engineering (SE) data and support SE. I have great interested in "Weight Schemes" project. and in the last few days I have learnt some detail about DFR model family by reading some papers and web page. I find that Terrier Project (http://terrier.org/) has implement most of DFR scheme in Java language, and briefly read related source of Terrier's package( org.terrier...

Hello guys.I have sent a pull request for the code and tests of the Tf-Idf weighting scheme. Please do let me know if any changes are required.Meanwhile,Ill begin working on implementing normalizations which require additional statistics and on the DFR schemes. https://github.com/xapian/xapian/pull/6 On Tue, Feb 26, 2013 at 5:30 PM, <xapian-devel-request at lists.xapian.org>wrote:...

...for me to encrypt and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The idea is that users supply an already-encrypted password. Most of the users can fetch their login password from /etc/shadow on their own computer. Wiki page http://wiki.dovecot.org/Authentication/PasswordSchemes indicates that scheme name CRYPT is the one that uses the libc crypt() function. But it also says it uses no more than 8 characters. Then there is MD5-CRYPT. But that doesn't call crypt(), I presume. No limit on password size is indicated. But this at least looks like SOME of the encrypted...

Hello, attached is an hg export on top of the current dovecot-2.2 branch, which adds support for a SCRAM-SHA-1 password scheme. Ideally I'd want doveadm pw's rounds flag to apply to this, but that's currently specific to the crypt password scheme, so I left it out for now. Regards, Florian Zeitz -------------- next part -------------- # HG changeset patch # User Florian Zeitz <florob at babelmonkeys.de>...

...9;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 of which weighting schemes were available in which version > isn't a key part of the $set command itself. Do you suggest dropping that piece of information out? Since the reason behind adding that is unclear to me so I'm not entirely sure if it would be a good idea. Thanks, Vivek