How juliodltv/zros works
ZROS is a lightweight Python messaging library with a ROS-like node API, using ZeroMQ for asynchronous topic transport. The main workflow is that application nodes publish and subscribe to topics through a shared broker; node timers and callbacks drive work. Built-in command-line tools publish, echo, and report node status, while optional OpenCV bridges encode and decode image messages. A graph visualizer is present under future/. The graph follows the sampled runtime and README; no other repository files were inspected.
Main entry points: zros.py Node API · zros_pub.py Publish CLI · zros_echo.py Echo CLI · zros_status.py Status CLI
Components 11
Topic Transport
- ZROS broker
zros/zroscore.py
CLI and Discovery
- Publish CLI
zros/zros_pub.py - Echo CLI
zros/zros_echo.py - Status CLI
zros/zros_status.py - Graph visualizer
future/zros_graph.py
Image Bridges
- Raw CV bridge
zros/zros.py - Compressed CV bridge
zros/zros.py
Other components
- Python application
Connections 12
- Python application → Node API: uses API
README.md - Node API → Publisher: creates
zros/zros.py - Node API → Timer: creates
zros/zros.py - Node API → ZROS broker: connects sockets
zros/zros.py - Publish CLI → Node API: creates node
zros/zros_pub.py - Publish CLI → Publisher: publishes payload
zros/zros_pub.py - Echo CLI → Node API: subscribes via
zros/zros_echo.py - Status CLI → Node API: subscribes via
zros/zros_status.py - Graph visualizer → Node API: subscribes via
future/zros_graph.py - Node API → Publisher: broadcasts graph
zros/zros.py - Python application → Raw CV bridge: encodes images
README.md - Python application → Compressed CV bridge: compresses images
README.md