speed up flagging with ItervalTree
keiranmraine opened this issue · comments
Keiran Raine commented
Most of the flagging code is looking for simple "hit" lookups in tabix files. This can be handled in exactly the same way as the input generation speed up.
Will have additional advantages as current code wraps each query with an eval
which is expensive:
cgpPindel/perl/lib/Sanger/CGP/PindelPostProcessing/FragmentFilterRules.pm
Lines 339 to 349 in da79133
Should be able to hide this in the reuse_unmatched_normals_tabix
and reuse_repeats_tabix
functions. Needs to be applied in both FilterRules.pm
and FragmentFilterRules.pm
.