Hi Michael,
On 12/13/2013 06:39 PM, Michael Lawrence wrote:
Coercion might suffice. I do remember Patrick optimizing these
selections with e.g. memcpy(), so they are pretty fast.
The memcpy() trick was used (and is still used in extractROWS) when
seqselect'ing by a Ranges object. For subsettin
Coercion might suffice. I do remember Patrick optimizing these selections
with e.g. memcpy(), so they are pretty fast. No profiling data though. I do
have some performance critical code that has relied on the Rle-based
extraction. Would be nice to avoid re-evaluating the performance.
On Fri, Dec
On 12/13/2013 01:49 PM, Michael Lawrence wrote:
Thanks, makes sense. Didn't realize we could dispatch on the 'i'
parameter. I sort of recall the perception that we couldn't, and that
was one of the main motivations behind seqselect. But it does appear
possible.
Well I was hoping I could do this
Thanks, makes sense. Didn't realize we could dispatch on the 'i' parameter.
I sort of recall the perception that we couldn't, and that was one of the
main motivations behind seqselect. But it does appear possible.
Michael
On Fri, Dec 13, 2013 at 1:10 PM, Hervé Pagès wrote:
> Hi Michael,
>
>
>
Hi Michael,
On 12/13/2013 01:03 PM, Michael Lawrence wrote:
I used to use seqselect for subsetting ordinary R vectors by Ranges and
Rle. IRanges:::extractROWS does this, but it's hidden behind the namespace.
What is the public way of doing this?
Maybe we just need to export extractROWS()? Or so
I used to use seqselect for subsetting ordinary R vectors by Ranges and
Rle. IRanges:::extractROWS does this, but it's hidden behind the namespace.
What is the public way of doing this?
Maybe we just need to export extractROWS()? Or something with a better name?
Michael
[[alternative HTM
