Extend evaluator with render mode control#331
Merged
daphne-cornelisse merged 5 commits into2.0from Mar 9, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
It can be useful to render based on a particular criterion. For example, instead of always displaying the first env, you may want to continually show the worst scenario in a batch of scenes. This was not possible because
vec_log(), which is used to collect stats from the envs, aggregates across agents and envs, losing per-env granularity.Solution
env_log()C binding that returns statistics per environment without aggregating across envs.first,random,worst_score,worst_collision) viarender_select_modein the eval config.Evaluatorruns a stats-only rollout first, selects the target env usingenv_log, then renders that env in a second rollout.Pipeline
Before
Before, the eval pipeline looked like this:
After
Now, if the render mode is not fixed nor random, it looks like this:
Logging example