[ensembl-dev] Running API scripts against old releases

Javier Herrero jherrero at ebi.ac.uk
Tue Jan 31 09:15:37 GMT 2012


Hi Simon

The lastest release for NCBI36 was e54!. I'd strongly recommend you use 
the API v.54 for this. The main methods haven't changes dramatically and 
it might be that the script works for 54 and 65 out of the box or with 
very few changes. However, you should use the API version that 
corresponds to the database you want to use.

To get the old API version, I'd recommend to use our public CVS server:

cvs -d :pserver:cvsuser at cvs.sanger.ac.uk:/cvsroot/ensembl checkout -r branch-ensembl-54 ensembl-api

I hope this helps

Javier

On 31/01/12 08:56, simon andrews (BI) wrote:
> I would like to run a Ensembl API script against quite an old release (whatever the last human release was which used the NCBI36 assembly).  I have the latest API code downloaded, but I'm guessing that it's not just going to be a case of making a registry change and pressing go.
>
> What is the recommended way to run automated queries against releases which are as old as this?
>
> Cheers
>
> Simon.
>
> --
>
>
>
>
> The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT Registered Charity No. 1053902.
> The information transmitted in this email is directed only to the addressee. If you received this in error, please contact the sender and delete this email from your system. The contents of this e-mail are the views of the sender and do not necessarily represent the views of the Babraham Institute. Full conditions at: www.babraham.ac.uk<http://www.babraham.ac.uk/email_disclaimer.html>
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> List admin (including subscribe/unsubscribe): http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/
>

-- 
Javier Herrero, PhD
Ensembl Coordinator and Ensembl Compara Project Leader
European Bioinformatics Institute (EMBL-EBI)
Wellcome Trust Genome Campus, Hinxton
Cambridge - CB10 1SD - UK





More information about the Dev mailing list