-
Notifications
You must be signed in to change notification settings - Fork 45
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
Valid SNPIDs missing in vcf file #221
Comments
Sorry a typo. Not basecalling but variant calling, of course. |
Hi @matomol, apologies for the delay in responding. Please can you provide a bit more information so I can assist you better - by 'snpid', do you mean the dbSNP identifier? We perform annotation with SnpEff as follows: first to add basic annotations, and then to annotate using ClinVar. The ClinVar VCF we use is out of date so we are in the process of updating that, but there won't be any dbSNP/rsIDs in the output VCFs as we are not using this dataset to annotate. |
Please find below the summary that I did for just one gene, LDLR. A similar statistics is prepared for all the genes on the Illumina Panel once we succeded to lift it over successfully.
Correctly annotated and with SNPID attached are only the two following SNPs in that region tested
The following SNPIDs where correctly found by Illumina and Nanopore, but only Illumina attached the correct SNPID.
Lastly, this SNP was not detected by Nanopore.
|
Operating System
Ubuntu 22.04
Other Linux
No response
Workflow Version
latest
Workflow Execution
Command line (Local)
Other workflow execution
No response
EPI2ME Version
No response
CLI command run
Workflow Execution - CLI Execution Profile
standard (default)
What happened?
I performed an analysis of the snp.vcf file and realized that although the variantes are correctly annotated the SNPID is missing. This is in particular true for SNPID with higher numbers, so that I assume that an outdated SNP reference database is used.
Relevant log output
Application activity log entry
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
The text was updated successfully, but these errors were encountered: