25 April 2018

This first article on Whole Genome Sequence (WGS) analysis is posted today to celebrate DNA Day, 25 April 2018.

This is the first in a continuing series on the files received when a person's entire genome is sequenced, the contents of those files, the tools needed to access the file data, and some things a genealogist can do with the data.

I now have access to the WGS data for several people who have also tested at most of the genealogy companies offering DNA tests. I am excited to be able to analyze these files so others can decide if a WGS test may be right for them now that prices are below $1000 and probably going lower "soon." When ordering higher resolution sequencing that is consistent with medical testing the price may be over $1000.

The first WGS I have access to was done through YSEQ.net. This is the company of Thomas and Astrid Krahn who are well known in the genetic genealogy community. YSEQ.net has excellent explanations of the options and processes on their website and are very responsive to questions via Facebook and their online contact form.

offer 15x, 30x, and 50x options for coverage (30x coverage is generally the minimum used for medical purposes; the test taker wanted to be able to use this for health purposes and did not want to pay for additional sequencing later unless it becomes possible to phase data as it is sequenced)

provide privacy acceptable to the test taker (the outsourced sequencing does not have the test taker's name attached, the outsource sequencing company will not use the DNA data for other purposes, raw data is archived at YSEQ.net where German law prohibits the data being used without permission from the test taker)

A kit was ordered from YSEQ.net on 15 November 2017, four swabs arrived on 18 November 2017, the kit was returned on 20 November 2017, and received by the lab on 27 November 2017. Online mtDNA results were available 39 days later on 5 January 2018. Online WGS results were available 24 days after that on 29 January 2018. That is only about 73 days including mail time between the USA and Germany. The micro SD card was received later.

The files received consisted of

a text file with information on how to download the online DNA data, an mtDNA comparison to the rCRS, and Y chromosome analysis if the test taker is male

a text file with 23andMe V3-style data with about 958,000 lines that could be used with third-party DNA websites and tools; any test taker who has also tested at other testing companies can compare the two files to see if both companies found the same allele values at all locations

an mtDNA FASTA file (this is also a plain text file format); any test taker who has also tested the full mtDNA sequence can compare the two files to see if both companies found the same allele values at all locations

a very large Variant Call Format (VCF) file with a complete set of extracted mutations - about 695MB - readable with a text file reader such as NoteTab Pro, but may slow down your system due to the size; this has interesting information on the length of data read from the test taker's chromosomes and the mutations of this test taker (provided as a TBI and GZIP file which you must unzip)

a BAM and BAI (BAM Index) file with the WGS data - these will require special tools to view as the files are compressed (this will be covered more in a later post; BAM is a binary or compressed version of a SAM file; a SAM (Sequence Alignment Map) file is a text-based format for storing biological sequences aligned to a reference sequence; Samtools are available for LINUX systems at http://www.htslib.org/)

a BAM.stats and BAM.idxstats.tsv file - both readable in a plain text file reader; these are small - 450 to 5,000 lines - and can be read by any text file reader (stats is an abbreviation for statistics; idx is a common abbreviation for index in the computer world; TSV is a tab-separated-value file similar to the CSV comma-separated-values files we use all of the time in DNA analysis)

what seems to be the mtDNA data in a BAM file format along with a BAM index

Image by Debbie Parker Wayne

I am in the process of installing Samtools on my LINUX system so I can read the BAM files. I suspect many genealogists will not do this unless they have experience with LINUX/UNIX systems. There are some Windows/Mac-based genome analysis tools also.

Even without Samtools there is a lot of interesting information here to analyze in the coming months and compare to data from the genealogy testing companies. If you are interested in learning more about BAM files see Samtools and NCBI Genome Workbench.

All statements made in this blog are the opinion of the post author. This blog is not sponsored by any entity other than Debbie Parker Wayne nor is it supported through free or reduced price access to items discussed unless so indicated in the blog post. Hot links to other sites are provided as a courtesy to the reader and are not an endorsement of the other entities except as clearly stated in the narrative.
To cite this blog post:
Debbie Parker Wayne, "Whole Genome Sequence (Part 1)," Deb's Delvings, 25 April 2018 (http://debsdelvings.blogspot.com/ : accessed [date]).

No comments:

Post a Comment

Search This Blog

About Me

Debbie Parker Wayne, Certified Genealogist®

East Texas, USA

I am the owner of Wayne Research, a genealogical research service. Laws affecting family history and genetic genealogy (DNA) are areas of special interest to me. Many of my posts will be in those areas as well as topics of general interest to genealogists. Contact me through my Web site at debbiewayne.com.

Credentials

The words Certified Genealogist and letters CG are registered certification marks, and the designations CGL and Certified Genealogical Lecturer are service marks of the Board for Certification of Genealogists®, used under license by board certificants after periodic evaluation.

This blog stores no cookies other than those created by Google's blogspot.com service. By posting a comment, you agree that this website can store and handle your data; your name and other identifying information you enter in a published comment will be publicly displayed.