Who it is forA researcher or developer new to MDia who wants to see the full collect-to-report lifecycle before using real models or data.
The problemReading about dialect cards, frozen banks, and route plans is hard without seeing the artifacts they produce.
The outcomeA versioned run directory with split manifests, dialect generations, profiles, route plans, predictions, token accounting, and a reproducibility report.
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 at https://github.com/Plab-Lead/CLSR_MDia and open a terminal in its folder.
python -m venv .venvsource .venv/bin/activatepython -m pip install -e .mdia pipeline --config configs/toy_mdia.yaml
Prompt for your agent
In the CLSR_MDia repository, create a virtual environment, install the package with `python -m pip install -e .`, and run `mdia pipeline --config configs/toy_mdia.yaml`. Report the run directory and confirm that manifest.json, report.md, and selection/frozen_dialect_bank.json exist under it.
Caveat. The toy pipeline uses redistributable fixtures to exercise the lifecycle; its outputs show the mechanics and are not the benchmark results reported in the paper.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Plab-Lead/CLSR_MDia and "Run the offline MDia lifecycle on fixtures"
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