-
Notifications
You must be signed in to change notification settings - Fork 7
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
synchronization with vgteam's fork #3
base: master
Are you sure you want to change the base?
Conversation
Allow max gap length to be different on different alignments
Add base-quality adjusted alignments
Fix memory alignment bug for packing quality scores
Fix bugs in DP and traceback
Dozeu already depends on the SSE4.1 API, this wasn't doing any good.
The latter in unavailable on many compilers.
Fix small bug in dynamic programming
Enable non-X86 compatibility
Fully implement the full length bonus
Use a simde that builds on Clang 11
Avoid complaints about extern C templates from simde
Handle an X-drop in between non-X-drop vectors correctly
For my part, I've done:
As I recall, the reason we were keeping the vgteam fork slightly upstream of the master branch here is that the option to have different insertion and deletion scores did not appear to be complete. Moreover, this is not a functionality that we had particular need for in VG. |
The commits from myself and @nemequ enable building dozeu for non-x86 and on x86 CPUs that lack SSE4.1. This will enable VG to build on arm64/aarch64 like the upcoming Apple Silicon, the well priced Graviton Amazon AWS servers, or the number 1 ranked supercomputer |
Allow full length bonus to be selected on a per read basis
Fix traceback over X-dropped vectors
Maintain two separate ranges in each forefront
Speed up score matrix look up in quality-adjusted alignments
…f reservations are wrong
Fix allocation to support longer problems
There is a lot going on here, but my understanding is that a number of issues have been resolved.
I think it's important to synchronize things. Upstream dozeu continues to get improvements and other fixes.
@jeizenga @mr-c @nemequ and @adamnovak might be able to describe relevant things.