[ensembl-dev] EFG array mapping environment probe2transcript fails looking for transcript_stable_id table

[Nathan Johnson]

Hi Gavin

Please be patient when using the dev list and always keep the conversation on the list, un-invited off list contact is unacceptable (see posting guidelines attached).

wrt the error you have found, it seems that this fix has been hanging around in my local repository for a while and missed check in for some reason.  I have now checked in the updated methods on the head. You can try checking out the head code and simply copying the Helper.pm to your v67 checkout. 

Thanks

Nathan Johnson
Senior Scientific Programmer
Ensembl Regulation
European Bioinformatics Institute
Wellcome Trust Genome Campus
Hinxton
Cambridge CB10 1SD

http://www.ensembl.info/
http://twitter.com/#!/ensembl


Ensembl dev posting guidelines

The Ensembl dev mailing list (dev at ensembl.org) is a forum for users of the 
Ensembl API, website and data including users maintaining Ensembl mirrors
or developing applications based on the Ensembl code.  All API/web installation 
questions, issues, possible bugs or other Ensembl code related queries are 
appropriate for this forum.  

Please keep in mind that many of the users posting here are volunteering 
their expertise.  While help is happily provided, there is an expectation that users
will spend the necessary time learning the system from the available documentation.


General information:

- Before posting users are encouraged to search the dev list archives at 
http://lists.ensembl.org/pipermail/dev/.  Additional information including
specific help for the API and a project FAQ are available at 
http://www.ensembl.org/info/index.html

- Choose a meaningful subject for your message.

- Ensembl also provides user support via helpdesk at ensembl.org.  
Questions sent to this address are not sent to the general dev list, but may be
used as the basis of FAQ entries, blog posts or other documentation.


How to format specific question types:

- If you are posting a question about the Ensembl API, please provide the
API version that you are using, which is found via Bio::EnsEMBL::ApiVersion

  use Bio::EnsEMBL::ApiVersion;
  printf( "The API version used is %s\n", software_version() );

A short code snippet illustrating a problem is normally very useful.

- Questions about installation of an Ensembl web site should include
information about the OS used and any applicable error messages.

- Questions about Ensembl data should include the release number.
Database version can be found in the database name or via the
schema_version entry in the meta table.


Administrative guidelines:

- Please keep messages on the list so that others can benefit from the
discussion.  All Ensembl team members will reply with the dev list in copy and
dev messages should not be sent directly to members of the
Ensembl team.

- Normal standards of professional behaviour are expected in all messages.  
Comments that are deemed rude or insulting are not acceptable.

- Uninvited off-list contact for commercial or other purposes is not acceptable.

- Messages sent to dev at ensembl.org will be archived.  These are indexed and
searchable via sources such as google.

- Job postings for Ensembl project positions at the EBI and Sanger may be
occasionally be sent to the list.  Other jobs postings are not appropriate for the list.





On 11 Jul 2012, at 10:53, Oliver, Gavin wrote:

> Hi Nathan,
> 
> Sorry to contact you directly but I am not having much luck on the mailing list.
>  
> I am leaving Almac in a couple of weeks (off to the Mayo Clinic) and have been asked to update our array annotations before I go.  I have not updated the annotations/APIs etc since v60 and am now trying to update to v67.
>  
> I have got as far as the RunTranscriptXrefs stage but then it is failing when the Helper.pm module looks for the transcript_stable_id table which appears to have been removed from the core schema after v64.
>  
> Are there any known issues with the current API version?
>  
> Best,
>  
> Gavin
>  
>  
>  
> The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender.
>  
> Almac Group (UK) Limited, registered no. NI061368.  Almac Sciences Limited, registered no. NI041550.  Almac Discovery Limited, registered no. NI046249.  Almac Pharma Services Limited, registered no. NI045055.  Almac Clinical Services Limited, registered no. NI041905.  Almac Clinical Technologies Limited, registered no. NI061202.  Almac Diagnostics Limited, registered no. NI043067. All preceding companies are registered in Northern Ireland with a registered office address of Almac House, 20 Seagoe Industrial Estate, Craigavon, BT63 5QD, UK.  
>  
> Almac Sciences (Scotland) Limited, registered in Scotland no. SC154034.
>  
> Almac Clinical Services LLC, Almac Clinical Technologies LLC and Almac Diagnostics LLC areDelaware limited liability companies and Almac Group Incorporated is a Delaware Corporation.  More information on the Almac Group can be found on the Almac website: www.almacgroup.com







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20120711/ffec7c90/attachment.html>