nemo_gym.environment.registry
nemo_gym.environment.registry
Read-only catalog for manifest-backed and legacy environments and benchmarks.
Module Contents
Classes
Functions
Data
API
A discovered runnable unit and its lightweight catalog metadata.
Bases: EnvironmentCatalogEntry
A discovered environment: its name, where it lives, and lightweight metadata.
Bases: ConfigError
A catalog entry is invalid or cannot be selected unambiguously.
Map environment name to its effective manifest or legacy entry under one directory.
Discover one catalog tree without importing or resolving runnable components.
Discover legacy runnable workloads colocated with resources servers.
Every manifest.yaml under tree_dir, without descending into Harbor datasets.
A fetched dataset (nemo_gym.data.tasks.harbor.hub.fetch_ref) lands under environments/harbor/ with a
Harbor manifest.toml at its root and hundreds of task folders below. Those folders are data, not
catalog entries, so the walk stops at any folder holding that file instead of scanning every task. The
folder itself is still read: a local dataset registered by a manifest.yaml at its root gets the same
manifest.toml the first time it is prepared (nemo_gym.data.tasks.harbor.manifest.check_manifest) and
stays a catalog entry.
Hidden folders are skipped at every depth, as recursive task discovery skips them
(nemo_gym.data.tasks.harbor.task.discover_tasks): the fetch stages its clone, a copy of every task, in a hidden
.nemo-gym-harbor-* folder inside the dataset folder, and a first fetch killed mid-clone leaves it there
before the manifest.toml that would stop the walk above it is written.
Read a resource-tree config that carries its own runnable workload.
Discover manifest and legacy runnable units across all workload locations.
Discover environments with standard component-root precedence.
Deep-parse an environment config for the gym list environments <name> inspect view.
Returns domain, description (via read_config_metadata), plus
value, resources_servers (names), agent (the agent type), and dataset names read from
the config’s server blocks. Never raises: an unreadable config yields empty/None fields.
Resolve a catalog name, requiring its kind only for a cross-kind collision.