MySeq is a web-application for privacy-protecting interactive analysis of personal genomes (distributed as compressed-and-indexed VCF files) inspired by GENOtation (previously the Interpretome) and DNA.LAND Compass. MySeq is intended for use as a genomics educational platform.
MySeq can load and analyze Tabix-indexed VCF files stored locally on the user's computer or available remotely. Queries and other analyses will only load the necessary blocks of the compressed VCF file, enabling efficient analysis of whole-genome-scale VCF files.
If you use MySeq, please cite:
Linderman MD, McElroy L, Chang L. MySeq: privacy-protecting browser-based personal Genome analysis for genomics education and exploration. BMC Med Genomics. 2019 Nov 27;12(1):172.
MySeq is deployed at https://go.middlebury.edu/myseq. Get started by doing one of 1) selecting a local VCF file and its index file, 2) providing a URL to a VCF file, or 3) selecting one of the pre-configured VCF files (Genome in a Bottle variant calls for NA12878/HG001). Check out a video demonstrating MySeq's features with variant calls from NA12878.
As an example of using a public URL, you can load the 1000 Genomes chr22 variant calls directly from AWS S3 with the following URL (try querying for rs72646967):
https://s3.amazonaws.com/1000genomes/release/20130502/ALL.chr22.phase3_shapeit2_mvncall_integrated_v5a.20130502.genotypes.vcf.gz
Note that querying and parsing a VCF with this many samples can take a few moments.
Any third-party server must allow cross-origin requests so that the MySeq application can requests resources from a different domain (e.g. from S3). See https://enable-cors.org for guides to configuring your server to enable cross-origin resource sharing (CORS).
MySeq analyses can be accessed by URL. All URLs accept the following query parameters:
| Parameter | Values |
|---|---|
vcf |
URL of Tabix-indexed VCF |
tbi |
URL of Tabix index file (if not specified, defaults to vcf.tbi) |
assumeRefRef |
1 to assume a WGS VCF in which absent calls have homozygous reference genotypes |
in addition, the query path accepts a the following query parameters:
| Parameter | Values |
|---|---|
query |
Comma-separated list of region, rsID or gene queries |
For example, the following links directly to query results in NA12878 (when running the development server)
or with the deployed application
The "bitter tasting" analysis example includes additional examples of query parameters in use. That example further demonstrates embedding MySeq as an iframe, e.g.
<iframe class="myseq" width=760 height=300 src="http://localhost:3000/query?vcf=https%3A%2F%2Fskylight.middlebury.edu%2F~mlinderman%2Fdata%2FNA12878.gatk-haplotype-annotated.vcf.gz&assumeRefRef=1&query=chr7%3A141673345%2C%20chr7%3A141672705%2C%20chr7%3A141672604"></iframe>to create an online tutorial.
MySeq is implemented with Create React App (CRA) and can be deployed via one of the CRA-suggested approaches. Note that MySeq uses client-side routing and so you will need to configure the server to serve index.html for unknown paths as described in the CRA documentation. At present MySeq is configured with a specific homepage. You will need to update the homepage property in package.json to point to your deployed homepage.
MySeq is implemented with Create React App (CRA) and so supports CRA's start, test and build scripts. In addition ESLint can be run with the npm run lint package script.
MySeq incorporates icons adapted from Font Awesome Free under a CC BY 4.0 license.