Skip to content
Prev 5929 / 21312 Next

[Bioc-devel] GIntervalTree objects are corrupted during save/load

On 07/01/2014 10:38 AM, Michael Lawrence wrote:
I see. That makes things a little bit more complicated. I wonder if the
whole effort is worth it given that serialization of a GIntervalTree
doesn't seem like a common use case and that re-processing the
GIntervalTree from the GRanges object maybe doesn't take that much
time (I didn't do any timings to back this up though). For PDict
objects it was nice to be able to serialize them even though it's
probably not something the user should do. Turning a DNAStringSet
object into a PDict object is very fast and the resulting object is
so big that a save/load cycle would actually take much longer than
re-processing the PDict object at each new session.

Also my feeling that the time and effort required to break from the Kent
would perhaps be better spent trying to implement something new like the
Nested Containment List algo. Since this would probably have to be
implemented from scratch anyway then it would make sense to use
SEXP-based memory, or even better, to put a thin abstract layer between
the algo itself and memory management so they are decoupled.

Cheers,
H.