CNV not called in some samples
Dear GATK Team,
- 1_CNV_Somatic_Panel (v.1.3.1)
- 2_CNV_Somatic_Pair (v.1.3.0)
- num_changepoints_penalty_factor 5
- kernel_variance_allele_fraction 0.8
- kernel_variance_copy_ratio 0.8
Sample 1:
chrX position1 position2 427 -26.224015 -
Sample 2:
chrX position1 position2 427 -26.003399 0
Best,
-
Have you had a chance to look at these docs: https://gatk.broadinstitute.org/hc/en-us/articles/360035531092--How-to-part-I-Sensitively-detect-copy-ratio-alterations-and-allelic-segments
-
Dear Bhanu Gandham,
Thank you for your reply! Yes, we have read through the tutorial docs and found them very helpful, but were still unsure of why a CNV might be called significant in one sample and not in another when both had the same mean log2 copy ratio. We wondered if it had to do with the variance of the segments immediately around the CNV in question, but aren't sure how the tool calculates whether a CNV is significant.
We also did note that the allelic segmentation is known to be less reliable when running with case-only samples, but it seemed like the document stopped short of saying that they shouldn't be used in case only studies. Does allelic segmentation add information in case-only calling, or should we be performing only copy-ratio segmentation?
Best,
Kate
-
Hi Kate,
I am checking with the team and will get back to you shortly.
-
Hi Kate,
- The first thing to try is to look at the documentation for
CallCopyRatioSegments
https://gatk.broadinstitute.org/hc/en-us/articles/360041850791-CallCopyRatioSegments and see if changing threshold parameters fixes things. - If not we would probably need to see more data, including plots and full modeled segments output and called segment outputs.
- Regarding the other question you asked: "doing copy-ratio + allelic segmentation improves the segmentation over just using the copy ratios (even in case only), but the allelic data is otherwise not used in CallCopyRatioSegments"
- The first thing to try is to look at the documentation for
Please sign in to leave a comment.
4 comments