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
This will create two RG tags for each read.
Of course, this can be averted without the -t flag in samtools fastq.
But the documentation of samtools fastq says it'll copy not only RG, but also BC and QT tags, so one could still want to keep that flag.
Alternatively, one can skip specifying the readgroup info for minimap2, and later add that by samtools reheader but this is extra work.
So, a convenient feature would be for minimap2 to check if the "comments" that would be copied from the input FASTQ come with RG. And if so, don't write that again based on the information provided via -R "@RG\ID:matching_readgroup_id...".
Thanks,
Steve
The text was updated successfully, but these errors were encountered:
Hi Heng,
This isn't necessarily a bug, but I was a bit surprised.
Also, this definitely is not a high-impact issue.
So, this is arguably an edge case.
When one has an input where each read has its associated RG (readgroup) information, that could be duplicated.
Here's an example.
Say the input is an unaligned BAM that has the RG tag for all its reads (with other tags like 5mC calls), one would run the command like the following
This will create two RG tags for each read.
Of course, this can be averted without the
-t
flag insamtools fastq
.But the documentation of
samtools fastq
says it'll copy not only RG, but also BC and QT tags, so one could still want to keep that flag.Alternatively, one can skip specifying the readgroup info for
minimap2
, and later add that bysamtools reheader
but this is extra work.So, a convenient feature would be for
minimap2
to check if the "comments" that would be copied from the input FASTQ come with RG. And if so, don't write that again based on the information provided via-R "@RG\ID:matching_readgroup_id..."
.Thanks,
Steve
The text was updated successfully, but these errors were encountered: