waymo-open-dataset VS eCAL

Interesting point about the Waymo dataset, though this reply suggests they have higher framerates and just don't release them.

Here's the full list of collisions and disengagements from the California DMV, as well as last year's full safety report from Waymo. Here are Waymo's white papers on readiness determinations, real-world collision analysis, collision avoidance, and simulated reconstructions, just to name a few. Portions of their raw data have also been made available to the community through the Waymo Open Dataset.

According to the dataset.proto file for range_image_compressed, the last channel should give an output whether a lidar point is in no label zone or not.

See https://github.com/waymo-research/waymo-open-dataset for more info.

First, if you haven't already, we encourage to check here to see if your questions have already been answered: https://github.com/waymo-research/waymo-open-dataset/issues

New version (5.94) of the high performance interprocess / interhost communication framework eCAL is available. eCAL supports different transport layer like shared memory for interprocess and udp multicast for interhost communication. It does not force the user to use a specific serialization format but supports some of the standards like google protobuf, capnproto or flatbuffers. The API is wrapped to C, C++, Python, C#, Rust and Go (the last two I never tested ;-)). Here you can find all the documentation. Check out the great applications for monitoring, record and replay. eCAL is Apache 2 licensed, repository hosted here. Have fun :-)

I you just need a fast publish / subscribe framework for windows you can give eCAL a try. The setup is done in less a minute and their is no dependency hell. Just to mention it as alternative. Documentation here

I would concider using eCAL since it blasts everything out of the water in terms of performance and comes with some handy tooling for inspection of messages in-travel.

Source on GitHub: https://github.com/continental/ecal

Check out eCal.

This really makes me want to try https://github.com/continental/ecal with https://github.com/google/flatbuffers to see how they compare. I also know that gpc for cpp at least stops functioning by about 4 MB of request size. Which I find stupid. What if I want to send uncompressed bitmaps!

Congratulations. Well done. eCAL will update as soon as possible to the new release. The new custom header and the n:m pub/sub support are really welcome new features.

Here is their counter callback example: https://github.com/continental/ecal/blob/master/samples/cpp/counter/counter_rec_cb/src/counter_rec_cb.cpp