Dataframes

Rerun, at its core, is a database. As such, you can always get your data back in the form of tables (also known as dataframes, or records, or batches...).

This can be achieved in three different ways, depending on your needs:

This page is meant as a reference to get you up and running with these different solutions as quickly as possible. For an in-depth introduction to the dataframe API and the possible workflows it enables, check out our Getting Started guide or one of the accompanying How-Tos.

We'll need an RRD file to query. Either use one of yours, or grab some of the example ones, e.g.:

curl 'https://app.rerun.io/version/latest/examples/dna.rrd' -o - > /tmp/dna.rrd

Using the dataframe API

The following snippet demonstrates how to query the first 10 rows in a Rerun recording using latest-at (i.e. time-aligned) semantics:

snippet: reference/dataframe_query

Check out the API reference to learn more about all the ways that data can be searched and filtered:

Using the blueprint API to configure a dataframe view

The following snippet demonstrates how visualize an entire Rerun recording using latest-at (i.e. time-aligned) semantics by displaying the results in a dataframe view:

snippet: reference/dataframe_view_query

Aside: re-using blueprint files from other SDKs

While the blueprint APIs are currently only available through Python, blueprints can be saved and re-logged as needed from any language our SDKs support.

First, save the blueprint to a file (.rbl by convention) using either the viewer (Menu > Save blueprint) or the python API:

snippet: reference/dataframe_save_blueprint

Then log that blueprint file in addition to the data itself:

snippet: reference/dataframe_view_query_external

Check out the blueprint API and log_file_from_path references to learn more:

You can learn more in our dedicated page about blueprint re-use.

Setting up dataframe view manually in the UI

The same dataframe view shown above can be configured purely from the UI: