Gene coverage issue in HG38
Hi, Recently I checked the coverage of gene OCA2, using both genome HG37 and hg38.
surprisingly, it was not not covered (very poorly mapped) in HG38, and full covered with good coverage in hg19 with all used capture kit.
we are not able to identify the problem, because for both of the genome we used GATK 4.3.0.0 with updated BWA-MEM aligner.
Suggestion welcome.
• 881 views
•
link
written
by
rajesh.msch •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
gatk LiftoverVCF finishes with no output VCF nor error.
written by jpablo •
-
GATK BaseRecalibrator error: input files reference and features have incompatible contigs
written by ben.ponv •
-
Big differences between two alignment tools outputs: BWA vs NanoPipe
written by alexandru.bologa.marian •
-
CollectHsMetrics per_base_coverage results quirk
written by a.j.wilson0000 •
-
BWA alignment score override
written by chase.rushton •
-
calling the variants in a sample with respect to other sample
written by AshishKS •
-
Lack of consensus between NGS & Sanger sequencing on indels/mutations
written by alons
-
DNA-seq PE150 BWA alignment
written by zhuozhu132 •
-
What Agilent Interval Files (.Bed) Should I Use For Exome Variant Calling With Gatk?
written by newDNASeqer
-
Multiplex In Exome Seq And "Customized/Capture" Seq Kits
written by CrazyB
I think there is a typo in your question. You can that it was not covered in HG38, but was covered in hg38. Presumably you mean one of these to be hg37?