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
The dbNSFP annotation set will in some cases have values for all or only a subset of the known transcripts. Is there a way to limit retrieval of annotations to a single transcript, or to predict the order of the lists?
For example, for the variant NM_000546.6(TP53):c.833C>G I would like the REVEL and Alphamissense annotations. From the dbNSFP data set we can see the these annotations are available only a different subset of the transcripts - see attached text file dbNSFP_query.txt
If I want values only for ENST00000269305 (the 9th item in the list) is there a way to limit the search to only that transcript? Alternatively (and ideally) could the list order be maintained with empty fields e.g:
The dbNSFP annotation set will in some cases have values for all or only a subset of the known transcripts. Is there a way to limit retrieval of annotations to a single transcript, or to predict the order of the lists?
For example, for the variant NM_000546.6(TP53):c.833C>G I would like the REVEL and Alphamissense annotations. From the dbNSFP data set we can see the these annotations are available only a different subset of the transcripts - see attached text file dbNSFP_query.txt
I can use this query to retrieve the values:
https://myvariant.info/v1/variant/chr17:g.7673787G%3EC?assembly=hg38&fields=dbnsfp.revel,dbnsfp.alphamissense,dbnsfp.ensembl.transcriptid
But the output lists have 19 values (transcripts), 16 values (alphamissense.score) and 6 values (revel.score), without an obvious order:
If I want values only for ENST00000269305 (the 9th item in the list) is there a way to limit the search to only that transcript? Alternatively (and ideally) could the list order be maintained with empty fields e.g:
"score": [0.951,0.951,0.951,0.951,0.951,.,.,.,0.951,.,.,.,.,.,.,.,.,.,]
The text was updated successfully, but these errors were encountered: