2 min readfrom Machine Learning

OpenSimula — open implementation of Simula-style mechanism design for synthetic data (in AfterImage) [P]

Our take

Introducing OpenSimula, an innovative addition to our open-source dataset tool AfterImage. This experimental Python implementation leverages Simula-style mechanism design to enhance synthetic data generation. It addresses the need for controlled diversity in reasoning tasks, allowing users to explore varying axes of complexity. OpenSimula facilitates effective factor sampling and meta-prompt diversification, ultimately refining outputs through a structured feedback loop. While this API is experimental, it offers a powerful framework for generating more robust data. We invite your feedback as we continue to evolve this tool.

Hi r/MachineLearning,

We added OpenSimula to our open-source dataset tool AfterImage: an experimental Python implementation of the Simula mechanism-design recipe from Davidson et al. (TMLR, PDF; framing also in this research blog).

Problem it targets:

For some SFT/eval setups you care less about “one prompt → one answer” and more about controlled diversity over a reasoning space: which axes of variation exist, how you joint-sample them, and how you stress-test generations before they land in a JSONL file.

What the code actually does (high level):

LLM-built factor taxonomiesweighted mix sampling over factors → meta-prompt diversification (+ optional complexification) → requirement critic loop with refinement → optional double-critic gate for verifiable MCQ. Artifacts are a versioned opensimula/ checkpoint (manifest, taxonomy bundle, sampling strategy) plus append-only JSONL for accepted points. You can plug in the same GenerationMonitor we use elsewhere for observability into generation metrics, or bridge scenarios into ConversationGenerator via a small callback.

Hard disclaimers (please read):

  • This is not a Google product, not a reference port of anything internal—just our read of the published recipe in the paper.
  • API is explicitly experimental and may change.
  • Cost and latency explode if you remove the caps on taxonomy width/depth; wide trees are many structured calls unless you tune bounds.
  • “Mechanism design” here helps structure the data-generating process; it does not magically fix model collapse or bad teacher models.

Code & docs:

I genuinely would love hear your feedback if any.

submitted by /u/Individual-Road-5784
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article