XS tag in SAM file
0
0
Entering edit mode
17 months ago
oghzzang ▴ 40

Dear users,

Hi. I'm oh.

I have questions about pre-processed bam by GATK4 pipeline (https://github.com/gatk-workflows/gatk4-data-processing/blob/master/processing-for-variant-discovery-gatk4.wdl).

In these processes, they only recommended "--ATTRIBUTES_TO_RETAIN X0" in MergeBamAlignment step.

So, my final recalibrated bam, there is no "XS" tag as follows.

A00126:66:HGLWFDSXX:3:1423:31693:6621   177     chr1    9996    0       93S58M  chr4    190122941       0       CCCCCCCCCCCCCCCCCCCCCCACAAACACCCCCCCCCCCCCCCCCCCCCAAACCCCCCCGCGCCTGTACACTCTTTCCCTACACGACGCTCTTCCGATATCCCTAACCCTAACCCTAACCCTAACCCTAACCCTAACCCTAACCCTAACC ??????????????+??+++++++++++++??+++?????+???+++?+?++++????+???5???+5+??+'???????5????++%5????'?????+'?????????????????????????????????????????????????? MC:Z:100S51M    MD:Z:0N0N0N0N0N2A50     PG:Z:MarkDuplicates     RG:Z:SA00719        NM:i:6  MQ:i:0  UQ:i:158        AS:i:53

In this point, I have two questions.

  1. I don't know the meaning of XS tag.

  2. How does it affect the post-steps (ex. variant calling, HLA typing, SV detect etc.) when there is no XS tag?

XS UQ GATK4 • 2.2k views
ADD COMMENT
0
Entering edit mode

The X* tags are called locally-defined tags, they optional and reserved to aligner-specific implementations, thus are not part of the SAM specifications:

2 Locally-defined tags

You can freely add new tags. Note that tags starting with ‘X’, ‘Y’, or ‘Z’ and tags containing lowercase letters in either position are reserved for local use and will not be formally defined in any future version of this specification.

I think XS:i and XS:A are bowtie / tophat tags. See some discussions:

AS:i and XS:i SAM File Fields (Bowtie2)

A new SAM tag for transcript strand

ADD REPLY

Login before adding your answer.

Traffic: 1898 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6