Import parallel human, mouse and dog RNA/proteomics from the 2026 nonclinical atlas
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
- 15/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- postgresql, python
- Ambito
- data-engineering, databases
Direzione di ricerca
Start with dependencies #4, #5, and #6, then inspect the verified GEO and MassIVE source records and Table S5 to identify pinned processed matrices and their terms. Review the existing canine import and checked intake in pirl-unc/oncoref#583 for reusable patterns. Done means human, mouse, and dog data pass through the shared API and offline fixtures, with reconciled source values and a coverage and sample-pairing manifest.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The Oziolor et al. atlas provides a shared study framework for human, mouse and dog, with rat, minipig and cynomolgus macaque also available. It reports 2,227 RNA-seq samples and 277 proteomics samples across more than 40 tissues overall. Those totals do not imply every tissue, specimen or assay is paired.
Verified source entry points
- RNA raw data: PRJNA1376953; resolve and pin the three processed GEO submissions from the final paper's data records and Table S5.
- Proteomics: MassIVE MSV000099729 human, MSV000099754 mouse, MSV000099744 dog; the dog deposit is also PXD070290.
- Later partitions from the same source: MSV000099753 rat, MSV000099746 minipig, MSV000099734 cynomolgus macaque.
Import
Create one dataset family with separate species/reference partitions and a common assay/sample schema. Import available sample-level RNA counts/TPM and TMT protein/peptide measurements, retaining original units, transformations, protein groups, plex/channel/bridge information and normalization. Preserve original reference/annotation and animal, tissue, sex, strain/breed and replicate metadata. Map targets to the exact appropriate PyEnsembl context; unmatched targets remain explicitly unmapped.
Audit donor/specimen/aliquot relationships before producing RNA/protein pairs. Mark tissue-only overlaps as such; do not claim simultaneous measurement. TMT intensities are relative measurements, not calibrated copies per cell or automatically comparable absolute values between species or proteins. Canonical protein abundance is not evidence for a nearby ncORF.
Acceptance
Publish a coverage and sample-pairing manifest for human/mouse/dog, with at least one real-data slice per species through the same API and offline fixture. Reconcile source row counts and representative numeric values. Record which processed matrices are public and their file-level terms independently of the article license; pin final-version inputs/checksums. Keep rat/pig/macaque easy to enable through metadata, without requiring those releases for the first three-species import.
Concrete canine extraction and delivery
- #23 — Bounded, provenance-checked extraction of Pfizer peptide/protein-group evidence. Prefer summarized exports and use the verified FTPS offset-read route if vendor extraction is needed; a full 86 GB local download is not an established prerequisite.
- #24 — Compact versioned canine protein-summary artifact shipped via #32 in release
2026-10-12.1(84.4 MB download; about 1.40 GB installed). Complete underlying peptide/group enrichment remains #23. - #38 — Expose complete pinned searched sequence assets and membership queries for downstream consumers.
- #39 — Add exact native unit/scale selectors across the common query API; coordinate storage/query benchmarks with #36.
The existing protein table is 48.2 MB (11.0 MB gzip, lossless replay verified). Its abundance summary can ship independently of deeper peptide enrichment. Reuse the checked intake in pirl-unc/oncoref#583 and Hitlist's existing canine import. orfdata owns the shared source facts/artifact; OncoRef and Hitlist retain their domain-specific interfaces and consume that release. Preserve existing imports and historical snapshots during migration. Consumer follow-ups: pirl-unc/oncoref#585 and pirl-unc/hitlist#668; the broader Hitlist data dependency remains pirl-unc/hitlist#666.
Roadmap: #3. Priority: P1.
Dependencies: #4, #5, #6.
- 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di openvax/orfdata
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
openvax/orfdata#194 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di openvax/orfdata
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pearu/agent-sandbox#451 ·
I maintainer di solito rispondono entro 1 giorno
-
run_gate loads a custom tasks file from outside the working directoryForse già presa @Ru0k3 l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
MakazhanAlpamys/Soup#3189 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
review developer setup docAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
NYCPlanning/data-engineering#2996 ·
I maintainer di solito rispondono entro 1 giorno