Rebuild a task set¶
For agent evaluators who want to run on a published task set, such as medomni-bench/v1, built from their own copy of the data. You build every <template>@<cohort> in the set from its config with Studio's builder, medomni-v1, and check each build. Bench then runs the built set.
Before you start¶
- Your copy of each dataset in the set is connected. See Connect your data.
- Space for the cache and the atom tasks in your workspace, on a disk with room for the dataset copies you use.
Steps¶
-
Build the cache for each dataset in the set.
medomni cache build mimic-iv -
Build the set. Every
<template>@<cohort>in it is built under every arm the set lists, by the builder the set names.medomni studio task build --set medomni-bench/v1 -
Check every build.
medomni studio task check --set medomni-bench/v1
Check¶
medomni studio task check --set medomni-bench/v1 runs the checks of medomni studio task check <template>@<cohort> on every pair in the set, and lists each pair as passing or failing. medomni bench run runs the checks on built tasks again before it starts.
Your results carry each task's config hash. Results with the same config hash used the same task config; the hash doesn't show that your copy of the data matches. To compare a build with someone else's, compare the per-step patient counts in your build manifests by hand.
Keep data local
The cache, built atom tasks, answers, traces and the results file contain patient data. Do not commit, upload or share them.
Where next¶
- Test your agent: run on the set you built.
- Build: the steps the counts come from.
- Cache: what the cache holds.