[ensembl-dev] VEP check existing.

[Guillermo Marco Puche]

You're right.
I'm sorry.

On 05/23/2013 09:50 AM, Duarte Molha wrote:
>
> Sorry to be frank Guillermo, but don't you think that is something you 
> can quick find out without asking the dev forum?
>
> Especially since there is a field on the output called 
> "Existing_variation"!
>
> If the variation has multiple names each ID is comma separated.
>
> Best regards
>
>
> Duarte
>
> *From:*dev-bounces at ensembl.org [mailto:dev-bounces at ensembl.org] *On 
> Behalf Of *Guillermo Marco Puche
> *Sent:* 23 May 2013 07:29
> *To:* Ensembl developers list
> *Subject:* Re: [ensembl-dev] VEP check existing.
>
> What's the field name on output?
>
> On 05/22/2013 06:50 PM, Duarte Molha wrote:
>
>     In that case the field remains empty or with a dash of the fields
>     is part of the main annotation fields (the default behavior)
>
>     On 22 May 2013 16:45, "Guillermo Marco Puche"
>     <guillermo.marco at sistemasgenomicos.com
>     <mailto:guillermo.marco at sistemasgenomicos.com>> wrote:
>
>     In case it doesn't exist what's the behavior then?
>
>     On 05/22/2013 05:20 PM, Duarte Molha wrote:
>
>         It does exactly that ... it checks Ensembl to find out if the
>         variation you are annotation has already been added to the
>         database (ie has a RS id identifier)
>
>
>         =========================
>              Duarte Miguel Paulo Molha
>
>         http://about.me/duarte
>         =========================
>
>         On Wed, May 22, 2013 at 4:09 PM, Guillermo Marco Puche
>         <guillermo.marco at sistemasgenomicos.com
>         <mailto:guillermo.marco at sistemasgenomicos.com>> wrote:
>
>         Hello,
>
>         I'm a bit in doubt with the follow VEP option, --check_existing.
>
>         I'm not really sure what it does. I've read the description
>         like a hundred times and i'm still confused. If someone could
>         explain this in detail it would be awesome.
>
>
>         Thank you.
>
>         Best regards,
>         Guillermo.
>
>
>         _______________________________________________
>         Dev mailing list Dev at ensembl.org <mailto:Dev at ensembl.org>
>         Posting guidelines and subscribe/unsubscribe info:
>         http://lists.ensembl.org/mailman/listinfo/dev
>         Ensembl Blog: http://www.ensembl.info/
>
>
>
>
>     _______________________________________________
>     Dev mailing list Dev at ensembl.org <mailto:Dev at ensembl.org>
>     Posting guidelines and subscribe/unsubscribe info:
>     http://lists.ensembl.org/mailman/listinfo/dev
>     Ensembl Blog: http://www.ensembl.info/
>
>
>
>
>     _______________________________________________
>
>     Dev mailing listDev at ensembl.org  <mailto:Dev at ensembl.org>
>
>     Posting guidelines and subscribe/unsubscribe info:http://lists.ensembl.org/mailman/listinfo/dev
>
>     Ensembl Blog:http://www.ensembl.info/
>
>
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info: http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20130523/e126a111/attachment.html>