C ritical Assessment of Genome Interpretation

Annotate all missense

Challenge: Annotate all missense

Variant data: public

Last updated: 12 October 2021

This challenge is closed.

How to participate in CAGI6? Download data & submit predictions on Synapse

Make sure you understand our Data Use Agreement and Anonymity Policy

Summary

dbNSFP currently describes 81,782,923 possible protein-altering variants in the human genome. The challenge is to predict the functional effect of every such variant. For the vast majority of these missense and nonsense variants, the functional impact is not currently known, but experimental and clinical evidence is accruing rapidly. Rather than drawing upon a single discrete dataset as typical with CAGI, predictions will be assessed by comparing with experimental or clinical annotations made available after the prediction submission date, on an ongoing basis. If predictors assent, predictions will also be incorporated into dbNSFP.

Background

Currently, dozens of in silico methods for predicting the deleteriousness of a variant are available (Hu et al. 2019). In many cases, different methods may give opposite predictions for the same variant. dbNSFP is a database of human nonsynonymous single nucleotide variants (nsSNVs) and their functional predictions and annotations (Liu et al., 2011, 2013, 2016, 2020). It compiles 37 functional prediction scores and 9 conservation scores, as well as other related information including allele frequencies observed in different large datasets, various gene IDs from different databases, functional descriptions of genes, gene expression and gene interaction information.

Prediction challenge

A list of all possible nsSNVs based on the human reference sequence was created from dbNSFP v4 (Liu et al., 2020). Predictors are asked to predict the functional effect predict each coding SNV. Since the vast majority of these nsSNVs do not have experimental information, this challenge will assess in silico predictions with new experimental or clinical annotations as they appear in literature or databases. We anticipate making regular evaluations at the time of each CAGI experiment.

Test file format

chr: Chromosome number
pos(1-based): Physical position on the chromosome as to hg38 (1-based coordinate). For mitochondrial SNV, this position refers to the rCRS (GenBank: NC_012920).
Ref: Reference nucleotide allele (as on the + strand)
Alt: Alternative nucleotide allele (as on the + strand)
aaref: Reference amino acid. "X" if the variant is a stop-loss
aaalt: Alternative amino acid. "X" if the variant is a stop-gain
hg19_chr: Chromosome as to hg19, "." means missing
hg19_pos(1-based): Physical position on the chromosome as to hg19 (1-based coordinate). For mitochondrial SNV, this position refers to a YRI sequence (GenBank: AF347015)
hg18_chr: Chromosome as to hg18, "." means missing 1
hg18_pos(1-based): Physical position on the chromosome as to hg18 (1-based coordinate). For mitochondrial SNV, this position refers to a YRI sequence (GenBank: AF347015)
Genename: Gene name; if the nsSNV can be assigned to multiple genes, gene names are separated by ";"
Cds_strand: Coding sequence (CDS) strand (+ or -)
Refcodon: Reference codon
Codonpos: Position on the codon (1, 2 or 3)
Ensembl_geneid: Ensembl gene id
Ensembl_transcriptid: Ensembl transcript ids (Multiple entries separated by ";")
Ensembl_proteinid: Ensembl protein ids. Multiple entries separated by ";", corresponding to Ensembl_transcriptids
AApos: Amino acid position with respect to protein. Multiple entires separated by “;”, corresponding to Ensembl proteinid.

Prediction submission format

The prediction submission is a tab-delimited text file. Organizers provide a file template, which should be used for submission. In addition, a validation script is provided, and predictors should check the correctness of the format before submitting their predictions.

In the submitted file, each row must include the following tab-separated fields:

chr: chromosome number
pos(1-based): physical position on the chromosome as to hg38 (1-based coordinate). For mitochondrial SNV, this position refers to the rCRS (GenBank: NC_012920).
ref: reference nucleotide allele (as on the + strand)
alt: alternative nucleotide allele (as on the + strand)
Prediction Score: Annotation score for each SNV from 0 (benign) to 1 (deleterious)
SD: standard deviation of the prediction in column 5 indicating confidence
Pred: Based on the score in column 19, indicate whether the SNV is "D(amaging)" , "T(olerated)" or "U(known)"
Comments: optional brief comment on the basis of the prediction in column

In the file, cells in columns 5-8 are marked with a "*". Submit your predictions by replacing the "*" with your value. No empty cells are allowed in the submission. You must submit predictions and standard deviation for all the variants; if you are not confident in a prediction for a variant, enter an appropriate large standard error for the prediction. Optionally, enter a brief comment on the basis of the prediction. If you do not enter a comment on a prediction, leave the "*" in those cells. Please make sure you follow the submission guidelines strictly.

In addition, your submission must include a detailed description of the method used to make the predictions, similar in style to the Methods section in a scientific article. This information will be submitted as a separate file.

If predictors assent, predictions will also be incorporated into dbNSFP. This must be explicitly specified in the document describing the method.

File naming

CAGI allows submission of up to six models per team, of which model 1 is considered primary. You can upload predictions for each model multiple times; the last submission before deadline will be evaluated for each model.

Use the following format for your submissions: <teamname>_model_(1|2|3|4|5|6).(tsv|txt)

To include a description of your method, use the following filename: <teamname>_desc.*

Example: if your team’s name is “bestincagi” and you are submitting predictions for your model number 3, your filename should be bestincagi_model_3.txt.

Related challenges