Represent ORFs on source-defined, circular and other non-Ensembl RNAs
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
Línea de trabajo
Start with the existing ReferenceORF validation against a single PyEnsembl transcript and its contiguous spliced-cDNA interval, then read the related reference and mapping issues #28, #46, #61 and #63 before proposing any model change. This is design work touching the reference-data contract, so a newcomer should first agree the representation for source RNA identity, topology and mappings with maintainers. Done means fixtures for a non-Ensembl linear transcript and a circRNA crossing its back-splice junction validate through the same path as bundled data.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
ReferenceORF currently validates against one PyEnsembl transcript and a contiguous interval of its spliced cDNA. This covers many additional ORFs on existing coding and noncoding ENSTs, but it cannot represent a source RNA absent from that annotation or a translation path crossing a circular RNA's back-splice junction.
Extend the existing reference and mapping machinery (#28/#46), coordinated with #61, so an ORF's source RNA can be represented without inventing an Ensembl transcript identity. This is a reference-data contract for Varcode/Isovar; ORFdata should not become a sample-specific transcript assembler or mutation engine.
Required behavior
- Preserve source transcript accession/version, full available RNA sequence, topology and ordered genomic mappings. Existing ENST placements retain their actual PyEnsembl transcript objects. Novel splice isoforms, retained-intron RNAs, source-defined fusions/readthrough RNAs and sequence-only references retain their own source identities and explicit links to compatible annotated transcripts.
- Support zero, one or multiple mapped genes/annotated transcripts as appropriate; distinguish a host gene from genes contributing sequence. Do not require a fake ENSG/ENST or overwrite the original RNA with its nearest annotated relative. Preserve assembly, taxon, reference release and mapping ambiguity.
- Represent a circular ORF with its explicit back-splice junction, start and ordered translation traversal, including a stop reached after crossing the junction. A stopless repeated traversal must remain an explicitly unbounded/partially observed product, not an arbitrarily truncated protein presented as complete. Linearize for an operation only with a reversible mapping and a stated origin.
- Preserve edited-RNA bases and complex/fusion segment mappings separately from the genomic reference. Query genomic variants only through validated mappings, retaining all affected RNA positions. Sequence-only references remain representable but cannot support a genomic consequence until mapped.
- Return native ORF/RNA/mapping objects through the same public contract. Explicitly report missing mappings and unsupported topology when a consumer cannot calculate an effect; do not discard records during import. User-supplied reference models should use the same validation path as bundled data.
Acceptance
Add pinned source-backed fixtures for a non-Ensembl linear transcript and a translated circRNA crossing its junction, plus focused cases for retained introns, multiple-gene source RNAs, ambiguous and sequence-only mappings. Test strand, traversal order, junction identity, version/reference isolation and serialization. Consumer tests must prove ordinary linear coding effects still work and unsupported nonlinear effects are visible. Do not copy experimental support from a source isoform to another merely sequence-compatible placement.
Source leads: Yang et al., circRNA translation and Fan et al., IRES-like elements and circRNA translation. These establish relevant source classes; individual endogenous ORF coordinates and products still require source qualification. Use GENCODE terminology for readthrough and retained-intron annotations. Coordinate IRES-derived products with #63.
- Lenguaje dominante
- Python
- Estrellas
- 1
- Forks
- 1
- Merge medio
- 10 h 11 min
- PR fusionados (30 d)
- 51
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de openvax/orfdata
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
openvax/orfdata#194 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
Los mantenedores suelen responder en 1 día
Todos los issues de openvax/orfdata
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pearu/agent-sandbox#451 ·
Los mantenedores suelen responder en 1 día
-
run_gate loads a custom tasks file from outside the working directoryPosiblemente ocupada @Ru0k3 la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
MakazhanAlpamys/Soup#3189 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
review developer setup docAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
NYCPlanning/data-engineering#2996 ·
Los mantenedores suelen responder en 1 día