-
Notifications
You must be signed in to change notification settings - Fork 10
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
index out of range when encoding large VCF #12
Comments
Hi, thanks for reporting. Looks like this might be an issue with the stream-vbyte lib that I am using. |
Actually, your file isn't so large. I'll take it from here. |
Hi, I pushed a fix for this. |
Wow that was fast. That binary works for me on the small VCF I created. I am now testing it on the whole VCF, and should be able to report back in a couple days. |
Thanks for reporting! spliceAI is definitely a good stress test for echtvar. I found another issue using the file you sent that's still present in that binary (so don't continue to use that one). I have just fixed that as well. I'll make a release next week. |
Awesome, thanks again. |
Just verifying this is resolved for you. Please let me know any other issues. |
Sorry for not giving an update, yes it was resolved. Thanks you |
No problem. Just wanted to verify. |
Hi Brent
Thank you for another great tool. I am getting this error when trying to encode a rather large VCF. The VCF is spliceAI indels, with a custom max field (max of four values). The json config is also below. I am also trying to attach the smallest VCF I can make that would still produce the error. (hopefully you can download this https://www.icloud.com/iclouddrive/0967utbVnXQf9DsBnTWh4tiqA#chr5 , sorry it is so large, if I drill down to smaller locations, the error goes away)
The text was updated successfully, but these errors were encountered: