nemo_gym
nemo_gym
Subpackages
Submodules
nemo_gym.agent_registrynemo_gym.anthropic_converternemo_gym.anthropic_utilsnemo_gym.base_resources_servernemo_gym.base_responses_api_agentnemo_gym.base_responses_api_modelnemo_gym.benchmarksnemo_gym.cli_setup_commandnemo_gym.config_typesnemo_gym.dataset_orchestratornemo_gym.gitlab_utilsnemo_gym.global_confignemo_gym.hf_utilsnemo_gym.openai_utilsnemo_gym.package_infonemo_gym.profilingnemo_gym.promptnemo_gym.registrynemo_gym.responses_converternemo_gym.reward_profilenemo_gym.rollout_collectionnemo_gym.server_metadatanemo_gym.server_statusnemo_gym.server_utilsnemo_gym.skillsnemo_gym.train_data_utils
Package Contents
Functions
Data
API
Resolve a possibly-relative path for reading a built-in or user-supplied file.
Absolute paths are returned unchanged. A relative path is tried first under the current working
directory (the user’s project), then under the Gym install root (PARENT_DIR) where built-in
assets live in both editable and wheel installs. This mirrors config_paths resolution, so a
repo-relative path like resources_servers/<env>/data/example.jsonl resolves by name from any
cwd. If neither exists the cwd candidate is returned so error messages point at the user’s cwd.
Use this for read paths only — never for write targets (e.g. metrics written next to a dataset), which must stay relative to the user’s writable cwd rather than the install root.