You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Vehicle Researcher
bc747137e3
|
5 years ago | |
|---|---|---|
| .. | ||
| include | 6 years ago | |
| messaging | 5 years ago | |
| .dockerignore | 5 years ago | |
| .gitignore | 5 years ago | |
| Dockerfile | 5 years ago | |
| README.md | 5 years ago | |
| SConscript | 5 years ago | |
| SConstruct | 5 years ago | |
| __init__.py | 6 years ago | |
| azure-pipelines.yml | 5 years ago | |
| car.capnp | 5 years ago | |
| generate_javascript.sh | 6 years ago | |
| install_capnp.sh | 5 years ago | |
| log.capnp | 5 years ago | |
| maptile.capnp | 6 years ago | |
| service_list.yaml | 5 years ago | |
| services.py | 5 years ago | |
README.md
What is cereal?
cereal is both a messaging spec for robotics systems as well as generic high performance IPC pub sub messaging with a single publisher and multiple subscribers.
Imagine this use case:
- A sensor process reads gyro measurements directly from an IMU and publishes a sensorEvents packet
- A calibration process subscribes to the sensorEvents packet to use the IMU
- A localization process subscribes to the sensorEvents packet to use the IMU also
Messaging Spec
You'll find the message types in log.capnp. It uses Cap'n proto and defines one struct called Event.
All Events have a logMonoTime and a valid. Then a big union defines the packet type.
Pub Sub Backends
cereal supports two backends, one based on zmq, the other called msgq, a custom pub sub based on shared memory that doesn't require the bytes to pass through the kernel.
Example
import cereal.messaging as messaging
# in subscriber
sm = messaging.SubMaster(['sensorEvents'])
while 1:
sm.update()
print(sm['sensorEvents'])
# in publisher
pm = messaging.PubMaster(['sensorEvents'])
dat = messaging.new_message()
dat.init('sensorEvents', 1)
dat.sensorEvents[0] = {"gyro": {"v": [0.1, -0.1, 0.1]}}
pm.send('sensorEvents', dat)