<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi David,<div class=""><br class=""></div><div class="">Hope you’re well. We’ve had a chat about this issue yesterday, unfortunately this is not something that we currently support, or could provide a quick fix for. However, we will be providing improvements to our protein annotations within the coming months, and we will keep this suggestion in mind if we feel this is something we could implement in the future. </div><div class=""><br class=""></div><div class="">The easiest solution, as we see it, would be to run VEP on both files and compare the HGVSp outputs at the end.</div><div class=""><br class=""></div><div class="">Kind Regards,</div><div class="">Andrew<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 15 Mar 2019, at 18:13, David Tamborero <<a href="mailto:david.tamborero@gmail.com" class="">david.tamborero@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">Thanks! Have a great weekend </div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El vie., 15 mar. 2019 18:31, Andrew Parton <<a href="mailto:aparton@ebi.ac.uk" class="">aparton@ebi.ac.uk</a>> escribió:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi David,<br class="">
<br class="">
Thanks for the suggestion, we’ve had similar queries to this before. I’ll discuss it with the team on Monday and get back to you.<br class="">
<br class="">
Kind Regards,<br class="">
Andrew<br class="">
<br class="">
> On 15 Mar 2019, at 14:01, David Tamborero <<a href="mailto:david.tamborero@gmail.com" target="_blank" rel="noreferrer" class="">david.tamborero@gmail.com</a>> wrote:<br class="">
> <br class="">
> I received a weird @vep email, and now i m unsure of whether this was published (cannot see it in the archive), so I send it again. Apologies if this is not the case.<br class="">
> <br class="">
> =<br class="">
> <br class="">
> Hello there,<br class="">
> <br class="">
> I m writing with further VEP whishes! The context is that I m matching the variants given to VEP with the content of a given database(s) that report variant effects (e.g. biomarkers of drug response). I m currently passing these knowledgebases to VEP as a vcf (with the corresponding .tbi) with the --custom flag, which works lovely.<br class="">
> <br class="">
> The thing is that I m also interested to have a match when the nucleotide change of the input variant is not the same than the one from the database *but* it leads to the same aminoacid change; something like:<br class="">
> <br class="">
> database: chr1:xxxxxA>C (geneX p.V28E)<br class="">
> <br class="">
> input: chr1xxxxxxA>C (geneX p.V28E) produces a 'perfect match'<br class="">
> input: chr1yyyyyyyG>T (geneX p.V28E) produces an 'aminoacid match'<br class="">
> <br class="">
> My plan is to keep using your --custom flag to retrieve the 'perfect' match and then to have my own script to retrieve the 'aminoacid match'. However, as you know, this is kind of a hassle (need to map the variants of the original databases with VEP to ensure that the protein statements are fully compatible, and I need to do it each time there is an update etc etc).<br class="">
> <br class="">
> In other words, it would be more neat and easy if this 'aminoacid match' is provided by VEP given the --custom vcf file(s). By any chance, do you have some option (that I did not see) that magically does it, or any option that you can implement this in some incoming release?<br class="">
> <br class="">
> (as for other requests, I think that this is a feature that would be useful for other users)<br class="">
> <br class="">
> Thanks a lot in advance!<br class="">
> br<br class="">
> _______________________________________________<br class="">
> Dev mailing list <a href="mailto:Dev@ensembl.org" target="_blank" rel="noreferrer" class="">Dev@ensembl.org</a><br class="">
> Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" rel="noreferrer noreferrer" target="_blank" class="">http://lists.ensembl.org/mailman/listinfo/dev</a><br class="">
> Ensembl Blog: <a href="http://www.ensembl.info/" rel="noreferrer noreferrer" target="_blank" class="">http://www.ensembl.info/</a><br class="">
<br class="">
_______________________________________________<br class="">
Dev mailing list <a href="mailto:Dev@ensembl.org" target="_blank" rel="noreferrer" class="">Dev@ensembl.org</a><br class="">
Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" rel="noreferrer noreferrer" target="_blank" class="">http://lists.ensembl.org/mailman/listinfo/dev</a><br class="">
Ensembl Blog: <a href="http://www.ensembl.info/" rel="noreferrer noreferrer" target="_blank" class="">http://www.ensembl.info/</a><br class="">
</blockquote></div>
_______________________________________________<br class="">Dev mailing list <a href="mailto:Dev@ensembl.org" class="">Dev@ensembl.org</a><br class="">Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" class="">http://lists.ensembl.org/mailman/listinfo/dev</a><br class="">Ensembl Blog: <a href="http://www.ensembl.info/" class="">http://www.ensembl.info/</a><br class=""></div></blockquote></div><br class=""></div></body></html>