Skip to content

feat(gymv): add multimodal environment integration - #2700

Draft
rohitrango wants to merge 5 commits into
NVIDIA-NeMo:mainfrom
rohitrango:rohit/gymv-nemorl-integration
Draft

rohitrango wants to merge 5 commits into
NVIDIA-NeMo:mainfrom
rohitrango:rohit/gymv-nemorl-integration

Conversation

@rohitrango

@rohitrango rohitrango commented Aug 24, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • add an env-id-parametric Gym-V resources server and environment configuration
  • add a GymV Responses API agent that preserves the initial multimodal observation in rollout output
  • add focused tests for Gym-V metadata, observation conversion, schemas, and agent behavior

Compatibility

  • based on current NVIDIA-NeMo/Gym main
  • verified all imported NeMo Gym APIs exist on current main

Validation

  • git diff --check
  • direct Python 3.13 syntax compilation for all 15 added Python files
  • focused runtime tests not run because the existing Python environments do not contain the project test/runtime dependencies
  • no uv commands were run

@rohitrango

Copy link
Copy Markdown
Contributor Author

/ok to test 5a8be59

Signed-off-by: rohitrango <rohit.rango@gmail.com>
@rohitrango
rohitrango force-pushed the rohit/gymv-nemorl-integration branch from 5a8be59 to 595a33b Compare August 24, 2026 04:09
@rohitrango

Copy link
Copy Markdown
Contributor Author

/ok to test 595a33b

Signed-off-by: Ali Roshan Ghias <aroshanghias@nvidia.com>
@aroshanghias-nvd

Copy link
Copy Markdown
Contributor

I prepared the minimal NeMo-RL compatibility follow-up as a one-commit PR against the current head branch: rohitrango#1

The commit is based directly on 595a33b and covers the required token/logprob metadata preservation, verify-envelope plumbing, seed-observation deduplication, and focused multi-turn regression coverage.

Validation completed:

  • 240 focused tests passed
  • scoped pre-commit checks passed
  • real two-rollout Gym-V + unchanged NeMo-RL policy/optimizer run completed
  • A/B controls reproduced metadata-loss failures when either required union-ordering fix was removed

No NeMo-RL source changes are required. @rohitrango, merging the linked PR should update this PR branch cleanly.

…ity-review

fix(gymv): preserve NeMo-RL rollout metadata
@copy-pr-bot

copy-pr-bot Bot commented Aug 25, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Signed-off-by: Ali Roshan Ghias <aroshanghias@nvidia.com>
…-token-covered-output

fix(gymv): enforce token-covered rollout bounds
@svcnvidia-nemo-ci svcnvidia-nemo-ci added area:environment Individual environments, benchmarks, verifiers, and environment-specific resources servers feature New capabilities, enhancements, or enablement work needs-review PR is ready for code review and waiting on a reviewer labels Oct 20, 2026
@yaoyu-33
yaoyu-33 marked this pull request as draft November 18, 2026 02:15
@yaoyu-33

Copy link
Copy Markdown
Contributor

We’re doing some cleanup of the open PR list. This PR has had no activity for over a month, so I’ve moved it back to draft.

If this change is still needed, please resolve any merge conflicts and mark the PR ready for review again when it’s ready to merge. Thanks!

@github-actions github-actions Bot removed the sla:triage-overdue Review assignment is over the one-business-day SLA label Nov 18, 2026

This branch was previously deployed

1 inactive (outdated) deployment
public — 595a33ba Deployed Aug 24, 2026 by copy-pr-bot[bot] via release / finalize / notify #1679
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:environment Individual environments, benchmarks, verifiers, and environment-specific resources servers feature New capabilities, enhancements, or enablement work needs-review PR is ready for code review and waiting on a reviewer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants