-
Notifications
You must be signed in to change notification settings - Fork 32
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
HATCHet fails with new version of bcftools 1.21 #227
Comments
Hi, any update on this bug? For some reason, this forced command: |
Hi tahashmi, I've pushed the fix so it should work with default conda recipe for HATCHetv2.1.0. Please try to reinstall it (without the specific version for bcftools and samtools) and let me know if it fixes your problem. Thank you. |
Hi @RunpengLuo , Thanks for this. Unfortunately due to removing and installing bcftools manually on HPC, I am having some issue with my account, hopefully it will be resolved today and then will try again. |
Hi, @RunpengLuo I have installed fresh hatchet conda env. Issue still exists:
|
Hi @tahashmi, sorry for the inconvenience, I think the BioConda hasn't sync the latest commit on the main branch, and I will work on this ASAP and let you know when it is done. At the mean time, do you mind to install HATCHet directly from source, the detailed steps are shown as follows. Thank you.
|
Thanks for the prompt reply. I can wait once you fix this issue. My hatchet workflow is already setup with default installation method, and it already took some time to setup gurobi. |
The new version of bcftools 1.21 requires to specify that the
AD
field is inINFO
in the query command used by HATCHet inhttps://github.com/raphael-group/hatchet/blob/783058042cc3ef78b3f46ff7478edb5b6dfd9f44/src/hatchet/utils/count_alleles.py#L236C22-L236C53
Specifically, the following command of bcftools called by HATCHet fails and hang with the new version of bcftools 1.21:
failing with the message:
The temporary solution is to install HATCHet with a previous version of samtools/bcftools, like 1.19, after correct setting up of bioconda channells:
In the meanwhile, @mmyers1 can we please fix this by making the bcftools command compatible, or changing bioconda recipe of HATCHet to only use a compatible version of bcftools/samtools please?
The text was updated successfully, but these errors were encountered: