-
Notifications
You must be signed in to change notification settings - Fork 38
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
Not a BGZF file #9
Comments
Is that 6 minutes to variant call a human ?? |
Hi Jared, Thanks for reporting this. Although I can't reproduce the issue on my machine, I think I know what's going on. Basically octopus will try to generate an index for compressed VCF (or BCF) output. This happens on destruction of the handle to the file. When the handle gets moved around early in the run (before anything has been written) the 'moved from' handle gets destroyed. I think the old handle remains in a valid state in your setup and therefore attempts to build an index on the empty file, which triggers this warning. This shouldn't have any adverse affects downstream, but I've added some additional checks to stop the index being generated on empty handles. Would you mind checking out the develop branch and seeing if the warning is still being generated? Many thanks, |
@iqbal-lab Alas no, this is on a ~100MB test .bam. Still, we are seeing running times of ~75mins with @dancooke checking develop now |
Wow. |
I can confirm that I no longer see the warning message in the develop branch. Thanks for the fast response. |
Hello again!
I am still receiving the above warning message. This is on an Ubuntu 16.04 VM. The output looks fine as far as I call tell.
The text was updated successfully, but these errors were encountered: