Represent recoded translation paths, readthrough and programmed frameshifts

Abierto
#65 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo

Línea de trabajo

Start with the ReferenceORF binder, which the issue says assumes one contiguous coding slice and a translation equal to protein plus stop, and read #61's consumer contract, since this extends it. Design the ordered translation-path representation before touching code, and check how #57 and #63 constrain it. Done means pinned readthrough, programmed frameshift and selenocysteine examples with exact source protein and residue-to-RNA mapping, plus wrong-event rejection and lossless round trips.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

The current ReferenceORF binder requires its coding positions to be one contiguous slice of spliced cDNA and requires ordinary table translation to equal protein_sequence + "*". That is a useful fast path, but it cannot describe every source-supported translation product. Changing the organism's genetic code is not a substitute for a local recoding event.

Extend #61's consumer contract to retain and, where supported, interpret source-defined recoding without forcing it into an incorrect ordinary ORF. Keep #57 for genetic-code support and coordinate with IRES-linked products in #63.

Required behavior

  • Represent stop-codon readthrough, programmed ribosomal frameshifts and codon-specific amino-acid exceptions such as selenocysteine with their source identity, positions, event parameters, evidence and relevant cis-acting features. Preserve the ordinary terminated product and readthrough product as distinct source-supported alternatives when both are reported.
  • Preserve an ordered translation path and enough codon-to-RNA/genome mapping to handle skipped or reused bases, split codons and frame changes. Do not fake an exon deletion or mutation to make the sequence satisfy an ordinary uninterrupted-frame validator. Keep the simple complete-ORF path simple; choose the smallest extension that preserves the exceptional cases.
  • Distinguish source-specified reference recoding from a frameshift or stop change caused by the patient's variant. Retain the reference event even when Varcode cannot yet simulate its altered outcome. Unknown recoded residues stay unknown; do not silently translate through every stop or substitute a generic code table.
  • Keep RNA editing as an explicit source-to-translated-RNA relationship rather than a codon-table override. Preserve reference and edited bases with provenance. Likewise, retain any source-supported ribosome-skipping event separately from proteolytic processing.
  • Expose translation requirements and available mappings directly. Varcode needs to distinguish an ordinary coding consequence, overlap with a recoding signal, and a consequence requiring unsupported recoding semantics. Reference evidence does not prove that a variant preserves the event or changes its efficiency.

Acceptance

Pin one real example each of stop readthrough, programmed frameshifting and selenocysteine; require exact source protein and residue-to-RNA mapping where the source defines them. Include variants before/at/after the event, strand/splice cases, wrong-event rejection and lossless round trips. Before claiming end-to-end support, verify that Varcode preserves the translation instructions; otherwise return an explicit unsupported calculation while retaining the reference record.

Terminology must distinguish stop-codon readthrough from a readthrough transcript spanning loci, and a source-programmed frameshift from a mutation-induced frameshift. GENCODE tags distinguish these annotations. INSDC CDS qualifiers include ribosomal_slippage, transl_except and RNA-editing exceptions; retain their meaning rather than inventing incompatible categories.

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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openvax/orfdata

Todos los issues de openvax/orfdata

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.