Skip to content

Add typed Hydra environment configuration MVP - #851

Draft
cvolkcvolk wants to merge 4 commits into
mainfrom
cvolk/feature/hydra-config-spike
Draft

Add typed Hydra environment configuration MVP#851
cvolkcvolk wants to merge 4 commits into
mainfrom
cvolk/feature/hydra-config-spike

Conversation

@cvolkcvolk

@cvolkcvolk cvolkcvolk commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

Add typed Hydra experiment configuration

Detailed description

  • Move reusable Arena environment and experiment Cfg types into core and resolve concrete environment schemas through EnvironmentRegistry.
  • Keep the YAML-driven Hydra runner as an example frontend with a required suite path and sequential experiment dispatch through eval-runner Jobs.
  • Preserve the legacy argparse path while making the experiment-to-Job compatibility boundary explicit.
  • Cover composition, registry resolution, invalid input, Job mapping, and simulator subprocess execution.

Show how structured environment configuration can compose before
simulator startup and feed the existing evaluation loop.

Keep the legacy JSON and argparse evaluation path available while the
remaining environments migrate.

Signed-off-by: Clemens Volk <cvolk@nvidia.com>
Keep the reusable environment and evaluation Cfg models out of the example package. Resolve concrete environment schemas through EnvironmentRegistry while retaining the Hydra runner as an example frontend.

Signed-off-by: Clemens Volk <cvolk@nvidia.com>

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

We should move this out of "example_environment_base" as it would essentially be our base environment contract (requiring a .build())

Signed-off-by: Clemens Volk <cvolk@nvidia.com>
Rename the declarative config so Job names only runtime work items.

Make the Hydra-to-argparse boundary explicit in the runnable example.

Signed-off-by: Clemens Volk <cvolk@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant