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

Try extension alignment if seed appears to be ungapped #377

Open
marcelm opened this issue Dec 11, 2023 · 1 comment
Open

Try extension alignment if seed appears to be ungapped #377

marcelm opened this issue Dec 11, 2023 · 1 comment

Comments

@marcelm
Copy link
Collaborator

marcelm commented Dec 11, 2023

Btw, what does strobealign currently do when the region with the NAM has the same length on the query and the reference and Hamming distance of the NAM region is high?

Do we fully realign such cases with SSW? If so, an optimization would be to run ksw on the ends only. I remember we have discussed similar scenarios when we tried out partitioning the alignments and use WFA2 but I don't remember the conclusions.

Clarification: I meant when Hamming distance is high -- possibly because regions outside the NAM region do not fit (e.g. indels). Then it might be inefficient to realign the whole read. One approach would be to try hamming of the NAM hit only, then extension of the ends.

Originally posted by @ksahlin in #357 (comment)

@marcelm
Copy link
Collaborator Author

marcelm commented Dec 11, 2023

Yes, we fully align. The only case in which we do not fully align is when the NAM on the query and the reference have the same length and the hamming distance is low (<5% differences).

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