Complete the curated TransCODE MS import and preserve sample-level peptide evidence

Abierto
#15 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, sql

Línea de trabajo

Start by reading the existing catalogue builder and its handling of peptide_sample_msrun_counts, then inspect the cited author exports and candidate tables 2–8 and 12. Audit targeted-PRM deposits separately to establish whether quantitative measurements are supplied. Done means reconciling included, excluded, and unmapped source records, preserving sample-level observations and evidence distinctions, and reporting updated catalogue counts.

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

Descripción

enhancement

The current 7,264-model catalogue imports legacy MS, author HLA mappings and community spectrum reviews, but its metadata explicitly excludes the complete curated 2026 shotgun tables. Pooled HLA spectrum counts are also insufficient for sample-level quantitative analysis.

Primary source: Deutsch et al. 2026 and author exports. Candidate tables include non-HLA peptide/ORF tables 2-3, synthetic-peptide validation table 4, HLA peptide/ORF/run tables 6-8 and annotation outcomes table 12. Audit deposited targeted-PRM data separately for any genuine quantitative measurements.

Import

Preserve source peptide/PSM/ORF confidence levels, false-discovery scope, unique/shared mappings, synthetic-spectrum validation, annotation outcomes, assay category and exact source release. A paper's annotation tier, our reviewed-spectrum flag and proof of function are different concepts.

Retain run/sample-level observations where supplied. The current builder sums peptide_sample_msrun_counts across runs; introduce the detailed observation dataset alongside that backwards-compatible summary. Link every pooled count to its contributing records and distinguish repeated spectra/runs from biological samples. Keep protein-digest abundance, HLA peptide presentation and MS detection counts separate. Import PRM intensity/ratio/calibration only if the deposit actually supplies it.

Acceptance

Reconcile source tables and published categories with explicit included/excluded/unmapped counts. Do not deduplicate distinct observations merely because their peptide sequence matches, and do not inflate biological replication by copying ambiguous mappings. Verify source-file licenses/permissions separately from article text; use author/repository data or local import where appropriate. Report updated catalogue evidence counts without treating unreviewed/missing measurements as absence or claiming all detected peptides establish functional proteins.

Roadmap: #3. Priority: P1.
Dependencies: #4, #5.

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.