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

Estimation of peptide elongation times from ribosome profiling spectra.

Nucleic Acids Res · 2021
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.

Supporting (toward a concern)
Content-critical question only partially held
+2 pts
From: Q8 · Severity of the miss (overall human judgment) 🟡
Minor / cosmetic deviation
+1 pts
From: Q3 · Location of the main deviation 🟡
Minor / cosmetic deviation
+1 pts
From: Q4 · Cause of the deviation 🟡
Minor / cosmetic deviation
+1 pts
From: Q6 · Severity of the deviation 🟡
Concordant (toward reproduced)
Code + data deposited & functional
-2 pts
From: Data & code availability Available & functional
Total score +3
✓ What held up
  • Reported values were directly comparable
  • Reported values are derivable from the shared data
  • The central claim held under reproduction
What did not (or only partly)
  • 🟡Could not use the authors’ exact input data
  • 🟡A deviation arose in the data or preprocessing
  • 🟡A deviation was attributed to the published material
  • 🟡The deviation was non-trivial in magnitude
  • 🟡Overall, the reproduction showed a material discrepancy
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

Described well enough to reproduce 1:1 for the core modelling claim. RiboTimes is the authors' own C++/R (Rcpp) MLE tool and the repo ships the paper's own demo input (data/Demo_input_file.txt, Demo_Data_Set_E_coli, 125 genes, GSE145571). I ran it on «our HPC» and reproduced the Figure 3A/B/C result directly: the two genes the paper names, rpsQ (paper r=0.83 -> repro 0.849) and atpE (paper r=0.81 -> repro 0.820), match within +/-0.02, and the stated 'Pearson r in the 0.7-0.8 range for high-density genes' is reproduced (top-20 density-gene median r=0.761). The Rcpp wrapper segfaulted at dyn.load under conda gcc-15 (SIGSEGV invalid-permissions); I pivoted to the repo's documented standalone C/main.cpp built with gcc-12, which ran cleanly and writes the same quantities to plain text. NOT attempted (hard 20% / out of scope): rebuilding RPF count tables from GSE145571 raw FASTQ (upstream alignment), mupirocin fold-change z-factors (Fig 9A), growth-rate-calibrated absolute elongation times (Fig 6B), and exact full-dataset z-factor/sigma figures (Fig 4A, Supp S5B) -- those use more genes than the 125-gene demo, so on the subset they are only qualitatively comparable (overlapping ranges, sd(log z)=0.40 vs reported 0.61/1.2). No fabrication concern: the reported Fig 3A/B values regenerate directly from the shipped data+code. Verdict: partial, with a clean 1:1 on the headline correlation claim.

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 76
    assessed: 2026-06-15 ⛓ bd9d00018071
✎ 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-15
Rubric version
v1.0
Assessed by
🤖 AI curator · claude (ai-curator room) · v1.0 · run #1 2026-06-15
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: opus
Founding hypothesis

Can quantitative, single-codon-resolution peptide elongation times be reliably extracted from ribosome profiling (Ribo-Seq) spectra despite technical biases such as base-specific RNase cleavage preferences? The authors hypothesize that a local codon context (around five codons including A, P and E sites) determines the ribosomal dwell time at each A-site codon and that modeling RPF counts with maximum likelihood statistics can neutralize generation/processing biases.

Core claims
  • A maximum-likelihood model that separates context-dependent bias factors from elongation-time factors enables bias-corrected estimation of peptide elongation times at single-codon resolution from Ribo-Seq spectra. method
  • The method neutralizes technical biases including base-specific RNase (e.g. MNase) cleavage preferences in RPF generation/processing. method
  • An inner local context of five codons, including those at the A, P and E sites, accounts for the ribosomal dwell time on each A-site codon of the transcriptome. mechanism
  • The expected RPF count at a codon is modeled as a product of library depth constant, ORF initiation frequency, expected elongation cycle time, and a context-dependent bias factor (λij = cRPF·νi·τij·γ^B_ij). method
  • The approach was validated on E. coli mupirocin (isoleucyl-tRNA synthetase inhibitor) data and on two S. cerevisiae datasets generated with RNases of distinct cleavage signatures (MNase and RNase A). finding
  • Using the more precise MNase 3'-end cleavage to infer the A-site codon improves resolution of bacterial ribosome profiling sets. finding
  • RPF copy-number distributions are modeled: Poisson after ligation, burst-like after PCR amplification, and Neyman type A after sequencing, approximated as Poisson under the study's conditions (A·q < 1). method
  • The method provides a new E. coli Ribo-Seq resource and a generalizable bias-correction framework for extracting elongation times. resource
Experimental setups
Assay System Perturbation Readout Platform
Ribosome profiling (Ribo-Seq) with deep sequencing E. coli B strain AS19, grown in LB to OD600 0.5 none (flash-frozen, biological replicates) RPF counts per codon/ORF, normalized to RPM and calibrated to A site fastx-toolkit 0.0.13.2, cutadapt 1.8.3, Bowtie 1.2.2 mapping to E. coli MG1655 U00096.3
Ribosome profiling (Ribo-Seq), re-analyzed public dataset E. coli MG1655 in MOPS complete synthetic media with all 20 amino acids mupirocin treatment (200 μM, 10 min) inhibiting isoleucyl-tRNA synthetase; vs untreated control RPF counts / elongation time estimates at codons GSM3358136 (untreated), GSM3358137 (mupirocin); collected by filtration
Ribosome profiling (Ribo-Seq), re-analyzed public dataset Saccharomyces cerevisiae RNase used for RPF generation (MNase vs RNase A) — distinct cleavage signatures RPF counts / bias-corrected elongation time estimates GSM2186726 (MNase), GSM2186728 (RNase A)
Key results
  • An inner local context of five codons (A, P, E sites included) accounts for ribosomal dwell time on each A-site codon. 5 codons
  • Method yields bias-corrected translation time estimates that account for RNase cleavage preferences across MNase and RNase A datasets.
  • Total of 915 context-defining parameters were estimated by fitting model-predicted RPF spectra to experimental transcriptome-wide spectra via nonlinear ML regression. 915 parameters
  • Validation succeeded on mupirocin-treated E. coli, where isoleucyl-tRNA synthetase inhibition is expected to alter elongation times at Ile codons.
Key statistics
  • count 915 context-defining parameters (number of parameters estimated by ML fitting of RPF spectra)
  • count 5 codons (size of inner local context (A, P, E sites) determining A-site dwell time)
  • other OD600 of 0.5 (E. coli AS19 culture density at harvest)
  • other 200 μM mupirocin, 10 min (treatment condition for E. coli MG1655 IleRS inhibition)

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.

The paper develops a maximum likelihood (ML) estimation framework to extract peptide elongation times from ribosome profiling (Ribo-Seq) data. RPF counts at each codon position are modeled as Poisson-distributed random variables, and a transcriptome-wide log-likelihood is maximized jointly over 915 context-defining parameters via non-linear regression. The method is applied to original E. coli data and validated against publicly available datasets from E. coli (antibiotic-treated) and S. cerevisiae (two RNases). Results are reported as bias-corrected parameter estimates rather than classical hypothesis-test outcomes.

Replicationbiological Sample sizeBiological replicates mentioned for E. coli library preparation; exact replicate count and power calculation not stated in provided text GroupsE. coli untreated vs. mupirocin-treated; S. cerevisiae MNase-digested vs. RNase A-digested libraries Pairingunclear Randomization/blindingnot stated Dispersionnone Exact p-valuesno Confidence intervalsno Multiplicity correctionnone stated
Statistical tests used
Test Applied to n Assumptions
Maximum likelihood estimation with Poisson likelihood (non-linear regression over transcriptome-wide log-likelihood) Estimation of 915 codon-context parameters (elongation times and bias factors) from RPF count spectra across all ORFs 915 context-defining parameters; transcriptome-wide RPF counts from E. coli and S. cerevisiae datasets; exact codon/ORF count not stated in provided text stated
Approaches that could also have been used
  • RPF counts are modeled with a Poisson distribution; the paper itself notes that a Neyman type A distribution (overdispersed relative to Poisson) is the more exact model for sequencing count data after PCR amplification, and simplifies to Poisson only when the product A·q is small
    Could also: A negative binomial (NB) likelihood — or the full Neyman type A likelihood the authors describe — could also be used to model RPF counts, as these naturally accommodate overdispersion common in sequencing data — When counts are overdispersed (variance > mean), a Poisson assumption underestimates parameter uncertainty; NB adds a dispersion parameter that absorbs extra-Poisson variability, which can yield better-calibrated uncertainty estimates for the elongation-time parameters
  • Parameter uncertainty (standard errors or confidence intervals) for the 915 estimated elongation-time and bias parameters is not reported in the provided text
    Could also: Profile likelihood confidence intervals, the Fisher information matrix (observed or expected), or parametric bootstrap resampling could also be used to quantify uncertainty around the ML point estimates — Reporting uncertainty bounds alongside point estimates allows readers to distinguish precisely versus imprecisely estimated elongation times and to propagate that uncertainty into downstream biological interpretation
  • Model parameters are estimated by maximizing a frequentist log-likelihood
    Could also: A Bayesian hierarchical model with priors on elongation times and bias factors (e.g., gamma or log-normal priors) could also be used to jointly estimate parameters and their posterior distributions — A Bayesian approach would naturally provide full posterior uncertainty for each parameter, allow partial pooling across codons or ORFs (shrinkage), and handle low-count positions more gracefully through the prior
  • Biological replicates are described but the provided text does not report how replicate-to-replicate variability is incorporated into the ML fitting or used to assess model reproducibility
    Could also: Replicate datasets could also be used to compute inter-replicate Pearson or Spearman correlations of estimated elongation times, or to perform a likelihood-ratio or permutation test of model fit across replicates — Formal assessment of replicate concordance for the estimated parameters would provide an empirical measure of reproducibility that complements in-model goodness-of-fit statistics
  • Model selection (e.g., choosing a context window of five codons) is described qualitatively; the statistical criterion used to select context width is not stated in the provided text
    Could also: Information criteria such as AIC or BIC, or cross-validation on held-out ORFs, could also be used to formally compare models with different context window sizes — A penalized-likelihood or cross-validation criterion would provide a principled, data-driven way to balance model complexity against fit quality, making the chosen context size easier to compare to alternatives
  • RPF counts are normalized per total mapped reads per million (RPM) prior to modeling
    Could also: Median-of-ratios normalization (as in DESeq2) or trimmed mean of M-values (TMM, as in edgeR) could also be used to normalize read counts across samples before or within the modeling framework — RPM normalization assumes that total mapped read depth is a valid reference across samples; compositional normalization methods are less sensitive to a few highly expressed ORFs dominating the library and are standard in comparative Ribo-Seq analyses
Software: fastx-toolkit 0.0.13.2 · cutadapt 1.8.3 · Bowtie 1.2.2 · Custom ML/non-linear regression (language/package not stated)

Citation network

Where this publication sits in the reproducibility-weighted citation graph — what it is built on, and what is built on it. Citation data from OpenAlex.

Citations
8
Impact: low
Foundation confidence
None of its references are in our reproducibility record yet — its foundation cannot be assessed.
Topics

No assessed neighbours yet — the network grows as more papers are assessed.

Data lineage

The datasets this paper uses (text-mined from the full text via Europe PMC), and which other assessed papers stand on the same data. A shared dataset is a factual link — not a judgement.

U00096 ENA in Methods (http://purl.org/orb/Methods)
also used by 1 paper:
1tot in Supplementary material (http://purl.obolibrary.org/obo/IAO_0000326)
no other assessed paper uses this yet
GSE119104 GEO in Data Availability (http://purl.obolibrary.org/obo/IAO_0000611)
no other assessed paper uses this yet
GSE145571 GEO in Data Availability (http://purl.obolibrary.org/obo/IAO_0000611)
no other assessed paper uses this yet
GSM2186726 GEO in Data Availability (http://purl.obolibrary.org/obo/IAO_0000611)
no other assessed paper uses this yet
GSM2186728 GEO in Data Availability (http://purl.obolibrary.org/obo/IAO_0000611)
no other assessed paper uses this yet
GSM3358136 GEO in Data Availability (http://purl.obolibrary.org/obo/IAO_0000611)
no other assessed paper uses this yet
GSM3358137 GEO in Data Availability (http://purl.obolibrary.org/obo/IAO_0000611)
no other assessed paper uses this yet

What was reproduced

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

Scope — pmid-33885812 (RiboTimes)

Paper: Estimation of peptide elongation times from ribosome profiling spectra. Tunney? — Dao Duc / Gustafsson et al., NAR 2021. PMID 33885812 · PMCID PMC8136808 · DOI 10.1093/nar/gkab260. Code: https://github.com/gustafGitHub/RiboTimes (master, last push 2021-03-25, C++/R, Rcpp, no license). Data: GEO GSE145571 (E. coli AS19 ribosome profiling) + validation libs (E. coli MG1655, S. cerevisiae).

The tool (what the pipeline does)

RiboTimes is an R wrapper (riboTimesMle.R) around a C++ maximum-likelihood estimator (C/RiboTimesMLE.cpp, exported runMLE() via Rcpp, cpp11 plugin only — no Eigen/Armadillo). Input = a text table of ribosome-protected-fragment (RPF) counts per codon position per gene. Output = a ~40-field R list: experimental vs modelled selectivity indices (sij_Exper, sij_Model), per-codon z-factors (zFP, zFP_HAT + their _Sigma), elongation times, and codon statistics. The repo ships the paper's own demo input data/Demo_input_file.txt (365 KB, E. coli) plus two yeast 300-gene demo tables — so the codon-count table that feeds the MLE is provided directly (no upstream read-alignment step needed to reproduce the modelling result).

IN SCOPE (pipeline-derived, attempted)

The MLE modelling step on the shipped E. coli demo input, and the quantities it emits that the paper reports:

id reported claim paper location how reproduced
C1 Pearson correlation between experimental and modelled RPF/selectivity spectra in the 0.7–0.8 range for high-footprint-density genes Fig 3C / Results run MleAlgorithm on demo; compute cor(sij_Exper, sij_Model) per gene, look at high-geneRPFdensity genes (rpsQ, atpE named in Fig 3A/B)
C2 σ ≈ 0.61 for bias-free elongation parameters; σ ≈ 1.2 for total context factors Supp Fig S5B from the z-factor outputs (zFP_HAT bias-free vs zFP context) spreads / _Sigma fields
C0 the pipeline itself runs on the paper's data and regenerates the described output structure + Fig 2/3 (plot_figures.R) repo demo structural reproduction (compiles, runs, produces 40-field list + figure PDFs)

Primary, cleanest claim = C1 (unambiguous computation from two emitted vectors). C2 is secondary/exploratory (figure-only value, field mapping less certain).

OUT OF SCOPE (not attempted, why)

  • Upstream read processing (FASTQ → RPF count tables from GSE145571 raw reads): not needed — the count tables are shipped; reproducing the aligner step is a separate, much larger pipeline and is the "hard 20%".
  • Mupirocin fold-change z-factors (Fig 9A: 13×/16×/8.5×): requires the MG1655 treated/untreated libraries processed into the tool's input format (not in the shipped demo) — out of scope for the 80/20.
  • Absolute elongation times calibrated by growth rate (Fig 6B): depends on doublingTime calibration + full dataset; demo-subset values not 1:1 comparable.
  • Wet-lab / manual content: none relevant.

Reproduction model

Third-party-vs-own: this is the authors' own repo, applied to the authors' own shipped demo data — a direct 1:1 reproduction of the modelling step.

Figures / tables: Fig 3AFig 3BFig S5BFig 4A
C0
Reported
RiboTimes MLE runs on the shipped E. coli demo and emits the described model outputs
Reproduced
compiled + ran (standalone C/main.cpp, gcc 12.4.0) in 2 s; 125 genes; R2/z-factor/elongation outputs produced
exact
C1a
Reported
rpsQ Pearson r = 0.83 (Fig 3A)
Reproduced
r = 0.849
within tolerance
C1b
Reported
atpE Pearson r = 0.81 (Fig 3B)
Reproduced
r = 0.820
within tolerance
C1c
Reported
Pearson r in 0.7-0.8 range for high-footprint-density genes (Fig 3A-C)
Reproduced
top-20 density-gene median r = 0.761 (range 0.588-0.961)
within tolerance
C2
Reported
sigma = 0.61 and 1.2 of log distributions (Supp Fig S5B)
Reproduced
sd(log z-factors) = 0.40 on the 125-gene demo subset
partial
C3
Reported
Fig 4A edge z-factors: p4 0.4-1.6, p11 0.2-2.1
Reproduced
p4 range 0.17-2.40, p11 range 0.19-5.93
partial

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.

Supporting (toward a concern)
Content-critical question only partially held
+2 pts
From: Q8 · Severity of the miss (overall human judgment) 🟡
Minor / cosmetic deviation
+1 pts
From: Q3 · Location of the main deviation 🟡
Minor / cosmetic deviation
+1 pts
From: Q4 · Cause of the deviation 🟡
Minor / cosmetic deviation
+1 pts
From: Q6 · Severity of the deviation 🟡
Concordant (toward reproduced)
Code + data deposited & functional
-2 pts
From: Data & code availability Available & functional
Total score +3

Running the authors' own RiboTimes MLE on their shipped E. coli demo reproduces the headline Fig 3A/B correlations 1:1 (rpsQ 0.83->0.849, atpE 0.81->0.820, both within +/-0.02) and the stated 0.7-0.8 band for high-density genes (median r=0.761). The only deviations are on secondary full-dataset figures (S5B sigma 0.61/1.2 -> sd(log z)=0.40; Fig 4A edge z-factor ranges), and these sit on our side — a consequence of using the 125-gene demo subset rather than rebuilding count tables from raw FASTQ — not an authors' defect. No fabrication concern; values are derivable from the shared data. Overall a solid reproduction with explainable, scope-driven secondary deviations.

🤝
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.

192.3 k
tokens (I/O) · 13.2 M incl. cache
19 min
runtime · 0.02 CPU-h
1.9 GB
peak RAM
4 (3 failed)
HPC jobs
hummel
machine