> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuneplane.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# tp eval

> Run a recipe's native evaluation

```bash theme={"theme":{"light":"github-light","dark":"github-dark-dimmed"}}
tp eval my-grpo --model Qwen/Qwen2.5-7B
```

Runs the evaluation that ships with the recipe's own framework — NeMo-RL's evaluation config, verl's
SFT validation loop. This is the framework's notion of "how is it doing", on the framework's terms.

That makes it different from [`tp bench`](https://docs.tuneplane.ai/en/cli/bench), which runs standard academic benchmarks
through an external harness so results are comparable across runs, methods, and other people's
models. Reach for `tp eval` while iterating on one method; reach for `tp bench` when comparing.

It can also run automatically after training:

```bash theme={"theme":{"light":"github-light","dark":"github-dark-dimmed"}}
tp submit my-grpo --profile h200:8 --then eval
```

## `tp eval`

Run a recipe's native evaluation

```bash theme={"theme":{"light":"github-light","dark":"github-dark-dimmed"}}
tp eval <EXP> [options]
```

| Argument | Description |
| - | - |
| `EXP` | Experiment name or path (**required**) |

| Option | Description |
| - | - |
| `--run-id` | VeRL SFT: the training run id that receives the validation samples |
| `--model` | NeMo-RL or VeRL SFT: HF model path / Hub id |
| `--eval-config` | NeMo-RL: explicit evaluation config path |
| `--data` | verl: explicit evaluation data path |
| `--step` `<int range>` | VeRL SFT: the training step the exported checkpoint belongs to |
| `--profile` | Hardware profile (managed by the server registry; `tp status` lists the available values) |
| `--allow-dirty` | Allow uncommitted changes in the working tree |
| `--dry-run` | Only print the command that would be submitted |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.