additional features

[mpetri]

Hey,

in my local fork of libcds I have some more features which I'm not sure are of interest as libcds2 is currently in development.

The features are:

• 64bit wavelet tree implementation (was able to create a wt over 15gb of text)
• build the wavelet tree level wise to save lots of space
• parallel wavelet tree construction (using pthreads)
• return the k most frequent items within a range.
• wt_coder_hutucker()
• faster BitSequenceRG based on http://sux.dsi.unimi.it/ (and take advantage of popcnt() cpu instruction if available)
• other minor fixes

should I push these features or should I wait for libcds2 to be in reasonable state?

-Matthias

[fclaude]

Hey,

thanks a lot for the contributions!! All the features you mention
sound great and I'm quite excited to see them. If you want you can
push them into libcds (only problem is that I changed the layout of
the project some minutes ago :-( ... ). Anyways, libcds2 should be on
a reasonable state in about a month, and you are more than welcome to
contribute in whatever you would like to :-).

Cheers,
Francisco.

On Wed, Aug 17, 2011 at 9:59 PM, mpetri
reply@reply.github.com
wrote:

Hey,

in my local fork of libcds I have some more features which I'm not sure are of interest as libcds2 is currently in development.

The features are:

• 64bit wavelet tree implementation (was able to create a wt over 15gb of text)
• build the wavelet tree level wise to save lots of space
• parallel wavelet tree construction (using pthreads)
• return the k most frequent items within a range.
• wt_coder_hutucker()
• faster BitSequenceRG based on http://sux.dsi.unimi.it/ (and take advantage of popcnt() cpu instruction if available)
• other minor fixes

should I push these features or should I wait for libcds2 to be in reasonable state?

-Matthias

Reply to this email directly or view it on GitHub:
#6