-
Notifications
You must be signed in to change notification settings - Fork 2
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
VEP - structural variants too long to annotate #1224
Comments
I think this is driven by:
We should just set these as skipped and not pull them out of the DB Should be able to make an 11M length del or something as a test case |
They were killed from OOM
It'll be a bit of a pain to not write them into the VCF as then we have multiple queries for "unannotated variants" ie to check in annotation range lock etc I don't think it harms anything by writing them out into the VCF - they'll be quickly skipped, but now skip reason will be correctly set. I will pull down a SV file to my local machine and run it once with and once without removing long records and check memory usage
original file - 664 long SV variants
New (stripped out longies)
Will try the one that crashed out VEP:
dump_18489_structural_variant.vcf
dump_18489_structural_variant_no_longies.vcf
|
So the amount of RAM used doesn't seem to vary much So won't strip them out |
Plan B is to limit the number of RepeatMasker records returned It was getting way out of hand, limited to 10k |
I have removed these from the VCF just before writing, and deployed to vg.com - will see if it makes a difference, re-running the annotation pipelines that crashed. There really are over 1k of variants in there that are >10M long wtf |
Hmm, seems to work. Need to verify that nothing went askew with the non-dumping of variants (ie they still got the annotation skipped message etc) I think they would only be inserted if vep warnings should just do asap |
We get these:
For these:
The text was updated successfully, but these errors were encountered: