-
Notifications
You must be signed in to change notification settings - Fork 21
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
smoove genotype - could not import: bam_hdr_destroy #230
Comments
I tried running it with smoove duphold, |
I'd like to ask you, has the problem been solved? |
I am also having the same problem. |
Hi, this means you need to use a newer version of htslib. |
Hi, I'm using htslib v1.20 and duphold v0.1.4 (both bioconda). I've tried different versions of htslib to no avail. I also tried updating duphold but conda tells me "All requested packages are already installed" if I don't specify a version, and that newer specified versions are incompatible with other packages in the environment (in a fresh conda environment install of smoove and all dependencies). Smoove ran just fine if duphold was omitted. Thanks. |
I am having the same problem. I have tried different versions of htslib as well (including initial v1.20) and duphold always gives error message: "could not import: bam_hdr_destroy". Even a clean install of the conda version of duphold(v0.1.4) produces this error. It appears the conda install for duphold is the issue. To get around this, I installed duphold from the github version here and replaced the default install (v0.1.4) with this new install (v0.2.3) in the bin for the conda environment for smoove. This appears to have fixed the problem |
@benstemon that's the best way. The github version is a static binary so has no dependencies. I don't know what's going on with the conda version. |
Hi,
I get this error for a lot of the samples I'm running, although I do seem to have a complete genotyped file for each bam I have.
I ran this command:
I was wondering what the bam_hdr_destroy file is and why it's not importing? Or if the issue is related to the former part of the joblog about the end position being smaller. Thanks!
Heidi
The text was updated successfully, but these errors were encountered: