nemo_gym.tasks.harbor.cli
nemo_gym.tasks.harbor.cli
gym eval run <folder | harbor:dataset> --agent <name>: prepare a taskset and run it.
Preparation writes, under results/harbor/<taskset>/:
tasks.jsonl: one materialized row per loadable task;skipped.json: omitted task IDs and reasons (empty when all tasks load);run_config.yaml: the resources server, agent and environment server blocks.
Then the ordinary end-to-end rollout collection runs with that config plus the selected agent, environment server and model configs.
Module Contents
Classes
Functions
Data
API
Write run_config.yaml and return it with the Hydra overrides for collection.
Fetch (for hub references) and load the tasks, then write the rows file.
A task folder that does not load is skipped with a warning (and listed in
PreparedTaskset.skipped) so the rest of the dataset still prepares.
Map --agent NAME[/FLAVOR] to responses_api_agents/<NAME>/configs/<FLAVOR>.yaml.
NAME may omit a trailing _agent (hermes selects hermes_agent).
Entry point for gym eval run <target> ....