-
Notifications
You must be signed in to change notification settings - Fork 35
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
Alignment with match score not optimal #26
Comments
Hi, Thanks for the feedback. This case is really interesting. I understand the problem and realize that @jeizenga's penalties-conversion (i.e., match-score) formulas apply to global alignment. However, in the case of ends-free alignment, the query and text segments aligned (outside ends-free regions) can be smaller than So, the first solution found by the WFA (with adapted scores) doesn't have to be optimal. Nevertheless, I understand that we can bound the classic score ( Hence, I belive that performing Cheers, |
Some of the details of the implementation are a bit opaque to me, but assuming that you do have |
I have not dived deep to understand the implementation. Here are 2 more "not optimal" solution:
|
In the end, it was just an initialization problem. In principle, it should be fixed. |
Using the latest v2.2, with match score, the alignment is not optimal preferring a gap and not a mismatch. The alignment result is "8D1I1M7I", expecting "7D1X1M7I"
The result:
The text was updated successfully, but these errors were encountered: