Can't find a matching hmm library in the database!

[1362996609zby]

Thanks for the tool, sorry this may be a nasty bug as I see many people encounter this problem. I installed bigslice exactly as instructed in the readme file, and successfully ran bigslice --version. At the same time, I indicated the location of program_db_folder in the command, which is where the download_bigslice_hmmdb command is placed by default, and the content is complete. However, I tried countless times and still got this error:
Fetching run details...
Can't find a matching hmm library in the database!
BiG-SLiCE run failed.
This leads me to wonder if there is some nasty bug, or can you tell me how to solve this problem? Thank you very much.

[CRZ0128]

I also followed the correct steps to install the software completely, but I also encountered the same problem

[1362996609zby]

I also followed the correct steps to install the software completely, but I also encountered the same problem

I solved this later. It is important that you follow the instructions in the README file to install download. Although bigslice has a parameter that specifies the database location, I find this parameter a bit problematic and it's best to install it to the default location using this command. Good luck!

[chenyongnian]

I also followed the correct steps to install the software completely, but I also encountered the same problem我也按照正确的步骤完全安装了软件，但我也遇到了同样的问题

I solved this later. It is important that you follow the instructions in the README file to install download. Although bigslice has a parameter that specifies the database location, I find this parameter a bit problematic and it's best to install it to the default location using this command. Good luck!我后来解决了这个问题。请务必按照README文件中的说明进行安装下载。虽然bigslice有一个参数指定数据库位置，但我发现这个参数有点问题，最好使用这个命令将其安装到默认位置。祝你好运！

I've encountered the same problem. Would you please show me what location you run the command and the parameters used? Thank you very much~~~

[ZhangZF1102]

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

[1362996609zby]

Thanks for your reply, It's clear that the big-slice have many bugs that havn't been solved, but i am glad that you can run it successfully, best wishes!

…

________________________________ 发件人: ZhangZF1102 ***@***.***> 发送时间: 2025年1月8日 14:10 收件人: medema-group/bigslice ***@***.***> 抄送: 1362996609zby ***@***.***>; Author ***@***.***> 主题: Re: [medema-group/bigslice] Can't find a matching hmm library in the database! (Issue #91) 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 ― Reply to this email directly, view it on GitHub<#91 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDRN6O2JSNA2BKY7BIHIFZT2JS6L3AVCNFSM6AAAAABSSIVN5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZWHAZDONZUHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[shuklagyanesh21]

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 have tried bigslice version 1.1.1 in a new python environment but the error
Fetching run details... Can't find a matching hmm library in the database! BiG-SLiCE run failed.
persists. The input region files given were from antismash v6. This is very frustrating. the --query mode has more than n number of issues.

Edit: The latest version of bigslice doesnt recognize older antismash version ouputs. So the only way around to use the query mode is to downgrade bigslice to v1 and use results from antismash v6 to query. This works because the older 1.2M BGC cluster was created using older bigslice and antismash versions.

[mengjx855]

Hi all, I’m seeing the same problem. I used antiSMASH v7 to identify BGCs, but the pre-processed database for query mode is built for antiSMASH v6, which creates a mismatch. The v7 results work with BiG-SLiCE v2, but not with the corresponding database; BiG-SLiCE v1 has a compatible database but doesn’t recognize antiSMASH v7. Hoping for an updated paper and a compatible database/software from the Medema lab soon. Any tips or workaround would be great.

[ZhangZF1102]

Hi all, I’m seeing the same problem. I used antiSMASH v7 to identify BGCs, but the pre-processed database for query mode is built for antiSMASH v6, which creates a mismatch. The v7 results work with BiG-SLiCE v2, but not with the corresponding database; BiG-SLiCE v1 has a compatible database but doesn’t recognize antiSMASH v7. Hoping for an updated paper and a compatible database/software from the Medema lab soon. Any tips or workaround would be great.

Currently there is still no pre-processed hmm database for BiG-SLiCE v2. As my attempts, the right way for bigslice abalysis is "antiSMASH v6 predication"—"BiG-SLiCE v1.1 analysis".
I also compared the BGC predicated by antiSMASH v7 and V6, V7 results about 5.7% more BGCs than V6.

[mengjx855]

Thanks for your kind response. In our study, we identified a large number of BGCs, and re-running the predictions would be time-consuming. I’m still waiting for the new pre-processed HMM database and would appreciate any update on its availability. 😁😁😁 # @

Hi all, I’m seeing the same problem. I used antiSMASH v7 to identify BGCs, but the pre-processed database for query mode is built for antiSMASH v6, which creates a mismatch. The v7 results work with BiG-SLiCE v2, but not with the corresponding database; BiG-SLiCE v1 has a compatible database but doesn’t recognize antiSMASH v7. Hoping for an updated paper and a compatible database/software from the Medema lab soon. Any tips or workaround would be great.

Currently there is still no pre-processed hmm database for BiG-SLiCE v2. As my attempts, the right way for bigslice abalysis is "antiSMASH v6 predication"—"BiG-SLiCE v1.1 analysis". I also compared the BGC predicated by antiSMASH v7 and V6, V7 results about 5.7% more BGCs than V6.