Skip to content

[Bioc-devel] Making transcriptLength function a method in GenomicFeatures?

4 messages · Hervé Pagès, Rainer Johannes, Martin Morgan

#
Hi Johannes,

We can make transcriptLengths() a generic but isn't the situation
similar to the extractTranscriptSeqs() situation that you brought
in January 
(https://stat.ethz.ch/pipermail/bioc-devel/2016-January/008570.html) for 
which adding the ellipsis to the argument list of the
function and proper forwarding of the extra arguments did the trick?
In the case of transcriptLengths() the extra arguments would be
forwarded to the internal calls to transcripts(), exonsBy(), cdsBy(),
fiveUTRsByTranscript(), and threeUTRsByTranscript(), and so
transcriptLengths() would work out-of-the-box on EnsDb objects.
Would that work?

H.
On 04/30/2016 04:05 AM, Rainer Johannes wrote:

  
    
#
Hi Herve,

passing down additional arguments to the internal exonsBy, cdsBy, fiveUTRsByTranscript and threeUTRsByTranscript would do it! That would be great, thanks.

cheers, jo
1 day later
#
On 05/02/2016 03:46 AM, Rainer Johannes wrote:
Hi Johannes --

Lori (cc'd, a new team member) and I are working on this.

The easiest thing to do is add '...' to the transcriptLengths argument 
list, and to pass this to transcripts, exonsBy, etc.

The only obstacle is that 'tx_name' (in the call to transcripts()) plays 
a central role in TxDb, but is not supported by EnsDb. Is it reasonable 
for you to add support for tx_name as a column (maybe a simple alias to 
tx_id, so no need for schema change)?

Martin & Lori
This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
#
Dear Martin, Lori,

I?ve added support for the column ?tx_name? (which will return the transcript ID) to all ensembldb methods so that?s fine now. Apparently I was just a little late, since that is now in the devel version 1.5.1.

thanks, jo