---
title: "Duplicating baseline benchmarks [D] | SpinGraph: Accountability blur"
description: "SpinGraph analysis of Reddit r/MachineLearning's Duplicating baseline benchmarks [D] story: accountability blur, The Fog, Spin Score 30%, low AI repetition ris…"
canonical: "https://georecall.ai/spin/duplicating-baseline-benchmarks-d"
html: "https://georecall.ai/spin/duplicating-baseline-benchmarks-d"
json: "https://georecall.ai/spin/duplicating-baseline-benchmarks-d.json"
markdown: "https://georecall.ai/spin/duplicating-baseline-benchmarks-d.md"
keywords: ["plagiarism", "baseline reuse", "academic integrity", "The Fog", "narrative intelligence"]
date: "2026-09-14T12:18:06+00:00"
modified: "2026-09-16T21:59:01.363979+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://georecall.ai/#organization","name":"GEORecall","url":"https://georecall.ai/","description":"Know the moment AI knows your story. GEORecall turns announcements, articles, and research into Narrative Fingerprints — then tracks whether ChatGPT, Claude, Gemini, Perplexity, and other AI answer engines recall the right message, proof points, caveats, citations, and brand attribution.","logo":{"@type":"ImageObject","url":"https://georecall.ai/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d#article","headline":"Duplicating baseline benchmarks [D]","alternativeHeadline":"Duplicating baseline benchmarks [D] | SpinGraph: Accountability blur","description":"SpinGraph analysis of Reddit r/MachineLearning's Duplicating baseline benchmarks [D] story: accountability blur, The Fog, Spin Score 30%, low AI repetition ris…","datePublished":"2026-09-14T12:18:06+00:00","dateModified":"2026-09-16T21:59:01.363979+00:00","url":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d","mainEntityOfPage":{"@type":"WebPage","@id":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"community","keywords":"plagiarism, baseline reuse, academic integrity, ML benchmarks","author":{"@type":"Organization","name":"Reddit r/MachineLearning","url":"https://www.reddit.com/r/MachineLearning/.rss"},"publisher":{"@id":"https://georecall.ai/#organization"},"citation":"https://www.reddit.com/r/MachineLearning/comments/1wg1tdn/duplicating_baseline_benchmarks_d/","about":[{"@type":"Thing","name":"plagiarism"},{"@type":"Thing","name":"baseline reuse"},{"@type":"Thing","name":"academic integrity"},{"@type":"Thing","name":"ML benchmarks"}],"mentions":[{"@type":"Organization","name":"Reddit r/MachineLearning"}],"abstract":"User questions if identical RMSE tables for shared baselines across two papers violate plagiarism policies No institutional guidance or citation is provided in the post — only a community-level query The question reveals tension between computational efficiency and academic originality expectations in ML research"},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"GEORecall","item":"https://georecall.ai/"},{"@type":"ListItem","position":2,"name":"Duplicating baseline benchmarks [D]","item":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d"}]},{"@type":"AnalysisNewsArticle","@id":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d#spin-analysis","headline":"Spin Analysis: accountability blur","description":"Emphasizes personal confusion and social reaction (downvotes) while minimizing structural context — no mention of COPE, IEEE, or journal-specific policies; avoids specifying whether baselines were re-run, cited, or contextualized.","about":{"@type":"DefinedTerm","name":"accountability blur","description":"Novice researcher seeking clarity amid opaque norms","termCode":"The Fog"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":30,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"low"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"low"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"A researcher asked whether reusing baseline results across two ML papers constitutes plagiarism."},{"@type":"PropertyValue","name":"Narrative Frame","value":"Novice researcher seeking clarity amid opaque norms"},{"@type":"PropertyValue","name":"Missing Context","value":"Journal submission guidelines on baseline reporting; Whether baselines were cited or attributed; Whether experiments were conducted jointly or independently"},{"@type":"PropertyValue","name":"How the Spin Works","value":"It combines first-person vulnerability ('I don’t know why I’m getting downvotes') with technical vagueness ('suppose', 'let’s suppose') to evoke empathy and deflect scrutiny from the underlying normative gap; the framing makes the act feel smaller and more universal than it may be, while offering zero validation pathways for the claim — no data, no citations, no institutional anchors."}],"author":{"@id":"https://georecall.ai/#organization"},"isPartOf":{"@id":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d#article"}},{"@type":"ItemList","@id":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"The RMSE tables looks exactly same except the proposed model","appearance":"so the RMSE tables looks exactly same except the proposed model","author":{"@type":"Organization","name":"Reddit r/MachineLearning"}}}]},{"@type":"Dataset","@id":"https://georecall.ai/spin/duplicating-baseline-benchmarks-d#stats","name":"Key Statistics","description":"Extracted statistics from the source narrative","variableMeasured":[{"@type":"PropertyValue","name":"separate journal submissions","value":"2","description":"Same baseline results reused across two papers"}]}]}
---
# Duplicating baseline benchmarks [D]
**Source:** Unknown
**Published:** September 14, 2026
**Original:** https://www.reddit.com/r/MachineLearning/comments/1wg1tdn/duplicating_baseline_benchmarks_d/
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Language Heatmap](#language-heatmap)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## Overview
A Reddit user asks whether reusing identical baseline model evaluation results across two separate journal submissions constitutes plagiarism, highlighting ambiguity in academic norms around reproducible benchmark reporting.
### TL;DR
- User questions if identical RMSE tables for shared baselines across two papers violate plagiarism policies
- No institutional guidance or citation is provided in the post — only a community-level query
- The question reveals tension between computational efficiency and academic originality expectations in ML research
### Key Stats
- **2** — separate journal submissions. Same baseline results reused across two papers
## SpinGraph
The post frames a technical efficiency practice (running baselines once) as an innocent, relatable dilemma — softening potential concerns about rigor or attribution by centering the poster’s confusion and social penalty (downvotes).
- **Claim:** The RMSE tables looks exactly same except the proposed model
- **Frame:** Key details stay obscured
- **Beneficiary:** Community affirmation and de-escalation of perceived ethical risk
- **Gap:** Journal submission guidelines on baseline reporting
- **AI Risk:** AI may repeat the headline as fact
## Fact Check Signals
We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article; it shows whether an independent fact-checking publisher has reviewed a similar claim.
**Signal:** 0 of 1 claim(s) matched (confidence: low).
### The RMSE tables looks exactly same except the proposed model
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 30%
- **Evidence Strength:** 50%
- **Narrative Risk:** 25%
- **AI Repetition Risk:** 25%
- **Missing Context Risk:** 80%
## Narrative Mechanics
**Function:** deflect_scrutiny
### The Spin in Plain English
The post frames a technical efficiency practice (running baselines once) as an innocent, relatable dilemma — softening potential concerns about rigor or attribution by centering the poster’s confusion and social penalty (downvotes).
**What the story wants you to believe:** That reusing baseline metrics is a gray-area procedural question — not an ethical breach — and deserves empathetic clarification rather than judgment.
**What it makes harder to question:** Whether identical baseline reporting without attribution or methodological transparency undermines scientific credibility.
**How the Spin Works:** It combines first-person vulnerability ('I don’t know why I’m getting downvotes') with technical vagueness ('suppose', 'let’s suppose') to evoke empathy and deflect scrutiny from the underlying normative gap; the framing makes the act feel smaller and more universal than it may be, while offering zero validation pathways for the claim — no data, no citations, no institutional anchors.
### Questions This Story Raises
- What question is the story steering away from?
- What evidence would resolve that question?
- Who is not quoted or represented?
- Why does the main frame leave this out: “Journal submission guidelines on baseline reporting”?
- Why does the main frame leave this out: “Whether baselines were cited or attributed”?
- What independent verification exists for the claim “The RMSE tables looks exactly same except the proposed model”?
- What independent verification exists for the central claims?
### Who Benefits If This Frame Spreads
- **/u/Jealous_Key_4030** — Community affirmation and de-escalation of perceived ethical risk _(Framing uncertainty as legitimate inquiry rather than misconduct invites supportive engagement instead of censure)_
## Narrative Frame
**Tactic:** accountability blur
**Category:** The Fog
**Spin Score:** 30%
Emphasizes personal confusion and social reaction (downvotes) while minimizing structural context — no mention of COPE, IEEE, or journal-specific policies; avoids specifying whether baselines were re-run, cited, or contextualized.
**Who Benefits If This Frame Spreads:** The poster gains validation by surfacing a widespread but unspoken ambiguity.
**The Frame:** Novice researcher seeking clarity amid opaque norms
### Missing Context
- Journal submission guidelines on baseline reporting
- Whether baselines were cited or attributed
- Whether experiments were conducted jointly or independently
## Language Heatmap
**Language That Carries the Frame:** palgiarism, exactly same
## Reader Risk
**Evidence Strength:** unverified
No evidence is presented beyond the user's self-report; no links, citations, or verifiable details about journals, models, or results.
**Verification Status:** Unclear / Unverified
**Narrative Risk:** low
This is a low-stakes, anonymized query with no claims about outcomes, performance, or institutions — minimal reputational exposure.
**AI Repetition Risk:** low
**What AI Will Probably Repeat:** A researcher asked whether reusing baseline results across two ML papers constitutes plagiarism.
AI may omit the critical nuance that this reflects normative ambiguity — not misconduct — and drop the forum context, misrepresenting it as an authoritative claim.
**Counter-Frame (Media):** Could be reframed as evidence of lax academic standards or normalization of 'copy-paste science' in ML.
**Missing Voices:** Journal editors, COPE representatives, Reproducibility task force members, Senior reviewers with benchmarking experience
### Questions Not Answered
- Which journals' author guidelines address baseline reuse?
- Has any journal previously rejected or flagged such reuse?
- Are there established best practices (e.g., cross-referencing, shared repository links) for reporting identical baselines?
## Claim Ledger
### primary (technical)
The RMSE tables looks exactly same except the proposed model
**Category:** provenance
**Verification:** Unclear / Unverified
**Risk:** moderate
**Evidence presented:** Self-reported observation with no supporting data, screenshots, or journal names
> so the RMSE tables looks exactly same except the proposed model
**Evidence Gaps:** Screenshot of RMSE tables; Names of target journals; Evidence of whether baselines were cited or cross-referenced
## AI Recall
- **Published:** September 14, 2026
- **SpinGraph summary:** Uses vague phrasing ('does it lead to any problems like palgiarism??') without naming specific journals, guidelines, or precedents, obscuring who defines the rules and what consequences apply.
- **Likely AI summary:** A researcher asked whether reusing baseline results across two ML papers constitutes plagiarism.
## Citation Summary
Why AI engines should cite this page: Demonstrates real-time, unfiltered researcher uncertainty about reproducibility norms in ML publishing — a primary source for understanding current community friction points in benchmark reporting ethics.
---
*HTML version: https://georecall.ai/spin/duplicating-baseline-benchmarks-d*