-
Notifications
You must be signed in to change notification settings - Fork 18
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
[simd_abpoa_align_sequence_to_subgraph1] Error in cg_backtrack. (4) #9
Comments
Thank you @ekg for providing this example. The banded DP is more fragile when the lengths of sequences differ too much, like this data: 264 vs 443. |
Any workaround (even dropping into non-banded mode when this happens) would be helpful! What do you suggest? Running everything non-banded to avoid this issue would be expensive. |
I'm also running into this issue when using the python API. Instead of being able to handle the error, the thread that gets the error just hangs since this error kicks you out of python. Is there a way for me to be able to handle this error through the python API? Disabling adaptive banding takes too long. |
There is now a flag on the result object that indicates if the traceback
was OK. It's not propagated to python.
…On Tue, Oct 13, 2020, 21:15 Roger Volden ***@***.***> wrote:
I'm also running into this issue when using the python API. Instead of
being able to handle the error, the thread that gets the error just hangs
since this error kicks you out of python. Is there a way for me to be able
to handle this error through the python API? Disabling adaptive banding
takes too long.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDQEIFJ6QIILWQUJCRURDSKSRO5ANCNFSM4SGARACA>
.
|
@rvolden As mentioned by Erik, this new flag is not added in pyabpoa right now, I will get it done sone. |
Anyway, the ultimate goal is to fix this bug instead of just break the loop and not provide any alignment result. |
You're right, the traceback error is 2, not 4. It's for a pairwise alignment where one has a long polyA but the other doesn't. poa_aligner = poa.msa_aligner(match=5, extra_b=16) # anything lower for extra_b throws the traceback error
res = poa_aligner.msa(subreads, out_cons=False, out_msa=True)
# errors out here
|
I modified the codes of the traceback part in the latest commit. Hopefully, this can resolve these bugs. @ekg @rvolden This works on the two sequence sets you guys provided here, please try it out on some other data. Yan |
Unfortunately, I still find cases that cause this error. fail_smoothxg_block_9338.fa.txt
|
I don't get the error for python2, but I get it in python3. The only modification I made to the makefile for python3 was to change the command to python3 instead of python: 103 install_py: python/cabpoa.pxd python/pyabpoa.pyx python/README.md
~ 104 | ${py_SIMD_FLAG} python3 setup.py install
105 |
106 sdist: install_py
~ 107 | ${py_SIMD_FLAG} python3 setup.py sdist #bdist_wheel To clarify, this is python 3.6.9, and the error I get with the same sequences I provided is |
@ekg This is a different case and different type of bug. Working on that. |
Nothing was changed related to the python side. Did you re-install pyabpoa in python3? |
Yeah, I reinstalled using pip3 for python3 |
These changes haven't been pushed to the pypi. So |
I should've been a bit more clear. I did |
This really sounds weird to me. Also, it works on my pc when I install with python3. |
Removed everything previously installed. It's working now. Thank you! |
I finally found a small reproducible example of an alignment problem.
To reproduce on this input FASTA, fail_smoothxg_block_3055.fa.txt:
The text was updated successfully, but these errors were encountered: