This page is for version 0.7.0.
For other versions, use one of these documentation indexes:
- Main (default): https://docs.nvidia.com/nemo/gym/main/llms.txt
- 0.7.0: https://docs.nvidia.com/nemo/gym/v0.7.0/llms.txt
- 0.6.0: https://docs.nvidia.com/nemo/gym/v0.6.0/llms.txt
- 0.5.1: https://docs.nvidia.com/nemo/gym/v0.5.1/llms.txt
- 0.5.0: https://docs.nvidia.com/nemo/gym/v0.5.0/llms.txt
- 0.4.0: https://docs.nvidia.com/nemo/gym/v0.4.0/llms.txt
- 0.3.0: https://docs.nvidia.com/nemo/gym/v0.3.0/llms.txt
- 0.2.1: https://docs.nvidia.com/nemo/gym/v0.2.1/llms.txt
Technical notes that document infrastructure decisions, performance investigations, and design rationale behind NeMo Gym.
System Design
How NeMo Gym components interact during startup, execution, and rollout collection.
architectureserver-infraResponses API Evolution
Why NeMo Gym uses the Responses API and how it differs from Chat Completions.
api-designschemaSWE RL Infrastructure Case Study
Infrastructure challenges and deployment topology for SWE RL training.
swe-rlcase-studyaiohttp vs httpx
Why NeMo Gym uses aiohttp instead of httpx for async HTTP.
server-infraperformance