Panel Validation using NA12878 DNA
0
1
Entering edit mode
7.6 years ago
NielQC ▴ 10

Hi there,

we have made a panel that comprises several (190) exonic alterations and now we want to test how capable are we to call these variants starting from a DNA sample. This post is for retrieve suggestions about how can we do this and/or to know if my approach is not correct.

Basically what I have been thinking about is purchasing NA12878 DNA from Coriell Institute, sequencing it and running a variant calling pipeline (without going into details, mapping vs GRCh37 and call variants with mpileup). Once I have the variants, check them vs the high-confidence calls set focusing on my 190 exonic alterations and if the alleles matches at these positions would mean that we call these variants correctly.

Is this a correct way?

Previously, aiming to evaluate just the bioinformatic pipeline and not the laboratory part, I did the same analysis with the GIAB NA12878 dataset (HiSeq x300) and checked the output variants with this callset HG001_GRCh37_GIAB_highconf_CG-IllFB-IllGATKHC-Ion-10X-SOLID_CHROM1-X_v.3.3.2_highconf_PGandRTGphasetransfer.vcf available at the GIAB ftp site. Previously I normalized the variants representation of both calls sets using vcflib vcfallelicprimitives.

And a last question. For my validation purpose, is there any difference between purchasing the NIST reference DNA and purchasing the Coriell Institute DNA Sample? I think it's the same, but look the difference in prices...

Any suggestion will be welcome

panel validation NGS NA12878 GIAB • 3.4k views
ADD COMMENT
0
Entering edit mode

Hello NielQC!

It appears that your post has been cross-posted to another site: http://seqanswers.com/forums/showthread.php?t=75867

This is typically not recommended as it runs the risk of annoying people in both communities.

ADD REPLY

Login before adding your answer.

Traffic: 2413 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