![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help about setting up TopHat | lewewoo | Illumina/Solexa | 2 | 11-14-2011 06:52 PM |
bowtie parameter setting | nunu_ping | RNA Sequencing | 0 | 09-28-2010 02:59 PM |
Setting up and efficiency | ColNYC | General | 0 | 09-14-2010 09:26 AM |
Mismatch setting in BWA | genelab | Bioinformatics | 4 | 08-04-2010 05:02 AM |
tophat parameter setting | hollandorange | Bioinformatics | 0 | 05-14-2010 04:12 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: Seoul, South Korea Join Date: Oct 2011
Posts: 30
|
![]()
Hi all
![]() When running bwa, I want the read group information to be implanted so that I can use the information in picard and GATK later. I wrote down what I understood. Please point out if you think I'm wrong about something ![]() -I see that RG ID is a read discriminator; even when BAM files are merged thanks to RG ID the reads can be discriminated. -RG PL seems to be the sequencing machine platform (e.g. illumina). -RG LB seems to be referred by picard MarkDuplicates so PCR duplicates in each sequencing library can be removed. Now, I mention here that I read SAM-format spec.s. ( http://samtools.sourceforge.net/SAM1.pdf ) However, I'm confused about 2 more things. 1. Why does RG PU exist in the first place? Currently, the only reason I put in PU is to avoid picard and GATK errors later. 2. What's the difference between RG ID and RG SM? Is there any sutble difference between the two? Thanks for your replies in advance! Have a great day ![]() |
![]() |
![]() |
![]() |
#2 |
Peter (Biopython etc)
Location: Dundee, Scotland, UK Join Date: Jul 2009
Posts: 1,543
|
![]()
SM is sample, and one sample might be sequenced twice, for instance with 454 and Illumina, which would be two read groups with different platform. At least, that is my understanding.
|
![]() |
![]() |
![]() |
#3 |
Member
Location: Seoul, South Korea Join Date: Oct 2011
Posts: 30
|
![]()
Thank you for your reply. So although I don't need the information right now, it can be important in some other pipeline I might take, right?
![]() |
![]() |
![]() |
![]() |
Thread Tools | |
|
|