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

Mismatch costs above ~128 not handled correctly #5

Open
adamnovak opened this issue Mar 30, 2016 · 0 comments
Open

Mismatch costs above ~128 not handled correctly #5

adamnovak opened this issue Mar 30, 2016 · 0 comments

Comments

@adamnovak
Copy link
Member

gssw_create_score_matrix happily takes 32-bit ints in, but they aren't allowed to be above the max value for an unsigned char if you want the alignment to work. This doesn't really seem to be documented (except by realizing that the score matrix is a matrix of bytes), or checked for, so I just spent about 10 minutes wondering why vg was producing totally bogus alignments and scores when I tried to jack up various penalties into the thousands as a way to ask for, say, alignments with no mismatches.

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