Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

With different read name, the algnment results seem different #486

Open
TomhitsJerry opened this issue Aug 19, 2024 · 0 comments
Open

With different read name, the algnment results seem different #486

TomhitsJerry opened this issue Aug 19, 2024 · 0 comments

Comments

@TomhitsJerry
Copy link

TomhitsJerry commented Aug 19, 2024

I use a totally the same fq, with the same sequence and quality, but only the read name differ. And got a different algnment result, here is one example of a read:
de463d9bc779358fdb68182b5f1a147
As you see, two reads with the same sequence and quality:
CCACAAAATAATAACAGCCATCTATGACAGACCCACAGCCAACATCATACAGAATGGGGAAAAATTGGAGGCATA
EEEEEEEEEEEEEEEEEEEEE@EEEEEEEEEEEEEEE@EEEEEEEEEEEEEEEEEEEEEEEEEEEEE@6EEEEEE..............................
but only with different read name:
2305151010:9:2D240611017US2S2720DX:L00:R001C020:2179:0810
202408121835_2305151010_2D240611017US2S2720DX_B_20240812B86L00R001C020:21790810:9
while have different results:
the first one is mapped:2305151010:9:2D240611017US2S2720DX:L00:R001C020:2179:0810
the second is unmap: 202408121835_2305151010_2D240611017US2S2720DX_B_20240812B86L00R001C020:21790810:9
the version of bowtie2 I used is 2.5.1, I cant see any update or changes about read name from the newly versions, and maybe the new version may have same siuation too.
Looking forward to it, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant