[ensembl-dev] Two caches and two versions of VEP
Eva Goncalves Serra
egs at sanger.ac.uk
Thu Jun 25 09:42:11 BST 2015
Thanks Will, this makes sense. Will have the two versions in parallel.
Cheers,
Eva
From: Will McLaren <wm2 at ebi.ac.uk<mailto:wm2 at ebi.ac.uk>>
Reply-To: Ensembl developers list <dev at ensembl.org<mailto:dev at ensembl.org>>
Date: Wednesday, 24 June 2015 17:16
To: Ensembl developers list <dev at ensembl.org<mailto:dev at ensembl.org>>
Subject: Re: [ensembl-dev] Two caches and two versions of VEP
Hi Eva,
Assuming you use INSTALL.pl to set everything up, the easiest thing to do would be to maintain two VEP versions in different directories. The underlying API is installed within that directory when you run INSTALL.pl, so won't be affected by running INSTALL.pl in another directory with a different version of the code.
The different cache versions will happily sit alongside each other in the same location as they are versioned.
You could in theory try running v75 code with a v80 cache, but I wouldn't be surprised if you encountered problems.
Regards
Will McLaren
Ensembl Variation
On 24 June 2015 at 16:47, Eva Goncalves Serra <egs at sanger.ac.uk<mailto:egs at sanger.ac.uk>> wrote:
Hi,
I have VEP v75 and cache v75 installed, however for another analysis I want to run VEP v80 (so GRCh38.p2). My question is: can I use the VEP script from version v75 and just download the v80 cache data or do I need to install the newest version of VEP v80 as well? And if that is the case, will that change my previous installation of v75 or will I be able to have both available?
Cheers,
Eva
_______________________________________________
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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20150625/dc722eea/attachment.html>
More information about the Dev
mailing list