support transcripts with >1 CDS?

Ouverte
#3 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
r
Domaine
bioinformatics

Piste de recherche

Reproduce the issue with the example GFF3 data using makeTxDbFromGFF, then inspect .find_exon_cds and the warning about multiple CDSs per exon. Done means the resulting cds() output retains all CDS annotations, including edenprotein.4, without dropping entries.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

hi there,

I am working on a viral genome, where the annotations (based on ribosome profiling) fairly often include >1 CDS per exon. Using makeTxDbFromGFF means that some of these CDSs get dropped with a warning The following transcripts have exons that contain more than one CDS (only the first CDS was kept for each exon). I'd like to be able to keep all the CDSs.

I'm not sure if this website is what determines 'official' gff3 specs, but it suggests that >1 CDS per exon should be allowed:
https://github.com/The-Sequence-Ontology/Specifications/blob/master/gff3.md

Any change that makeTxDbFromGFF could support >1 CDS per exon? Not sure how tricky that would be. Example data below, from the website linked above.

Thanks!

Janet

Here's the example gff file from that page:

##gff-version 3
##sequence-region ctg123 1 1497228
ctg123	.	gene	1000	9000	.	+	.	ID=gene00001;Name=EDEN
ctg123	.	TF_binding_site	1000	1012	.	+	.	ID=tfbs00001;Parent=gene00001
ctg123	.	mRNA	1050	9000	.	+	.	ID=mRNA00001;Parent=gene00001;Name=EDEN.1
ctg123	.	mRNA	1050	9000	.	+	.	ID=mRNA00002;Parent=gene00001;Name=EDEN.2
ctg123	.	mRNA	1300	9000	.	+	.	ID=mRNA00003;Parent=gene00001;Name=EDEN.3
ctg123	.	exon	1300	1500	.	+	.	ID=exon00001;Parent=mRNA00003
ctg123	.	exon	1050	1500	.	+	.	ID=exon00002;Parent=mRNA00001,mRNA00002
ctg123	.	exon	3000	3902	.	+	.	ID=exon00003;Parent=mRNA00001,mRNA00003
ctg123	.	exon	5000	5500	.	+	.	ID=exon00004;Parent=mRNA00001,mRNA00002,mRNA00003
ctg123	.	exon	7000	9000	.	+	.	ID=exon00005;Parent=mRNA00001,mRNA00002,mRNA00003
ctg123	.	CDS	1201	1500	.	+	0	ID=cds00001;Parent=mRNA00001;Name=edenprotein.1
ctg123	.	CDS	3000	3902	.	+	0	ID=cds00001;Parent=mRNA00001;Name=edenprotein.1
ctg123	.	CDS	5000	5500	.	+	0	ID=cds00001;Parent=mRNA00001;Name=edenprotein.1
ctg123	.	CDS	7000	7600	.	+	0	ID=cds00001;Parent=mRNA00001;Name=edenprotein.1
ctg123	.	CDS	1201	1500	.	+	0	ID=cds00002;Parent=mRNA00002;Name=edenprotein.2
ctg123	.	CDS	5000	5500	.	+	0	ID=cds00002;Parent=mRNA00002;Name=edenprotein.2
ctg123	.	CDS	7000	7600	.	+	0	ID=cds00002;Parent=mRNA00002;Name=edenprotein.2
ctg123	.	CDS	3301	3902	.	+	0	ID=cds00003;Parent=mRNA00003;Name=edenprotein.3
ctg123	.	CDS	5000	5500	.	+	1	ID=cds00003;Parent=mRNA00003;Name=edenprotein.3
ctg123	.	CDS	7000	7600	.	+	1	ID=cds00003;Parent=mRNA00003;Name=edenprotein.3
ctg123	.	CDS	3391	3902	.	+	0	ID=cds00004;Parent=mRNA00003;Name=edenprotein.4
ctg123	.	CDS	5000	5500	.	+	1	ID=cds00004;Parent=mRNA00003;Name=edenprotein.4
ctg123	.	CDS	7000	7600	.	+	1	ID=cds00004;Parent=mRNA00003;Name=edenprotein.4

And here's the warning - we lose the edenprotein.4 annotation

library(txdbmaker)
example_txdb <- makeTxDbFromGFF(file="~/Desktop/example.gff3")
# Import genomic features from the file as a GRanges object ... OK
# Prepare the 'metadata' data frame ... OK
# Make the TxDb object ... OK
# Warning message:
#     In .find_exon_cds(exons, cds) :
#     The following transcripts have exons that contain more than one CDS (only the
#     first CDS was kept for each exon): mRNA00003

cds(example_txdb, use.names=TRUE)
# GRanges object with 10 ranges and 1 metadata column:
#               seqnames    ranges strand |    cds_id
#                   <Rle> <IRanges>  <Rle> | <integer>
#  edenprotein.1   ctg123 1201-1500      + |         1
#  edenprotein.2   ctg123 1201-1500      + |         2
#  edenprotein.1   ctg123 3000-3902      + |         3
#  edenprotein.3   ctg123 3301-3902      + |         4
#  edenprotein.1   ctg123 5000-5500      + |         5
#  edenprotein.2   ctg123 5000-5500      + |         6
#  edenprotein.3   ctg123 5000-5500      + |         7
#  edenprotein.1   ctg123 7000-7600      + |         8
#  edenprotein.2   ctg123 7000-7600      + |         9
#  edenprotein.3   ctg123 7000-7600      + |        10
Langage dominant
R
Étoiles
5
Forks
2
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Bioconductor/txdbmaker

Toutes les issues de Bioconductor/txdbmaker

Issues similaires

Plus d'issues R

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.