External data-loader example

<picture> <source media="(max-width: 480px)" srcset="https://static.rerun.io/external_data_loader_cpp/83cd3c2a322911cf597cf74aeda01c8fe83e275f/480w.png"> <source media="(max-width: 768px)" srcset="https://static.rerun.io/external_data_loader_cpp/83cd3c2a322911cf597cf74aeda01c8fe83e275f/768w.png"> <source media="(max-width: 1024px)" srcset="https://static.rerun.io/external_data_loader_cpp/83cd3c2a322911cf597cf74aeda01c8fe83e275f/1024w.png"> <source media="(max-width: 1200px)" srcset="https://static.rerun.io/external_data_loader_cpp/83cd3c2a322911cf597cf74aeda01c8fe83e275f/1200w.png"> </picture>

This is an example executable data-loader plugin for the Rerun Viewer.

It will log C++ source code files as markdown documents. To try it out, compile it and place it in your $PATH, then open a C++ source file with Rerun (rerun file.cpp).

Consider using the send_columns API for data loaders that ingest time series data from a file. This can be much more efficient that the stateful log API as it allows bundling component data over time into a single call consuming a continuous block of memory.