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
In running STARSolo with --quantMode TranscriptomeSAM and --outSAMattributes CR UR, the CR and UR tags in the transcriptome bam do not match those in the genome bam. I checked versions 2.7.8a, 2.7.7a, 2.7.6a, and 2.7.5a, and I didn't see this behaviour in 2.7.5a or 2.7.6a. It appears that the sequences for these incorrect tags are being pulled from the read immediately upstream of the proper read.
To double check, I added the CB and UMI sequences to the read name in the UMI-tools style. In the genome bam CR,UR,CB,UB match the read-name sequences, and give the correct tags (CR:Z:TGTTACCGTC UR:Z:AAAACCAAAT)
Searching for this read in the input files, we see that the fastq files are properly synced, and it seems that the incorrect CR/UR are from the previous read in the fastq:
…ambled in TranscriptomeSAM file Aligned.toTranscriptome.out.bam. This bug appeared in 2.7.7a. Fixed a bug causing seg-faults with --clipAdapterType CellRanger4 option.
thanks a lot for reporting this bug.
Please try the patch I just pushed to github-master, it should have fixed the issue.
I will make a 2.7.8b release in a couple of days.
Hi,
In running STARSolo with
--quantMode TranscriptomeSAM
and--outSAMattributes CR UR
, the CR and UR tags in the transcriptome bam do not match those in the genome bam. I checked versions 2.7.8a, 2.7.7a, 2.7.6a, and 2.7.5a, and I didn't see this behaviour in 2.7.5a or 2.7.6a. It appears that the sequences for these incorrect tags are being pulled from the read immediately upstream of the proper read.To double check, I added the CB and UMI sequences to the read name in the UMI-tools style. In the genome bam
CR,UR,CB,UB
match the read-name sequences, and give the correct tags (CR:Z:TGTTACCGTC UR:Z:AAAACCAAAT
)Whereas in the transcriptome bam they do not (
CR:Z:AGTTCTTCCG UR:Z:GCCGAATCTT
)Searching for this read in the input files, we see that the fastq files are properly synced, and it seems that the incorrect CR/UR are from the previous read in the fastq:
Edit: add 2.7.6a, fix version typos
The text was updated successfully, but these errors were encountered: