-
Notifications
You must be signed in to change notification settings - Fork 24
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
vcf2bed segmentation fault #22
Comments
I'm also seeing this happen on a large subset of WGBS samples (perhaps 25%). I'm consistently getting segfaulting in the middle of vcf2bed runs on large pileup.vcf.gz files from the biscuit pipeline. I can provide example files (though they're quite large) if needed. |
I think a lot has been updated since last year. Could you provide me the version number of biscuit you are using? Thanks. |
I'm using version 0.2.2.20170522, which I see is not the latest release. I'll try the latest version, and I'll report back tomorrow |
New version seems to solve the problem - this can be resolved. Thanks! |
fwiw, if you use samblaster with biscuit, be absolutely certain to use a
version later than 0.3.2
…--t
On Wed, Oct 17, 2018 at 10:48 AM Chris Miller ***@***.***> wrote:
New version seems to solve the problem - this can be resolved. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#22 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAARIhldSIyVQ24KUlzVtCD-WcDf72qxks5ul0MngaJpZM4PJWqY>
.
|
Thank you for getting back @chrisamiller . I am glad it worked! |
I followed the instructions to use biscuit 0.2.2.20170522 for alignment and so on using a 58GB TCGA WGBS file. I repeatedly got segmentation fault at vcf2bed step
biscuit vcf2bed -k 10 -t cg output.vcf.gz > output.cg.bed
job killed when the output is about 42Mb. I have tried small input and have no problems.
Btw, I assume I can chunk the input VCF to smaller ones and get the same result after merging the output. Could you confirm this?
The text was updated successfully, but these errors were encountered: