Who it is forA reviewer, auditor, or researcher who needs to check the reported MDia accuracy and generated-token numbers without rerunning model inference.
The problemPublished accuracy and token savings are hard to trust unless the numbers can be recomputed from the source records.
The outcomeA fresh output directory with recomputed aggregates, paired intervals, frontiers, a VALIDATION.json file, and exported PNG and SVG figures.
What you need first
- Python 3.10+ for the offline toy pipeline, or Python 3.11+ for the release reproduction
- A terminal and git for cloning the repository
- No API keys are needed for the toy pipeline or the offline release reproduction
- For new model inference, benchmark inputs from their original sources and provider access (see docs/extending.md)
Steps
- Clone the repository and open a terminal in its folder.
python3 -m venv .venv-evidencesource .venv-evidence/bin/activatepython -m pip install -r requirements-evidence.lock.txtpython scripts/verify_mdia_release.pypython scripts/reproduce_mdia_release.py --output runs/mdia-results-20261005
Prompt for your agent
In the CLSR_MDia repository, set up the .venv-evidence environment from requirements-evidence.lock.txt, run scripts/verify_mdia_release.py, then run scripts/reproduce_mdia_release.py with a fresh output directory. Report whether all checks pass by reading VALIDATION.json, and list the exported table and figure files.
Caveat. This command recomputes analyses from released scalar records and runs offline; it does not run new model inference, which needs the original benchmark inputs and providers.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Plab-Lead/CLSR_MDia and "Reproduce the released MDia benchmark tables offline"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer