Expand the viral CDS catalogue across GDC HPV types and qualified HPV lineages

Abierto
#93 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
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python

Línea de trabajo

This is a large design-level import, so read the parent issues #91 and #92 and the existing HPV16 nine-CDS seed catalogue first to learn the format and native models. Check the GDC inventory file and PaVE reference genomes to see how each entry's sequence is qualified against its annotation source. Done means every GDC HPV entry has an explicit coverage status, with source hashes, and the listed tests pass. Start with a narrow slice, such as one qualified type, rather than the full 189 entries.

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

Descripción

Family import under https://github.com/openvax/orfdata/issues/91, following https://github.com/openvax/orfdata/issues/92.

Cover all 189 HPV entries in the historical GDC inventory, then provide a separately versioned expansion for clinically relevant types and within-type lineages/strains. HPV type and within-type strain/lineage are different identities. Prioritize cancer-associated mucosal types using source-backed evidence; inclusion in GDC alone is not a carcinogenicity classification.

Sources: PaVE reference genomes and transcript maps, versioned RefSeq/GenBank records, and the GDC inventory. Some GDC entries are marked revised or lack versioned RefSeq IDs; qualify each actual sequence against the annotation source rather than copying offsets by type name.

Acceptance:

  • Reuse the seed catalogue format/native models and offline installation. Publish source release/date, accession.version, taxon/type/lineage and exact sequence hashes per entry.
  • Preserve supported alternative initiation and joined CDS paths as distinct source definitions; do not infer complete transcript boundaries from coding fragments or transfer one type's splice model to another.
  • Check source translations and circular-coordinate placements per reference. Represent source disagreement and unavailable models explicitly; give every GDC HPV entry an honest coverage status.
  • Keep additional curated ORFs distinct from the nine-CDS RefSeq HPV16 seed and retain their primary evidence. Document where source annotations are incomplete.
  • Test several independently qualified types, a within-type alternate reference, conflicting source placements and a type with missing annotation. Identical proteins may group for reporting while retaining their original RNA/reference occurrences.

Use #64/#66 for any remaining initiation or source-RNA limitations, #70/#71 for selection/composition. Isovar will apply these definitions to observed sample paths; this issue does not add read screening or assembly to ORFdata.

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.