Skip to content

Conversation

@phiraml
Copy link

@phiraml phiraml commented Jan 9, 2026

PR Type

  • RL Environment PR - Complete Environment Snapshot & Zero-Training sections
  • [X ] Non-Environment PR - Complete Description, Related Issues & Type of Change sections

📝 General Information

Description

Related Issues

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Code refactor (no functional changes)
  • Build/CI/CD related changes
  • Other (please describe): Vision evals

✅ Developer & Reviewer Checklist

  • Code follows project style (black, isort, flake8 pass with pre-commit)
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes
  • [] Docstrings added for all new public classes / functions
  • [-] If .env vars required, did you add it to the .env.example in repo root?

phiraml and others added 3 commits January 9, 2026 18:28
Copy link
Collaborator

Choose a reason for hiding this comment

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

why is this in the pr?

@dmahan93
Copy link
Collaborator

can you move this to a subfolder, vision evals, and add a readme that contains what's been tested and how they compare to other implementations?

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.

3 participants