124085,124093,"deletion",9,55142239,55156999,"chr7","chrchr7:55142239-55156999",26.5,4474,17460,3.9
124085,124113,"duplication",20,55142239,55201432,"chr7","chrchr7:55142239-55201432",57.8,12671,45280,3.57
124085,124126,"deletion",13,55142239,55366179,"chr7","chrchr7:55142239-55366179",115,20719,81052,3.91
124085,124134,"duplication",8,55142239,55431346,"chr7","chrchr7:55142239-55431346",85.4,23742,90328,3.8
124085,124136,"deletion",2,55142239,55433799,"chr7","chrchr7:55142239-55433799",132,25303,97612,3.86
124085,124187,"duplication",51,55142239,55795890,"chr7","chrchr7:55142239-55795890",178,45707,146585,3.21
Hi
I just noticed an issue where regions with more reads than expected are being called as deletions (reads.ratio >> 1). In the example there's also an issue with overlapping regions being called as both deletions and duplications. Anyone have any ideas on what might be happening here?
Best regards
-Harald