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

Aperta
#15 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python, sql

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
1
Fork
1
Merge medio
10h 11m
PR unite (30g)
51

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openvax/orfdata

Tutte le issue di openvax/orfdata

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.