| 266 | = Analyzing potential composition of reads in a fastq file = |
| 267 | |
| 268 | * To get a quick preview of what genomes/collections of sequences the reads in a fastq file might map to, one can use the FastQ Screen tool. |
| 269 | * Information about FastQ Screen can be found at this page: http://www.bioinformatics.babraham.ac.uk/projects/fastq_screen/ |
| 270 | * FastQ Screen allows you to screen your fastq file against a set of libraries, which can be set up to contain the genomes of interest, potential contaminating genomes, vectors, sequencing adaptors, ribosomal RNAs, or other contaminants commonly seen in sequencing experiments. This allows you to see if composition of the reads matches with what you expect and, where the contamination might have come from, if any. |
| 271 | * FastQ Screen uses bowtie or bowtie2 for mapping. The libraries you wish to screen against need to be bowtie-indexed. |
| 272 | * Paths to the bowtie indexed libraries need to be specified in the fastq_screen.conf file, which is called either from the same directory where the fastq_screen program is (by default) or from a manually specified location using the -conf /path/to/.conf file optioin. |
| 273 | * Sample commands are: |
| 274 | {{{ |
| 275 | |
| 276 | "bsub fastq_screen [OPTION] file.fq" |
| 277 | |
| 278 | Commonly used options are: |
| 279 | |
| 280 | [--aligner] Specify 'bowtie' or bowtie2' to use for the mapping. |
| 281 | [--outdir] Specify a directory in which to save output files. |
| 282 | [--illumina1_3] Assume that the quality values are in encoded in Illumina v1.3 format. Defaults to Sanger format if this flag is not specified. |
| 283 | [--conf] Manually specify a location for the configuration file to be used for this run. If not specified then the file will be taken from the same directory as the fastq_screen program. |
| 284 | |
| 285 | |
| 286 | }}} |
| 287 | |
| 288 | |