> I cannot imagine that this it would be possible for an exon to project > out beyond a transcription region.
I could imagine it happening occasionally as an annotation error. > transcript = ensembl_gene_db[transcript_id] > > exon5 = transcript.exons[5] > print exon5.start, exon5.stop > > would be easy to make work and to have the 'start' and 'stop' be generated > dynamically upon request (last line). > > Is this the sort of thing we need? The UCSC known gene table also encodes exon information as two blobs of comma seperated lists. I think it is a common pattern for their database schema. When I've been using it I usually split all the exons out into an NLMSA and mostly ignore the start stop locations in the annotation table. (On the other hand I barely know how to use pygr). Diane
pgpOlHJVt9pDx.pgp
Description: PGP signature
