Mercurial > repos > devteam > bwa_0_7_10
comparison bwa_macros.xml @ 4:d04dfa7de2dc draft
Uploaded
| author | devteam |
|---|---|
| date | Thu, 06 Nov 2014 14:52:14 -0500 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 3:6bfb657c8fe1 | 4:d04dfa7de2dc |
|---|---|
| 1 <macros> | |
| 2 | |
| 3 <token name="@RG@"> | |
| 4 ----- | |
| 5 | |
| 6 .. class:: warningmark | |
| 7 | |
| 8 **Read Groups are Important!** | |
| 9 | |
| 10 One of the recommended best practices in NGS analysis is adding read group information to BAM files. You can do thid directly in BWA interface using the | |
| 11 **Specify readgroup information?** widget. If you are not familiar with readgroups you shold know that this is effectively a way to tag reads with an additional ID. | |
| 12 This allows you to combine BAM files from, for example, multiple BWA runs into a single dataset. This significantly simplifies downstream processing as | |
| 13 instead of dealing with multiple datasets you only have to handle only one. This is possible because the readgroup information allows you to identify | |
| 14 data from different experiments even if they are combined in one file. Many downstream analysis tools such as varinat callers (e.g., FreeBayes or Naive Varinat Caller | |
| 15 present in Galaxy) are aware of readgtroups and will automatically generate calls for each individual sample even if they are combined within a single file. | |
| 16 | |
| 17 **Description of read groups fields** | |
| 18 | |
| 19 (from GATK FAQ webpage): | |
| 20 | |
| 21 .. csv-table:: | |
| 22 :header-rows: 1 | |
| 23 | |
| 24 Tag,Importance,Definition,Meaning | |
| 25 "ID","Required","Read group identifier. Each @RG line must have a unique ID. The value of ID is used in the RG tags of alignment records. Must be unique among all read groups in header section. Read group IDs may be modified when merging SAM files in order to handle collisions.","Ideally, this should be a globally unique identify across all sequencing data in the world, such as the Illumina flowcell + lane name and number. Will be referenced by each read with the RG:Z field, allowing tools to determine the read group information associated with each read, including the sample from which the read came. Also, a read group is effectively treated as a separate run of the NGS instrument in tools like base quality score recalibration (a GATK component) -- all reads within a read group are assumed to come from the same instrument run and to therefore share the same error model." | |
| 26 "SM","Sample. Use pool name where a pool is being sequenced.","Required. As important as ID.","The name of the sample sequenced in this read group. GATK tools treat all read groups with the same SM value as containing sequencing data for the same sample. Therefore it's critical that the SM field be correctly specified, especially when using multi-sample tools like the Unified Genotyper (a GATK component)." | |
| 27 "PL","Platform/technology used to produce the read. Valid values: ILLUMINA, SOLID, LS454, HELICOS and PACBIO.","Important. Not currently used in the GATK, but was in the past, and may return. The only way to known the sequencing technology used to generate the sequencing data","It's a good idea to use this field." | |
| 28 "LB","DNA preparation library identify","Essential for MarkDuplicates","MarkDuplicates uses the LB field to determine which read groups might contain molecular duplicates, in case the same DNA library was sequenced on multiple lanes." | |
| 29 | |
| 30 | |
| 31 **Example of Read Group usage** | |
| 32 | |
| 33 Suppose we have a trio of samples: MOM, DAD, and KID. Each has two DNA libraries prepared, one with 400 bp inserts and another with 200 bp inserts. Each of these libraries is run on two lanes of an illumina hiseq, requiring 3 x 2 x 2 = 12 lanes of data. When the data come off the sequencer, we would create 12 BAM files, with the following @RG fields in the header:: | |
| 34 | |
| 35 Dad's data: | |
| 36 @RG ID:FLOWCELL1.LANE1 PL:illumina LB:LIB-DAD-1 SM:DAD PI:200 | |
| 37 @RG ID:FLOWCELL1.LANE2 PL:illumina LB:LIB-DAD-1 SM:DAD PI:200 | |
| 38 @RG ID:FLOWCELL1.LANE3 PL:illumina LB:LIB-DAD-2 SM:DAD PI:400 | |
| 39 @RG ID:FLOWCELL1.LANE4 PL:illumina LB:LIB-DAD-2 SM:DAD PI:400 | |
| 40 | |
| 41 Mom's data: | |
| 42 @RG ID:FLOWCELL1.LANE5 PL:illumina LB:LIB-MOM-1 SM:MOM PI:200 | |
| 43 @RG ID:FLOWCELL1.LANE6 PL:illumina LB:LIB-MOM-1 SM:MOM PI:200 | |
| 44 @RG ID:FLOWCELL1.LANE7 PL:illumina LB:LIB-MOM-2 SM:MOM PI:400 | |
| 45 @RG ID:FLOWCELL1.LANE8 PL:illumina LB:LIB-MOM-2 SM:MOM PI:400 | |
| 46 | |
| 47 Kid's data: | |
| 48 @RG ID:FLOWCELL2.LANE1 PL:illumina LB:LIB-KID-1 SM:KID PI:200 | |
| 49 @RG ID:FLOWCELL2.LANE2 PL:illumina LB:LIB-KID-1 SM:KID PI:200 | |
| 50 @RG ID:FLOWCELL2.LANE3 PL:illumina LB:LIB-KID-2 SM:KID PI:400 | |
| 51 @RG ID:FLOWCELL2.LANE4 PL:illumina LB:LIB-KID-2 SM:KID PI:400 | |
| 52 | |
| 53 Note the hierarchical relationship between read groups (unique for each lane) to libraries (sequenced on two lanes) and samples (across four lanes, two lanes for each library). | |
| 54 </token> | |
| 55 <token name="@info@"> | |
| 56 ----- | |
| 57 | |
| 58 .. class:: infomark | |
| 59 | |
| 60 **More info** | |
| 61 | |
| 62 To obtain more information about BWA and ask questions use these resources: | |
| 63 | |
| 64 1. https://biostar.usegalaxy.org/ | |
| 65 2. https://www.biostars.org/ | |
| 66 3. https://github.com/lh3/bwa | |
| 67 4. http://bio-bwa.sourceforge.net/ | |
| 68 | |
| 69 </token> | |
| 70 | |
| 71 <token name="@dataset_collections@"> | |
| 72 ------ | |
| 73 | |
| 74 **Dataset collections - processing large numbers of datasets at once** | |
| 75 | |
| 76 This will be added shortly | |
| 77 | |
| 78 | |
| 79 </token> | |
| 80 | |
| 81 | |
| 82 </macros> |