MétaCan
Menu
Back to cohort
Record W2971384141 · doi:10.1038/s41597-019-0174-7

Creating reproducible pharmacogenomic analysis pipelines

2019· article· en· W2971384141 on OpenAlexaff
Anthony Mammoliti, Petr Smirnov, Zhaleh Safikhani, Wail Ba-Alawi, Benjamin Haibe‐Kains

Bibliographic record

VenueScientific Data · 2019
Typearticle
Languageen
FieldDecision Sciences
TopicScientific Computing and Data Management
Canadian institutionsVector InstituteInstitute of Cancer ResearchOntario Institute for Cancer ResearchUniversity Health NetworkUniversity of TorontoPrincess Margaret Cancer Centre
Fundersnot available
KeywordsWorkflowComputer sciencePipeline (software)ScalabilityIdentifierPharmacogenomicsData scienceProcess (computing)Pipeline transportMetadataData accessData miningDatabaseBioinformaticsWorld Wide WebEngineeringBiologyProgramming language

Abstract

fetched live from OpenAlex

The field of pharmacogenomics presents great challenges for researchers that are willing to make their studies reproducible and shareable. This is attributed to the generation of large volumes of high-throughput multimodal data, and the lack of standardized workflows that are robust, scalable, and flexible to perform large-scale analyses. To address this issue, we developed pharmacogenomic workflows in the Common Workflow Language to process two breast cancer datasets in a reproducible and transparent manner. Our pipelines combine both pharmacological and molecular profiles into a portable data object that can be used for future analyses in cancer research. Our data objects and workflows are shared on Harvard Dataverse and Code Ocean where they have been assigned a unique Digital Object Identifier, providing a level of data provenance and a persistent location to access and share our data with the community.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.044
metaresearch head score (Gemma)0.072
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: Reproducibility · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.956
Threshold uncertainty score0.233

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0440.072
Meta-epidemiology (narrow)0.0010.002
Meta-epidemiology (broad)0.0020.004
Bibliometrics0.0050.005
Science and technology studies0.0020.003
Scholarly communication0.0080.007
Open science0.0040.008
Research integrity0.0020.004
Insufficient payload (model declined to judge)0.0040.003

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.295
GPT teacher head0.455
Teacher spread0.160 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

Study designNot applicable
DomainReproducibility
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations7
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueScientific DataSame topicScientific Computing and Data ManagementFrench-language works237,207