Open Aisha-D opened 5 months ago
Example of custom annotation order swapped:
ocker run -v /home/dnanexus:/opt/vep/.vep ensemblorg/ensembl-vep:release_103.1 ./vep -i /opt/vep/.vep/128858722-24079Q0066-24NGSHO12-8128-U-96527893_markdup_recalibrated_tnhaplotyper2_split.vcf -o /opt/vep/.vep/128858722-24079Q0066-24NGSHO12-8128-U-96527893_markdup_recalibrated_tnhaplotyper2_split_filevep.vcf --vcf --cache --refseq --exclude_predicted --symbol --hgvs --af_gnomad --check_existing --variant_class --numbers --offline
--custom /opt/vep/.vep/clinvar_20240317_hg38_withchr.vcf.gz,ClinVar,vcf,exact,0,CLNSIG,CLNREVSTAT,CLNDN
--custom /opt/vep/.vep/novaseq_205samples_211007.vcf.gz,Prev,vcf,exact,0,AC,NS
--custom /opt/vep/.vep/CosmicNonCodingVariants_GRCh38_v99.normal.vcf.gz,COSMIC,vcf,exact,0,ID
--custom /opt/vep/.vep/CosmicCodingMuts_GRCh38_v99.normal.vcf.gz,COSMIC,vcf,exact,0,ID --plugin CADD,/opt/vep/.vep/./in/vep_refs/whole_genome_SNVs.tsv.gz,/opt/vep/.vep/./in/vep_refs/gnomad.genomes.r3.0.indel.tsv.gz --fields SYMBOL,VARIANT_CLASS,Consequence,EXON,HGVSc,HGVSp,gnomAD_AF,CADD_PHRED,Existing_variation,ClinVar,ClinVar_CLNDN,ClinVar_CLNSIG,COSMIC,Prev_AC,Prev_NS,Feature
##INFO=COSMIC,Number=.,Type=String,Description="/opt/vep/.vep/CosmicNonCodingVariants_GRCh38_v99.normal.vcf.gz (exact)">
##INFO=COSMIC_ID,Number=.,Type=String,Description="ID field from /opt/vep/.vep/CosmicNonCodingVariants_GRCh38_v99.normal.vcf.gz">
Hi @Aisha-D, I can reproduce the issue - thanks for reporting it. We are looking for a solution.
Best wishes, Diana
The issue is in your command. In the custom annotation you use the same short name (COSMIC) for both cosmic annotations:
--custom /opt/vep/.vep/CosmicNonCodingVariants_GRCh38_v99.normal.vcf.gz,COSMIC,vcf,exact,0,ID
--custom /opt/vep/.vep/CosmicCodingMuts_GRCh38_v99.normal.vcf.gz,COSMIC,vcf,exact,0,ID --plugin CADD,/opt/vep/.vep/./in/vep_refs/whole_genome_SNVs.tsv.gz,/opt/vep/.vep/./in/vep_refs/gnomad.genomes.r3.0.indel.tsv.gz --fields SYMBOL,VARIANT_CLASS,Consequence,EXON,HGVSc,HGVSp,gnomAD_AF,CADD_PHRED,Existing_variation,ClinVar,ClinVar_CLNDN,ClinVar_CLNSIG,COSMIC,Prev_AC,Prev_NS,Feature
This name has to be unique, if you change the names to COSMICNonCoding
and COSMICCoding
the output returns both files info correctly.
--custom /opt/vep/.vep/CosmicNonCodingVariants_GRCh38_v99.normal.vcf.gz,COSMICNonCoding,vcf,exact,0,ID
--custom /opt/vep/.vep/CosmicCodingMuts_GRCh38_v99.normal.vcf.gz,COSMICCoding,vcf,exact,0,ID --plugin CADD,/opt/vep/.vep/./in/vep_refs/whole_genome_SNVs.tsv.gz,/opt/vep/.vep/./in/vep_refs/gnomad.genomes.r3.0.indel.tsv.gz --fields SYMBOL,VARIANT_CLASS,Consequence,EXON,HGVSc,HGVSp,gnomAD_AF,CADD_PHRED,Existing_variation,ClinVar,ClinVar_CLNDN,ClinVar_CLNSIG,COSMIC,Prev_AC,Prev_NS,Feature
Let me know if you have more questions.
Best wishes, Diana
Hi Diana, Thanks for looking into this. We resolved the issue but was hoping rather than overriding the data if the same name was used to instead raise an error.
That makes sense. We will update VEP in the future to check if there are any duplicated names.
Best wishes, Diana
Describe the issue
If two custom annotations with the same name are provided, vep will annotate the VCF using first custom annotation and ignore the second annotation source. Expectation was an error to be raised (to require clarification to differentiate the two annotation sources).
Example of command and VCF header output:
System