diff --git a/client/src/components/pages/FAQPage.js b/client/src/components/pages/FAQPage.js index 754eba12..fd27d332 100644 --- a/client/src/components/pages/FAQPage.js +++ b/client/src/components/pages/FAQPage.js @@ -10,12 +10,10 @@ const FAQPage = () => {

To generate plots, we either use pre-computed, batch-corrected and normalized sample-wise signal matrices, or use the UCSC bigWigSummary tool to calculate average signal across a feature for each sample - upon request. These values are combined with genotype information extracted from a{" "} - Gemini database into a box plot on a server, which is - then sent to the user’s browser if they have signed in and agreed to the terms of use. Plots are generated - as needed, rather than in advance, and are derived directly from the matrix or track and genotype data. + upon request. These values are combined with genotype information, extracted from a VCF file, to create a + box plot on a server, which is then sent to the user’s browser if they have agreed to the terms of use. + Plots are generated as needed, rather than in advance, and are derived directly from the matrix or track and + genotype data.

@@ -24,10 +22,11 @@ const FAQPage = () => { We generate{" "} UCSC Genome Browser track hubs upon - request to visualize averaged normalized track segments for a given genomic feature. These averaged tracks - are created on the fly by averaging bigWig regions of samples sharing an experimental treatment and - genotype, using our command-line tool:{" "} + rel="noreferrer">UCSC Genome Browser track hubs or{" "} + IGV.js{" "} + browser instances upon request to visualize averaged normalized track segments for a given genomic feature. + These averaged tracks are created on the fly by averaging bigWig regions of samples sharing an experimental + treatment and genotype, using our command-line tool:{" "} bw-merge-window.