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

Understanding the dpal logic #70

Open
karen-nativ opened this issue Oct 2, 2022 · 1 comment
Open

Understanding the dpal logic #70

karen-nativ opened this issue Oct 2, 2022 · 1 comment

Comments

@karen-nativ
Copy link

Hello,
I'd like help understanding the logic of the dpal module in global mode.
It should find the best global alignment using the Needleman Wunsch algorithm correct?
However I see different behavior, for example when running the following (the m flag allows a gap of length 100, and g parameter for global mode):
./ntdpal -m 100 ACCCCTTTTTTTTTTTTT AT g

The output is:
|ACCCCTTTTTTTTTTTTT| |AT| G score=0.00 len=2 |16,0|17,1|

From the output I understand that the alignment created is:

ACCCCTTTTTTTTTTTTT
----------------AT

Meaning the alignment includes indels and at the end a T/A mismatch and a T/T match.
However the Needleman Wunsch algorithm in this case can give us the following alignment:

ACCCCTTTTTTTTTTTTT
A----------------T

In this case the created gap is of the same length but we have two matches - A/A and T/T.
So it seems this output has a better score.

Why are the outputs different in this case?
Or perhaps does the dpal module work a bit differently than the NW algorithm? If so, how?

Thanks for the help.

@untergasser
Copy link
Member

I am not sure it is a complete implementation. It might be optimized for speed and primer design. I think match scores 1 mismatch and gap -1. So it the first is better. I hope this helps.

Best,
Andreas

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

2 participants