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
# claims to take multiple things with [,...]
About: Convert between textual and numeric flag representation
Usage: samtools flags INT|STR[,...]
# works
$ samtools flags 60
0x3c 60 UNMAP,MUNMAP,REVERSE,MREVERSE
# help message and no answer
$ samtools flags 60 43
About: Convert between textual and numeric flag representation
Usage: samtools flags INT|STR[,...]
Flags:
0x1 PAIRED .. paired-end (or multiple-segment) sequencing technology
0x2 PROPER_PAIR .. each segment properly aligned according to the aligner
0x4 UNMAP .. segment unmapped
0x8 MUNMAP .. next segment in the template unmapped
0x10 REVERSE .. SEQ is reverse complemented
0x20 MREVERSE .. SEQ of the next segment in the template is reversed
0x40 READ1 .. the first segment in the template
0x80 READ2 .. the last segment in the template
0x100 SECONDARY .. secondary alignment
0x200 QCFAIL .. not passing quality controls
0x400 DUP .. PCR or optical duplicate
0x800 SUPPLEMENTARY .. supplementary alignment
# lets try the comma it suggested, but it ignores the second one
$ samtools flags 60,43
0x3c 60 UNMAP,MUNMAP,REVERSE,MREVERSE
The text was updated successfully, but these errors were encountered:
Looks like an unclear documentation to me. I think that the comma only refers to when providing STRs as arguments, whereas you can only supply one INT at a time. I think:
The docs should state something clarifying that it is 1 numeric <-> set of textual, e.g.:
About: Convert numerical flag value into respective set of textual flags, or a set of textual flag into the corresponding numerical flag.
samtools flags 60 43 (outputs help message, 0 exit status) and samtools flags 60,43 (outputs textual set of first numerical flag) should maybe complain about too many arguments being provided, instead of the inconsistent behaviour?
The text was updated successfully, but these errors were encountered: