Skip to content
3 changes: 3 additions & 0 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,9 @@ where = [""]
# tightening the first pattern to "torchtitan.*" cannot silently drop it.
include = ["torchtitan*", "torchtitan_recipes*"]

[tool.setuptools.package-data]
"torchtitan.experiments.rl.examples.verifiers" = ["verifiers_env.toml"]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is because when release, python packaging includes .py files automatically, but not .toml files. This will not make verifiers a hard dependency

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe i am wrong, but this doesn't smell right. I will take a look at the .toml, but i wonder if theres a more elegant solution. If this is the only way, we should add a comment here on why we need it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The toml is consumed by Verifiers. The alternative is to translated into torchtitan VerifiersRollouter.Configs but the Verifiers has so many config fields which I just leave verifiers' config system as is

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strongly against this thing here, commented at https://github.com/pytorch/torchtitan/pull/4356/changes#r3919769394


[tool.pytest.ini_options]
addopts = ["--showlocals"] # show local variables in tracebacks
testpaths = ["tests"]
Expand Down
1 change: 1 addition & 0 deletions torchtitan/experiments/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -20,5 +20,6 @@
"alphabet_sort",
"dapo_math",
"search_r1",
"verifiers",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

verifiers folder may have N experiments, right? if we had verifiers/swe_bench and verifiers/dapo_math would this still work ok?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it depends on how we want to organize verifiers examples. I think I will update the current code to be verifiers/components and verifiers/dapo_math, so here will be update correspondingly.

]
)
8 changes: 7 additions & 1 deletion torchtitan/experiments/rl/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Together, the unified model, batch-invariant mode, and single training stack pro

Note: Unified-model performance varies by model, input shape, and parallelism: it can trail native vLLM in inference-only workloads but outperform it end to end in some RL configurations. Batch invariance trades throughput for exact numerics and can be used for debugging or controlled on-policy studies.

[Architecture](#architecture) · [Write an experiment](#write-an-experiment) · [DAPO Math](./examples/dapo_math) · [Observability](#observability) · [Quick Start](#quick-start)
[Architecture](#architecture) · [Write an experiment](#write-an-experiment) · [DAPO Math](./examples/dapo_math) · [Verifiers](./examples/verifiers) · [Observability](#observability) · [Quick Start](#quick-start)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you proposing that we delete dapo_math based on our Rollouter and keep only the verifiers-based one? I am not sure i 100% agree with it. What were your thoughts when you decided that?

@wwwjn wwwjn Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I want to keep both. Verifiers examples is trying to not emphasis on DAPO math , but just as an example for verifiers. The DAPO-math is the official support we have, which is a stand-alone task we used for stress-testing our RL and verifiers-free.


> **Note:** TitanRL is under active development. APIs and configurations may change.

Expand Down Expand Up @@ -94,6 +94,12 @@ Train on verifiable math with DAPO loss and Math-Verify rewards.

[Run DAPO Math](./examples/dapo_math)

### Verifiers: optional integration example

Run the DAPO Math workload with Verifiers managing the local rollout environment.

[Run Verifiers](./examples/verifiers)

### Search-R1: multi-turn tool use

Train a model to issue search queries, consume tool responses, and answer with an exact-match reward.
Expand Down
31 changes: 31 additions & 0 deletions torchtitan/experiments/rl/examples/verifiers/README.md

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am missing a more general readme of how to adapt verifiers task to our setup.

Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Verifiers

This example keeps the existing [DAPO Math](../dapo_math) recipe unchanged and replaces only its rollout path with [Verifiers](https://github.com/PrimeIntellect-ai/verifiers). Training still uses the filtered DAPO-Math dataset, AIME 2025 validation, DAPO loss, and the Qwen3-4B-Base model.

Verifiers runs a single-turn math task with its `null` harness. The runtime is a local subprocess; there is no Docker or remote sandbox and no tools are exposed. Do not use this configuration for untrusted code execution.

Verifiers is optional, and all Verifiers integration code lives in this example.
Other TitanRL recipes do not require it.

## Setup

Follow the [TitanRL setup](../../README.md), then install this example's dependencies:

```bash
pip install -r torchtitan/experiments/rl/examples/verifiers/requirements.txt

python scripts/download_hf_assets.py \
--repo_id Qwen/Qwen3-4B-Base \
--local_dir torchtitan/experiments/rl/example_checkpoint \
--all
```

## Run

```bash
python -m torchtitan.experiments.rl.train \
--module verifiers \
--config rl_dapo_qwen3_4b_verifiers_8k
```

Use `rl_dapo_qwen3_4b_verifiers_32k` for the 32K response variant.
11 changes: 11 additions & 0 deletions torchtitan/experiments/rl/examples/verifiers/__init__.py
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Copyright (c) Meta Platforms, Inc. and affiliates.
# All rights reserved.
#
# This source code is licensed under the BSD-style license found in the
# LICENSE file in the root directory of this source tree.

from torchtitan.experiments.rl.examples.verifiers.rollouter import (
VerifiersMathRollouter,
)

__all__ = ["VerifiersMathRollouter"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is about some general reusable infra, would be good (for both human and agent) if you could provide a summary of the plumbing work + breakdown on what each file is about.

Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Copyright (c) Meta Platforms, Inc. and affiliates.
# All rights reserved.
#
# This source code is licensed under the BSD-style license found in the
# LICENSE file in the root directory of this source tree.

from torchtitan.experiments.rl.examples.verifiers.components.dataset import (
VerifiersTaskDataset,
VerifiersTaskSample,
)
from torchtitan.experiments.rl.examples.verifiers.components.env_server import (
VerifiersEnvServer,
)
from torchtitan.experiments.rl.examples.verifiers.components.rollouter import (
VerifiersRewardFn,
VerifiersRollouter,
)

__all__ = [
"VerifiersEnvServer",
"VerifiersRewardFn",
"VerifiersRollouter",
"VerifiersTaskDataset",
"VerifiersTaskSample",
]
121 changes: 121 additions & 0 deletions torchtitan/experiments/rl/examples/verifiers/components/dataset.py
Original file line number Diff line number Diff line change
@@ -0,0 +1,121 @@
# Copyright (c) Meta Platforms, Inc. and affiliates.
# All rights reserved.
#
# This source code is licensed under the BSD-style license found in the
# LICENSE file in the root directory of this source tree.

from __future__ import annotations

import importlib
import random
import sys
from collections.abc import Iterator
from dataclasses import dataclass, field
from typing import Any

from torchtitan.config import Configurable


def register_local_taskset_alias(taskset_id: str) -> str:
"""Register a dotted local taskset under an ID Verifiers 0.3.0 can import."""
if "." not in taskset_id or "/" in taskset_id:
return taskset_id

module = importlib.import_module(taskset_id)
alias = taskset_id.replace(".", "_").lower()
existing = sys.modules.get(alias)
if existing is not None and existing is not module:
raise ValueError(f"taskset alias {alias!r} is already registered")
sys.modules[alias] = module
return alias


@dataclass(frozen=True, kw_only=True, slots=True)
class VerifiersTaskSample:
"""Serialized task data dispatched to a stateless Verifiers EnvServer."""

task_data: dict[str, Any]


class VerifiersTaskDataset(Configurable):
"""Load a Verifiers taskset into TorchTitan's resumable dataset contract."""
Comment on lines +40 to +41

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this sounds just like an indexed dataset + mix using VerifiersTaskSample.

Should we use grain?
Do we actually support >1 task?

I am not very convinced that we need to implement a new dataset class just for verifiers.


@dataclass(kw_only=True, slots=True)
class Config(Configurable.Config):
# Importable Verifiers taskset plugin ID or local dotted module path.
taskset_id: str
# Keyword arguments used to construct the taskset's config.
taskset_args: dict[str, Any] = field(default_factory=dict)
# Optional task cap; required when the taskset is infinite.
num_tasks: int | None = None
# Seed used to produce a reproducible task order.
seed: int = 42
# Whether to reshuffle the task order at initialization and each epoch.
shuffle: bool = True

def __post_init__(self) -> None:
if self.num_tasks is not None and self.num_tasks <= 0:
raise ValueError("num_tasks must be positive")

def __init__(self, config: Config) -> None:
# Verifiers is an example-only dependency. Keep the import local so the
# rest of TorchTitan RL does not require it.
from verifiers.v1.utils.loaders import load_taskset, taskset_config_type

taskset_id = register_local_taskset_alias(config.taskset_id)
taskset_config = taskset_config_type(taskset_id).model_validate(
{"id": taskset_id, **config.taskset_args}
)
taskset = load_taskset(taskset_config)
if config.num_tasks is None and taskset.INFINITE:
raise ValueError(
f"Verifiers taskset {config.taskset_id!r} is infinite; "
"num_tasks is required"
)
tasks = list(
taskset if config.num_tasks is None else taskset.head(config.num_tasks)
)
if not tasks:
raise ValueError(
f"Verifiers taskset {config.taskset_id!r} yielded no tasks"
)
if config.num_tasks is not None and len(tasks) != config.num_tasks:
raise ValueError(
f"Verifiers taskset {config.taskset_id!r} yielded {len(tasks)} "
f"tasks, expected {config.num_tasks}"
)

self._samples = [
VerifiersTaskSample(task_data=task.data.model_dump(mode="json"))
for task in tasks
]
self._rng = random.Random(config.seed)
self._shuffle = config.shuffle
self._order = list(range(len(self._samples)))
self._position = 0
if self._shuffle:
self._rng.shuffle(self._order)

def __iter__(self) -> Iterator[VerifiersTaskSample]:
return self

def __next__(self) -> VerifiersTaskSample:
if self._position == len(self._order):
self._position = 0
if self._shuffle:
self._rng.shuffle(self._order)
sample = self._samples[self._order[self._position]]
self._position += 1
return sample

def state_dict(self) -> dict:
return {
"rng_state": self._rng.getstate(),
"order": list(self._order),
"position": self._position,
}

def load_state_dict(self, state_dict: dict) -> None:
self._rng.setstate(state_dict["rng_state"])
self._order = list(state_dict["order"])
self._position = int(state_dict["position"])
Loading
Loading