> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/advanced/raw-measurement-files.md).

# Raw measurement files

The raw file behind each measurement, and the Python package that reads it. For custom solutions only.

{% hint style="danger" %}

### Only as part of a custom solution

Raw measurement files are for work we scope with you as a [custom solution](https://help.sbtinstruments.com/advanced/what-is-a-custom-solution.md). Their format can change with any software update. [Contact us](https://sbtinstruments.com/contact) before you build anything on them.
{% endhint %}

## Download the files

In Access, click *Download summary* in the side bar. Pick a period under *Date filter* and download *measurements.zip*. See [Export your data](https://help.sbtinstruments.com/more/software/export-your-data.md).

The ZIP file holds one BDR file (.bdr) per measurement. Its name holds your BactoBox® ID, the start time and the measurement ID, for example `measure-bb2241039-2026-01-08T155239+0100-S02.bdr`.

{% hint style="info" %}
The ZIP file is named like a device data bundle, for example `bb2241039-2026-01-09.zip`. The two hold different things.
{% endhint %}

## Read the files with Pilus

*Pilus* is our open-source Python package for BDR files. It converts a BDR file to a CSV file.

```shell
uv run pilus convert measure-bb2221028-A02.bdr measure-bb2221028-A02.csv
```

Find the code and the instructions on [GitHub](https://github.com/sbtinstruments/pilus). *Pilus* is released under the [MIT License](https://opensource.org/license/mit).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sbtinstruments.com/advanced/raw-measurement-files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
