Represent recoded translation paths, readthrough and programmed frameshifts

未关闭
#65 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
1
派生
1
平均合并
10 小时 11 分钟
30 天内合并 PR
51

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

openvax/orfdata 的其他 Issue

查看 openvax/orfdata 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。