![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
DESeq2 Anomaly/Issue? | The_Corsair | Bioinformatics | 7 | 03-02-2015 07:07 PM |
Newbie Question: Calculating physical coverage from genome coverage | tristanstoeber | Illumina/Solexa | 4 | 06-24-2013 11:53 AM |
TruSeq lib prep anomaly | barturas | General | 0 | 02-19-2013 12:47 PM |
Solexa anomaly.txt for structual variants | bioinfosm | Bioinformatics | 1 | 01-09-2009 02:58 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Junior Member
Location: Latvia Join Date: Oct 2011
Posts: 6
|
![]()
Hello,
I am doing exome sequencing of non-malignant tumors on Ion Proton PI chip. Sequencing works fine, but when analysed BAM with Qualimap 2.0.2, I received strange picture of coverage: ![]() and ![]() while coverage of exome sequencing of leukocyte derived DNA is more even (except X): ![]() Interesting that when analysing more closely there is high similarity between the tumor sample coverage - hills and valleys follow the same pattern across all samples (currently 3). My aim is to find exome mutations that differ between tumor samples and blood (obviously). When analysed further tens of thousands SNVs are found different between blood derived DNA and tumor although literature suggests about 100-to 200 for this type of tumor. Has anyone seen such pictures before? Are they normal? Can it be corrected and how? Thanks in advance! |
![]() |
![]() |
![]() |
Tags |
coverage anomaly, exome, proton, tumor |
Thread Tools | |
|
|