-
Notifications
You must be signed in to change notification settings - Fork 240
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
split-vep could not recognize M-CAP #1686
Comments
This is caused by the dash which is not considered a valid tag name character by VCF specification. This is a problem because A quick workaround is to edit the header and replace with underscores, e.g. The program could be also made smarter and replace such characters automatically. Could you please show the VEP line from the header and a single data line for debugging? |
Thanks for the reply. I tried to reheader and replace it as MCAP and that works well, just need more steps to edit the header and then reheader. Attched with some lines, see if it could help you fix this problem, M-CAP is in the last second and last third fields. |
This is now addressed, offending characters are replaced with underscores. Please try it out |
Thank you so much, it worked well, with "%M_CAP_pred". |
Invalid characters are replaced with underscores, uniqueness of newly formed tag names is currently not checked for (a possible future todo). Fixes samtools#1686
Hi, I try |
@hanguojun007 This would have to be done before the plugin is run. For example the VEP definition
would be changed to
with reheader, then the plugin With the latest version this is not needed anymore. |
Invalid characters are replaced with underscores, uniqueness of newly formed tag names is currently not checked for (a possible future todo). Fixes #1686
Hi,
I am using bcftools +split-vep to extract the M-CAP score from the vcf annotated by VEP, but it could not recognize and produced error below:
I checked with
bcftools +split-vep *.vep.vcf.gz -l
, "M-CAP_score" was actually present in the CSQ field.I also tired with some other typos, but all didn't work. Are there any solutions to solve this problem?
Thanks!
The text was updated successfully, but these errors were encountered: