> One thing I’m not clear on is how to expand the ranges from one step
> to the next. The way GenomicInteractions are structured, there is a
> Granges object with all possible ranges, and the GInteractions object
> is populated by reference to said interactions.
If you're already in C++, then
Thank you for the tip, Aaron! I’m working on the sorting step right now.
One thing I’m not clear on is how to expand the ranges from one step to the
next. The way GenomicInteractions are structured, there is a Granges object
with all possible ranges, and the GInteractions object is populated
Hi Luke,
I also don’t see the visual representation. It sounds like you want to
summarise over disjoint boxes in the interaction heat map. It also sounds like
your strategy is to use quad-trees, truncated at a certain depth with all the
children accumulated to that depth. If so then what
Note that your visual won't show up for many (all?) of us. Nonetheless,
I think I know what you want to do.
Your task does not lend itself to vectorization, which makes it
difficult to write efficient R code. It's not impossible, but it would
be quite hard to read and debug, and your maintenance
Hello. I am planning to develop a new package which extends the
GenomicInteractions package. I would like some help/advice on implementing the
following functionality.
Consider the follow GenomicInteractions object
GenomicInteractions object with 10 interactions and 1 metadata column:
