nemo_gym.orchestration.export_step
nemo_gym.orchestration.export_step
One post-run export of a submitted benchmark, with its outcome kept in a result file.
The driver step of a job runs this after gym eval run, once per configured export:
python3 -m nemo_gym.orchestration.export_step <exporter> +key=value .... The exporters themselves know nothing
about it; what a job needs on top of them (telling several exports apart afterwards, not repeating one that
finished, retrying one that was interrupted) lives here.
Module Contents
Functions
Data
API
python3 -m nemo_gym.orchestration.export_step <exporter> +key=value ...: the settings are Hydra overrides.
Run the post-run exporter name on the run rollouts_jsonl_fpath points at.
result_json_fpath is a setting of this step, not of the exporters. When it is set, the outcome is also kept
in that file, which is how a job that runs several exports can tell them apart afterwards: no file means never attempted, running means interrupted (for
example at the walltime), and anything else is a final result. An export that already succeeded or was
skipped is not repeated; a failed or interrupted one is retried. A configuration error is recorded as a
failed result too, and still raised.