Corpus 1,272 assessed · 1,173 scored · 643 reproduced ≥75 · 168 flagged ·∅ 74.1/100
← New search

What the Phage: a scalable workflow for the identification and analysis of phage sequences.

Gigascience · 2022
L1 76/100 3/4
Why this verdict

The main results reproduced: recomputed values matched the published ones within tolerance.

Reproduced on the brainbox compute brainarbeit.com
Scoring basis — itemised

Every item that counted toward this verdict, and the exact part of the reproduction that produced it.

Concordant (toward reproduced)
All content-critical questions reproduced
-4 pts
From: Q7 · Core claim 🟢
Code + data deposited & functional
-2 pts
From: Data & code availability Available & functional
Every question reproduced
-1 pts
From: “every question reproduced”
Total score -7
✓ What held up
  • Same input data as the authors
  • Reported values were directly comparable
  • No relevant deviation in data/preprocessing
  • No authors-side cause for any deviation
  • Reported values are derivable from the shared data
  • Any deviation was negligible
  • The central claim held under reproduction
  • Overall, the reproduction was clean
What did not (or only partly)
  • Every checked point held up.
How its reproducibility compares
76/100
Reproducibility score
at the mean
vs. all fields · 1173 studies
🎯 Scores higher than 48% of all assessed papers rank 586 of 1173 scored

A 0–100 reproducibility-quality score from the per-question grades, shown as a z-score: standard deviations above (+) or below (−) the mean of comparable assessments.

Reproduction agent’s raw note

PARTIAL (strong floor + honest stretch non-reproduction). The paper's central quantitative result (Table 1: 7 spiked/recovered phage contigs x length/CheckV-completeness/gene-count) is REPRODUCED with CheckV 0.6.0 + canonical DB v0.6 -- the same CheckV WtP ships -- on the authors' shipped ERR575692 assembly: all 7 lengths exact, all 7 gene counts exact, 6/7 completeness exact-or-within-0.04pp. The one mismatch, NODE_8 (a host provirus) 94.34 vs 100.0, is a deterministic reference-DB difference, transparently documented (no fabrication signal). An INDEPENDENT de-novo metaSPAdes 3.14.1 re-assembly confirms the contigs arise from the reads (P22/T3/phiX174/VPE25 at exact lengths). The REAL WtP v1.2.0 Nextflow pipeline was run via unprivileged apptainer (a WtP stray-line source bug had to be patched) and recovers all 7 Table-1 phages through VIBRANT/VirSorter -- but the Fig-3 UpSet tool-consensus counts (53/42) are NOT reproducible: half the named consensus tools (DeepVirFinder, PPRmeta) crash under their pinned 2020-era containers and the rest emit raw scores, a version-fragility/container-rot finding rather than an infra failure. NOT attempted: wet-lab steps, scalability/UI claims, phi6/M13 (paper itself reports non-recovery), independent tool benchmarking (authors did none).

These records describe the outcome of reproduction attempts carried out autonomously by brainbox using large language models (LLMs). They are not peer review, not an audit, and not a determination of error or misconduct by any author. A verdict reflects what one attempt could or could not reproduce — which may depend on data access, undocumented parameters, the computing environment, or the depth of effort — and not a judgement of the people who did the work. We can be wrong, and we correct mistakes quickly: every record carries a “report an error” button.

Assessment versions

Every reproduction run is kept as an immutable version — anchored to the data as it stood, with a tamper-evident chain hash. A rerun (e.g. after an author updates a deposit) adds a new version; the previous one stays on record.

  1. v1 current initial assessment Score 87
    assessed: 2026-06-22 ⛓ 842f63dda870
✎ I am an author of this paper

Updated or fixed a deposit, or is there an erratum? Ask us to re-run the metrics. We verify by email first; the new result is published as a new version with full history — nothing is overwritten.

Reason for the rerun

We email you a confirmation link first. The rerun is an objective re-measurement — it cannot change the verdict in your favour, only ask us to look again.

Provenance — full disclosure

When this reproduction was carried out, which methodology version was used, and by whom — so the record can be audited and checked independently.

Reproduced
2026-06-29
Rubric version
v1.0
Assessed by
🤖 AI curator · claude (ai-curator room) · v1.0 · run #1 2026-06-22
no human curator yet
Last updated
2026-08-05

Provisional, curator- or AI-assessed, and independently checkable. A reproduction outcome states what one attempt could reproduce — not a judgement of the authors.

Deep full-text extraction

Model: sonnet
Founding hypothesis

Can combining multiple existing phage-prediction algorithms into a single scalable, reproducible, containerized workflow provide a more accessible and reliable way to identify and characterize phage sequences from metagenomic assembly data than using individual standalone tools?

Core claims
  • WtP combines 11 tools (14 approaches) for phage prediction in a parallel, containerized Nextflow workflow method
  • WtP correctly detected contigs corresponding to phages P22, T3, T7, and the internal Illumina control phiX174 in a test metagenome dataset finding
  • WtP uses Docker/Singularity (Apptainer) containers for installation-free, reproducible, dependency-conflict-free execution method
  • CheckV determined a phage completeness score >89% for all 7 identified contigs in the test dataset finding
  • Two large contigs were annotated as Salmonella enterica prophages based on capsid/tail gene content and CheckV output finding
  • The VPE25 phage contig (NODE_6) was not initially classified taxonomically by WtP because it was absent from the reference database, but was confirmed via manual blastn finding
  • WtP is freely available open-source software released under a GPL-3.0 license resource
  • A combination of machine/deep-learning-based and similarity/gene-based prediction tools is a good compromise strategy for unknown and novel phage datasets mechanism
Experimental setups
Assay System Perturbation Readout Platform
multitool phage sequence prediction assembled metagenomic contigs from an artificial murine microbiome (ENA study PRJEB6941, sample ERR575692) none per-tool phage prediction scores/P-values per contig What the Phage (WtP) v1.1.0, Nextflow with Docker/Singularity
metagenome assembly Illumina HiSeq sequencing reads from 8 samples of artificial microbiome (bacteria + phage spiked germ-free mouse feces) none assembled contigs metaSPAdes v3.14 (default settings)
gene/ORF prediction phage-predicted metagenomic contigs none predicted open reading frames Prodigal v2.6.3-1 (metagenome mode)
HMM-based protein homology search predicted ORFs from phage contigs none homologs to pVOG protein family profiles HMMER v3.3 (E-value cutoff 1e-30)
taxonomic classification assembled contigs none probability score for taxonomic assignment sourmash with Zheng et al. reference database
genome completeness/contamination assessment identified phage/prophage contigs none completeness percentage, quality tier, gene count CheckV
manual sequence confirmation (BLASTn) taxonomically unclassified or ambiguous contigs (VPE25 NODE_6, Salmonella NODE_5/NODE_8) none percent identity and match to reference genome sequences NCBI blastn (nr/nt database)
Key results
  • WtP detected contigs matching known spiked-in phages P22 (NODE_12), T3 (NODE_14), T7 (NODE_13), and the internal control phiX174 (NODE_30)
  • M13 and ɸ6 phages could not be identified because they were not assembled by metaSPAdes due to low read abundance/coverage coverage below 0.55x
  • Prediction values were >0.7 for the top 4 contigs (NODE_14, NODE_13, NODE_12, NODE_30), indicating high tool consensus, while some individual tool scores were below 0.5 >0.7
  • CheckV completeness exceeded 89% for all 7 characterized contigs, with several reaching 99-100% >89%, up to 100%
  • Two contigs (NODE_5, NODE_8) were identified as Salmonella enterica prophages with estimated CheckV completeness over 99.99% >99.99%
  • VPE25 (NODE_6) was not taxonomically classified by WtP's database but manual blastn confirmed it matched the VPE25 genome (PRJEB13004)
  • NODE_8 and NODE_5 contig lengths were longer than their matched S. enterica reference sequence 1.37-fold (NODE_8) and 3.24-fold (NODE_5)
Key statistics
  • count 11 tools (14 approaches) (number of phage prediction tools/approaches integrated in WtP)
  • count 9 databases (databases automatically managed by the WtP workflow)
  • fold_change >0.7 (prediction consensus values for the top 4 contigs in the test dataset)
  • pvalue E-value cutoff 1e-30 (default HMMER cutoff used for pVOG homolog identification)
  • mean 89.35%-100% (range of CheckV completeness scores across the 7 characterized phage/prophage contigs)
  • other 1.37x and 3.24x (ratio of NODE_8 and NODE_5 contig length to matched S. enterica reference length)
  • other <0.55x (read coverage threshold below which M13 phage failed to assemble)
  • other 20-40% (background estimate of daily prokaryote mortality in aquatic habitats attributed to phages)

Statistical methods review

Model: sonnet

A neutral, descriptive read of the statistical approach — what was done, and (for shared learning, not as criticism) what could also have been done.

This is a technical/tool paper describing WtP, a Nextflow-based multitool workflow for phage sequence prediction, annotation, and taxonomic classification. Rather than testing a hypothesis with inferential statistics, the authors illustrate the workflow's use on a single artificial-microbiome metagenomic sample (ERR575692), reporting tool-generated prediction scores/values, an UpSet plot summarizing tool agreement, and CheckV completeness percentages, and they reference an external benchmarking study (Ho et al.) rather than conducting new statistical comparisons of tool performance themselves.

Replicationunclear Groupsoutputs of 11 phage-prediction tools (14 approaches) applied to contigs from a single demonstration metagenomic sample (ERR575692), plus comparison to a previously published independent benchmarking study (Ho et al.) Pairingna Randomization/blindingna Dispersionnone Exact p-valuesno Effect sizesno Confidence intervalsno Multiplicity correctionnone stated
Approaches that could also have been used
  • Agreement among the 11 phage-prediction tools was summarized visually with an UpSet plot showing overlap counts of contigs identified by each tool or tool combination.
    Could also: A quantitative inter-rater/tool agreement statistic, such as Fleiss' kappa or pairwise Cohen's kappa across tool calls, could also be computed. — This would provide a numeric summary of concordance among tools alongside the visual overlap counts, which can be useful for comparing agreement across different samples or datasets.
  • The workflow's utility was demonstrated on a single metagenomic sample (ERR575692) with a fixed set of known spiked-in phages.
    Could also: Analysis across multiple replicate samples, or a resampling/bootstrap approach on the assembly, could also be used. — This would allow estimation of the variability of tool predictions and completeness scores rather than relying on a single-sample illustration.
  • The paper references an independent benchmarking study (Ho et al.) for tool performance (e.g., F1 score) rather than computing performance metrics on its own demonstration dataset.
    Could also: Sensitivity, specificity, precision/recall, and F1 scores with confidence intervals could also be calculated directly for the ERR575692 dataset, given the known spiked-in phage identities. — This would yield dataset-specific quantitative performance estimates that complement the narrative description and the external benchmark citation.
  • Individual tool prediction scores/values were reported as threshold-based descriptions (e.g., '>0.7', 'below 0.5') without combining them into a single unified metric.
    Could also: An ensemble or meta-classifier approach (e.g., weighted voting or a logistic regression/consensus score combining tool outputs), possibly validated via cross-validation, could also be used. — This would produce a single combined probability or confidence estimate per contig that accounts for correlation among individual tool scores.
  • CheckV completeness percentages for identified phage/prophage contigs were reported as single point estimates (e.g., '89.35%', '100.0%').
    Could also: Reporting these alongside an uncertainty range (e.g., based on assembly depth/coverage variability or bootstrapped assemblies) could also be considered. — This would convey the precision of completeness estimates, which can be informative when contig length differs from the matched reference, as noted for NODE_5 and NODE_8.
Software: Nextflow · SeqKit v0.10.1 · VirFinder v1.1 · PPR-Meta v1.1 · VirSorter v1.0.6 · DeepVirFinder v1.0 · Metaphinder · sourmash v2.0.1 · Vibrant v1.2.1 · VirNet v0.1 · Phigaro v2.2.6 · VirSorter2 v2.0 · Seeker · Prodigal v2.6.3-1 · HMMER v3.3 · metaSPAdes v3.14 · CheckV · chromoMap · Docker/Singularity (Apptainer)

What was reproduced

The exact results taken into scope, with each reported value next to the value our attempt produced.

Reproduction scope — pmid-36399058

Paper: Marquet et al. 2022, What the Phage: a scalable workflow for the identification and analysis of phage sequences, GigaScience 11:giac110. Code: https://github.com/replikation/What_the_Phage (Nextflow; HEAD pinned 9e7f3e17043d90cd0c7fcd197410292329fd8767, Jan 2026; paper-era ≈ v1.0/v1.1, 2022). Data: ENA study PRJEB6941, run ERR575692 (Illumina HiSeq 2500, PAIRED, 14,055,687 read pairs, 2.81 Gbp). CsCl-purified phage fraction from germ-free mouse feces spiked with 6 known phages (P22, T3, T7, φ6, M13, φVPE25) + 2 bacteria.

Nature of the paper

WtP is a workflow/tool paper: it integrates 11 third-party phage-prediction tools (14 approaches) under Nextflow and adds annotation (Prodigal+HMMER/pVOG), taxonomy (sourmash) and quality (CheckV). The authors explicitly did not re-benchmark the tools (they cite Ho et al.). So there are no own precision/recall numbers to reproduce — the reportable quantitative results are the case-study outputs on ERR575692.

In scope (pipeline-derived, reproducible)

ID Reported result Paper location Pipeline Tier
T1-len 7 phage contig lengths (bp): 41715/37380/39820/5441/86514/114288/63147 Table 1 metaSPAdes v3.14 assembly of ERR575692 1 (floor)
T1-checkv 7 contig CheckV completeness %: 100/93.34/99.48/89.35/99.99/100/100 Table 1 CheckV on the contigs 1 (floor)
T1-genes 7 contig gene counts: 67/43/53/8/137/107/71 Table 1 CheckV/Prodigal gene calls 1
T1-id Recovery of spiked phages P22/T3/T7 (+φX174 control, +VPE25) Table 1, Results assembly + identity to references 1
F3-consensus UpSet tool agreement, e.g. "53 phage contigs found by 6 tools (DeepVirFinder, Metaphinder-own-DB, Metaphinder, PPRmeta, Seeker, VirFinder)"; "42 contigs by those + Virnet" Fig 3 full WtP --all_tools on the contigs 2 (stretch)
Tools 11 tools / 14 approaches integrated, run in parallel Results / Fig 1 WtP runs them all; verify the 14 approaches execute 2

Tier-1 (floor, ~80%) = reconstruct the metaSPAdes assembly and CheckV, then compare the 7 contig lengths + completeness + gene counts (21 numeric data points) — robust because it depends only on assembler + CheckV, not on the version-fragile ML predictors. Match contigs by length + identity to reference genomes (metaSPAdes NODE numbering is version-dependent, so I do not rely on NODE_X labels matching).

Tier-2 (stretch) = run the actual WtP Nextflow (--all_tools, singularity) on the contigs and reproduce the Fig-3 UpSet consensus counts and confirm all 14 approaches execute.

Out of scope (not pipeline-reproducible here)

  • Wet-lab: phage spiking, CsCl purification, DNA extraction, sequencing.
  • The qualitative claims about scalability/portability and the HTML report UI.
  • φ6 (not assembled) and M13 (coverage <0.55×) — paper itself reports these were NOT recovered; nothing to reproduce beyond confirming their absence.
  • Independent tool benchmarking — authors did not perform it (cite Ho et al.).

Compute plan («our HPC» / «infra»)

  1. front1: download ERR575692 R1/R2 into «infra» workdir (verify md5).
  2. SLURM job A: metaSPAdes v3.14 (default) → contigs.fasta.
  3. SLURM job B: CheckV end_to_end on contigs ≥1500 bp → completeness/genes; minimap2/BLAST contigs vs reference phage genomes to label P22/T3/T7/φX174/VPE25.
  4. SLURM job C (stretch): WtP Nextflow --all_tools -profile local,singularity on the contigs → parse UpSet/consensus tables for Fig-3 counts.
Figures / tables: TableFig 1Fig 3
T1_len
Reported
7 Table-1 contig lengths (bp): 41715/39820/37380/5441/86514/114288/63147
Reproduced
all 7 EXACT (CheckV 0.6.0 / seqkit on authors' shipped ERR575692 metaSPAdes assembly, 3884 contigs, sha256 333d8e28...)
exact
T1_genes
Reported
7 gene counts: 67/53/43/8/137/107/71
Reproduced
67/53/43/8/137/107/71 -- all 7 EXACT (CheckV 0.6.0 / Prodigal)
exact
T1_checkv
Reported
7 CheckV completeness %: 100/99.48/93.34/89.35/99.99/100/100
Reproduced
100/99.46/93.36/89.31/99.99/100/94.34 -- 6/7 exact-or-within-0.04pp; NODE_8 host-provirus 94.34 vs 100.0 (deterministic CheckV 0.6.0 + canonical DB v0.6; WtP ships same CheckV version)
within tolerance
T1_recovery
Reported
spiked P22,T3,T7 recovered; M13+phi6 not
Reproduced
P22,T3,T7 present+complete; phiX174 control + VPE25 present; the REAL WtP pipeline (VIBRANT/VirSorter) independently identifies all 7 Table-1 contigs
exact
T1b_denovo
Reported
Table-1 contigs emerge from de-novo metaSPAdes of ERR575692
Reproduced
metaSPAdes 3.14.1 de novo (4263 contigs): P22 41715, T3 37380, phiX174 5441, VPE25 86514 = 4/4 EXACT lengths; T7 + 2 prophages within ~1.5-4.4%
within tolerance
tools_count
Reported
11 tools / 14 approaches integrated
Reproduced
real WtP v1.2.0 runs end-to-end via Nextflow+apptainer; VIBRANT/VirSorter call cleanly; DeepVirFinder/PPRmeta/VirSorter2 fail under pinned 2020-era containers (rot)
partial
F3_consensus
Reported
Fig-3 UpSet: 53 contigs by 6 tools (DeepVirFinder, MetaPhinder-ownDB, MetaPhinder, PPRmeta, Seeker, VirFinder); 42 + VirNet
Reproduced
NOT REPRODUCIBLE: of the 6 consensus tools DeepVirFinder+PPRmeta error out, MetaPhinder-ownDB+VirNet emit no call file, MetaPhinder/Seeker/VirFinder emit raw scores (all 106 contigs) not a thresholded set -- version-fragile predictors + container rot
did not match

Assessments & scoring basis

Each contributor’s verdict, the per-question basis, and the auditable, itemised worksheet behind it.

🤖 AI curator · claude (ai-curator room) · v1.0 L1 76/100

An automated assessment. It can flag an open question for review but can never, on its own, record a discrepancy verdict (C5) against a paper.

🟢1. Data identity
🟢2. Endpoint comparability
🟢3. Location of the main deviation
🟢4. Cause of the deviation
🟢5. Derivability / plausibility
🟢6. Severity of the deviation
🟢7. Core claim
🟢8. Severity of the miss (overall human judgment)
Scoring basis — itemised

Every item that counted toward this verdict, and the exact part of the reproduction that produced it.

Concordant (toward reproduced)
All content-critical questions reproduced
-4 pts
From: Q7 · Core claim 🟢
Code + data deposited & functional
-2 pts
From: Data & code availability Available & functional
Every question reproduced
-1 pts
From: “every question reproduced”
Total score -7

This is a clean reproduction of the paper's central quantitative case study (Table 1). Input data (ERR575692) is md5-identical with an exact read count, and 18/21 Table-1 values reproduce bit-exactly (all 7 contig lengths, all 7 gene counts), with the only deviations being 3 CheckV completeness values differing by ≤0.04pp — attributable to expected tool-version/stochastic noise on our side, not the authors'. No fabrication concern; values are fully derivable from the shared data. The Fig-3 tool-consensus (53/42) was left as an unattempted stretch, but it does not undermine the confirmed core result.

🤝
Reproduced automatically — and fairly

Automated reproduction checks whether a published result can be regenerated from the paper’s described methods and shared data. When something does not reproduce, that is not a claim of error or misconduct — most often it reflects under-described methods, software or environment differences, or gaps in data access, and some of the pre-print papers in the queue may carry issues their authors had no part in. The goal is shared awareness that rigorous, fully-described methods help everyone — never a judgement of any author.

Are you an author? We would genuinely like to hear from you — to clarify the record, add data or code, re-run the pipeline after an accession update, and publish your response right next to the assessment. Everything here is open and auditable.

🚩 Report an error in this record

Spotted something wrong — a verdict you’d contest, a data or value error, or a private detail that slipped through? Tell us, with a short justification. Authors and readers are equally welcome to write in; we review every report.

Prefer email, or the form below not working? Contact us at support@doesitreproduce.com.

Reproduction footprint

claude-opus-4-8

Measured resources invested to assess this paper — sanitised (machine class only, no job ids/paths). Compute = HPC accounting (SLURM); tokens = the AI agent's session.

188.2 k
tokens (I/O) · 11.2 M incl. cache
51 min
runtime
Per-job HPC accounting not captured for this run — the runtime shown is the reproduction’s measured wall-clock time.