Tagged with #fastq
1 documentation article | 0 announcements | 1 forum discussion



Created 2015-08-13 23:03:02 | Updated 2015-08-19 22:12:26 | Tags: fastq pre-processing ubam
Comments (0)

Most sequencing providers generate FASTQ files with the raw unmapped read sequences, so that is the most common form in which the data is input into the mapping step of the pre-processing pipeline. This is not ideal because among other flaws, much of the metadata associated with sequencing runs cannot be stored in FASTQ files, unlike BAM files which can store more information. See this blog post for an overview of the many problems associated with the FASTQ format.

At the Broad Institute, we generate unmapped BAM (uBAM) files directly from the Illumina basecalls in order to keep all metadata in once place, and we do not write the data to FASTQ files at any point. This involves a slightly more complex workflow than is shown in the general Best Practices diagram. See this presentation for more details of how this works.

In case you're wondering, we still show the FASTQ-based workflow as the default in most of our documentation because it is by far the most commonly-used workflow, and we want to keep the documentation accessible for our more novice users.

No posts found with the requested search criteria.

Created 2013-01-31 11:23:58 | Updated | Tags: illumina fastq encoding sanger
Comments (2)

Hi, I use GATK for Variant Call in an Investigation Unit. When I use RealignerTargetCreator, I get an error: I'm using a wrong encoding for quiality scores. Which encoding (sanger, illumina, solexa) is ok to use with GATK? Do you have any tool to convert to that encoding? Thank you