# What is the meaning of these misaligned reads in a sequencing run?

I am analyzing some SARS-CoV-2 sequencing runs abd often find read alignments like the one in the image.

GACCCGGTGGGTTTTAC---ACTTAAAAACACAGTCTGTAC
GACCCTGTGGGTTTTAC---ACTTAAAAACACAGTCTGTAC
GTTTCAC---ACTTAAAAACACAGTCTGTAC
GGTTTAC---ACTTAAAAGCACAGTCTGTAC
CCACACTCTCCTAGCAC---ACTTAAAAACACAGTCTGTAC
CCACACTCTCCTAGCACCATACTTAAAAACACAGTCTGTAC


It basically says there are reads that share part of a sequence and part of another one. The first 4 reads are the same sequence and it's a sequence that you can effectively find in the official SARS-CoV-2 assembly but the other two reads are a mix of this one with another sequence (and both are the same mix) but with only a small (3bps) indel of difference.

The sequence of the last two reads does not appear anywhere in the official SARS-CoV-2 sequence.

• What does it mean?
• Are these sequencing errors?
• If that is the case how is it that the same mistake is repeated with similar but not exactly the same data?
• If these are real RNA sequences present in the probe, why are these not used anywhere in the final assembly and how did they arrive there?

Is there any other option that I am missing?

• That's an old question that somehow has reappeared today. I'd like to point out that I realized months later that there was a problem in my alignment software and I think that's why there was a repeated indel. Nov 14 '20 at 2:51
• There is a lot of biological interest in this sort of question, so its really important to understand this thoroughly
– M__
Dec 5 '20 at 10:11

• I have news about that. I have found that sometimes there is a merge between a read and a reverse-complemented read. That can only mean that the merge occurs when the sequence has been translated to DNA in the PCR phase. Therefore at least in some cases it doesn't seem to be a rearrangement of the virus. An example read for SARS-CoV-2: AGGTAATAGCACATCACTACGCAACTTTAGATACATTTCTTTATTTAACAAAAAGGTGCACAGCGCAGCTTCTTCAAAAGTACTAGTTTAAAAGACCAATAAATCCTACTGACCAGTCTTCTTACATCGTTGATAGTGTTACAGTGAAGAATGGTTCCATCCATCTTTACTTTGATAAAGCTGGTCAAAAGACTTATGAAAGACATTCTCTCTCTCATTTTGTTAACTTAGAC Apr 26 '20 at 1:02