You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had trouble when reading files with GeneticVariation.VCF.Reader that were output form the gatk tool: funcotator. When I called the function on the vcf file it threw an error. I have tried to describe this error and give a possible cause of the error below. It is a minor issue, and I resolved it by deleting a single line in my input vcf file before calling GeneticVariation.VCF.Reader which solved the problem but i wanted to draw the developers to the issue as it would be better to run it without my hack of manually deleting a line in the input vcf file :)
Expected Behavior
I took a vcf file, v4.2, that was output from funcotator and passed it to the function GeneticVariation.VCF.Reader.
Current Behavior
here is the current behavior from a live Julia session:
julia> inputvcfIO = open("./NA18486.annotated.edited.vcf", "r")
IOStream(<file ./NA18486.annotated.edited.vcf>)
julia> GeneticVariation.VCF.Reader(inputvcfIO)
GeneticVariation.VCF.Reader(BioCore.Ragel.State{BufferedStreams.BufferedInputStream{IOStream}}(BufferedStreams.BufferedInputStream{IOStream}(<256.0 KiB buffer, 28% filled, data immobilized>), 1, 3414, false), GeneticVariation.VCF.Header:
metainfo tags: fileformat ALT FILTER FORMAT GATKCommandLine INFO contig source
sample IDs: NA18486)
And as you can see the problem is resolved.
Here is my issue: I cannot see what is wrong with that line ##Funcotator Version=4.2.6... Why is it not accepted as valid input?
Note, it is possible that other gatk tools insert lines like this in their vcf output files so the problem may occur in other places. (I acknowledge this may actually be an issue to raise with the gatk developers instead?)
This bug certainly affects the usability of the code. I was initially using the VIVA command line program for analyzing vcf files and received this error. so I had to go looking at the Julia source code of dependencies of the VIVA program to resolve the issue.
The text was updated successfully, but these errors were encountered:
To me, that line looks invalid. GATK was known to produce VCFs that break standards, so someone should check if this issue was not caused by GATK instead (by looking at the standard and what's allowed). Since it's a line containing just package version, it should be easy to fix its format to be standard-compliant.
PS: looking at some of my VCF files - unquoted spaces are allowed, so probably the pipe character (|) is the problem. I can try making some fake VCF for testing later. Also - do bcftools handle such file?
I have had trouble when reading files with GeneticVariation.VCF.Reader that were output form the gatk tool: funcotator. When I called the function on the vcf file it threw an error. I have tried to describe this error and give a possible cause of the error below. It is a minor issue, and I resolved it by deleting a single line in my input vcf file before calling GeneticVariation.VCF.Reader which solved the problem but i wanted to draw the developers to the issue as it would be better to run it without my hack of manually deleting a line in the input vcf file :)
Expected Behavior
I took a vcf file, v4.2, that was output from funcotator and passed it to the function GeneticVariation.VCF.Reader.
Current Behavior
here is the current behavior from a live Julia session:
Possible Solution / Implementation
So I went to line 17 of the vcf file as the error log above advises, and found the following line:
Once I deleted this line, I re-ran the code:
And as you can see the problem is resolved.
Here is my issue: I cannot see what is wrong with that line ##Funcotator Version=4.2.6... Why is it not accepted as valid input?
Note, it is possible that other gatk tools insert lines like this in their vcf output files so the problem may occur in other places. (I acknowledge this may actually be an issue to raise with the gatk developers instead?)
This bug certainly affects the usability of the code. I was initially using the VIVA command line program for analyzing vcf files and received this error. so I had to go looking at the Julia source code of dependencies of the VIVA program to resolve the issue.
The text was updated successfully, but these errors were encountered: