Skip to content

Conversation

@relh
Copy link
Contributor

@relh relh commented Jan 8, 2026

Summary

  • Stop assigning render_mode in the CoGames env wrapper.
  • Keep the render_mode argument for API compatibility.

Context

MettaGridPufferEnv exposes a read‑only render_mode that always reports "ansi". Assigning to it raises an AttributeError. The simplest fix is to accept render_mode in the wrapper but ignore it so CoGames training runs without error and behavior stays unchanged.

Testing

  • python -m pufferlib.pufferl train cogames.cogs_v_clips.training_facility.harvest --train.total-timesteps 2000 --vec.num-envs 1 --vec.num-workers 1 --train.batch-size 64 --train.minibatch-size 64 --train.device cpu --env.render-mode none

@relh relh changed the title Guard render_mode assignment in cogames env Fix CoGames env init with read-only render_mode Jan 8, 2026
@relh relh changed the title Fix CoGames env init with read-only render_mode Pass render_mode into MettaGrid CoGames env Jan 8, 2026
@relh relh changed the title Pass render_mode into MettaGrid CoGames env Ignore render_mode for CoGames MettaGrid env Jan 8, 2026
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.

1 participant