-
Notifications
You must be signed in to change notification settings - Fork 39
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
"Can't find a matching hmm library in the database!" when running --query mode from antiSMASH v6 results #67
Comments
Just checking in about this. Do you have any suggestions? |
bump |
No I haven't been able to get past it so I haven't been able to use to package. I've posted my data if you want to try it out. |
@jolespin did you ever figure out the issue? I encounter the issue too. |
I encounter the same issue, anybody know how to solve this problem? I used the latest software (v2.0.0) and the latest database for bigslice, I tried to put all database files into one directory but it didn't work. |
@brilliant2643 @PannyYi I was going to incorporate it into my VEBA package but wasn't ever able to fix this issue. I gave up on this software in the interim but look forward to using it/incorporating once this issue is resolved. I developed some de novo clustering for antiSMASH BGCs in the VEBA biosynthetic module. Some of the scripts are standalone too. You can use it like:
The
You can also run antiSMASH with it instead of providing antiSMASH results (check the docs). Not sure if it works with your results but if it does, you will end up with the following files:
I typically use the Hope this helps. If you want to read more about the methodology check out the preprint on bioRxiv. Peer reviewed paper should be coming out soon. In the final stages of review right now. If you want something similar to BIG-SLICE then I think you can use the BIRCH algo in scikit-learn but I'm not sure exactly how the backend is implemented. |
Thanks a lot ! I will try it later! |
still gives the same error
Anyone could figure out the reason? |
All right, in many attempts, I found that this issue can be solved by using BigSlice V1.1 |
While, it should be notice that, BigSlice V1.1 can only recognize the results of Antismash V6 |
I'm running version: v1.1.1 . This is issue is an extension of #66
Attaching my antiSMASH v6 directory.
SRR17458614__CONCOCT__P.2__9.zip
The text was updated successfully, but these errors were encountered: