You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unsure whether to file this as a bug or a feature request:
I'm using the --sam-RG flag to set the read group for my alignment jobs. When I look at output from Bowtie, I do get a well-formed @RG line in the SAM header, but none of the reads have RG tags set. The SAMv1 spec (pdf) states both should be set, to enable matching of alignments to the corresponding group specified in the header. Quoting from the section specifying @RG lines in headers:
@RG
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.
My use case is that I need to run mulitple bowtie jobs, merge the outputs together, and still be able to trace alignments back to the job that created them. I had planned to set a unique read group for each job to do so.
Hi folks,
I'm unsure whether to file this as a bug or a feature request:
I'm using the
--sam-RG
flag to set the read group for my alignment jobs. When I look at output from Bowtie, I do get a well-formed@RG
line in the SAM header, but none of the reads haveRG
tags set. The SAMv1 spec (pdf) states both should be set, to enable matching of alignments to the corresponding group specified in the header. Quoting from the section specifying@RG
lines in headers:My use case is that I need to run mulitple
bowtie
jobs, merge the outputs together, and still be able to trace alignments back to the job that created them. I had planned to set a unique read group for each job to do so.Details:
bowtie -f --sam --sam-RG 'ID:test --best -x test_ebwt test_reads.fa
Thanks for your time!
The text was updated successfully, but these errors were encountered: