> 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/software/miscellaneous/pilus.md).

# Pilus

Python toolbox for working with BactoBox® data files on your computer

*Pilus* is an open-source Python package that turns your BactoBox® data files into something you can load, analyze, and plot. It reads the binary formats your BactoBox® produces — [BDR file](/software/file-formats/bdr-file.md) and [IQS file](/software/file-formats/iqs-file.md) — and converts them to friendlier formats such as *summary.csv*.

{% hint style="info" %}

## Advanced feature 🧩

This is an advanced feature. We only support advanced features through a *custom solution*. Contact SBT for details.
{% endhint %}

## Install

*Pilus* uses [`uv`](https://docs.astral.sh/uv/) to manage dependencies. Once you have `uv`, install *Pilus* and its dependencies:

```shell
uv sync --all-extras
```

## Convert a BDR file to CSV

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

{% hint style="info" %}
Find the source code, full instructions, and more examples on [GitHub](https://github.com/sbtinstruments/pilus). *Pilus* is released under the [MIT License](https://opensource.org/license/mit).
{% endhint %}


---

# 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/software/miscellaneous/pilus.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.