I did some CNV on a targeted sequencing run. I was provided with a panel that contained a "SNP-Backbone", meaning 2000 targets more or less evenly distributed over the genome. I did the calling using CNVKit and PureCN. One aspect of the calling process is the segmentation, where adjacent targets are merged into one segment. This can lead to the calling considering a region (segment) lost/deleted, even though it is only supported by two targets that are millions of base pairs away. In the image below, the "Panel" shows the location of the targets. The "CNV_Freq" shows a large deletion spanning the centromer, which doesn't really make sense, but its surrounding target regions are deleted, so it is deleted as well
I am aware, that there is no real reason around this issue, but would it make sense to filter, for example gene losses, based on distance to the next target? The further away, the less reliable?
I will admit, that the neighboring targets are rarely "volatile", with one going up and the other one down and then up again.