Message Passing with ZMQ

[ropresearch]

PR Type

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

---

📝 General Information

Description

This PR introduces a ZMQ integration in the Atropos API to create a message bus that aggregates rollout data from instances of the same environment to push for WandB.

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):

---

✅ 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?

[dmahan93]

we should probably not change anything on the server.py, and leave the zmq as a separate system