CNVkit- weird results when using the same sample as normal
1
0
Entering edit mode
2.1 years ago
biobiu ▴ 120

Hi, I'm using CNVkit to detect copy number alterations in hybridized capture panel. When I've used the same sample (exactly the same bam) as a reference I somehow do find some CNA. We used the batch command followed by the call command with default parameters (and with dropping low-coverage). 15 out of the 75 segments were found to have copy-number alteration (cn!=2). The cnn files are exactly the same both for the on- and off-targets so the problem starts when creating the cnr. Any idea why this discrepancy happens?

cnv • 642 views
ADD COMMENT
1
Entering edit mode
2.1 years ago
Eric T. ★ 2.6k

Sorry, I'm not sure I follow. Could you paste both commands here so I can see the difference?

ADD COMMENT
0
Entering edit mode

Thanks for your reply, I'll clarify. There are no two commands, just a batch command of the same sample as test and normal sample:

cnvkit.py batch SAMPLE.bam -n SAMPLE.bam --targets TAR.bed --annotate refFlat.txt --fasta ~ucsc.hg19.fasta --access access-5k-mappable.hg19.bed --output-reference ref.cnn --output-dir --drop-low-coverage

and then: cnvkit.py call SAMPLE.cns

ADD REPLY
0
Entering edit mode

This is expected. CNVkit doesn't directly subtract the normal from the test sample; the normal sample is one of several factors that go into the final calls.

ADD REPLY

Login before adding your answer.

Traffic: 1270 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6