> 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/measurements-explained/limits-of-detection.md).

# Limit of detection

BactoBox® counts individual particles. If there are too *few* particles, the concentration estimate is too uncertain. If there are too *many* particles, we can't tell them apart. Therefore, we have limit of detection (LoD). BactoBox® outputs concentrations in these ranges:

* 30 000–5 000 000 **cells/mL** (3·10⁴ to 5·10<sup>6</sup> cells/mL)
* 30 000–5 000 000 **total/mL** (3·10⁴ to 5·10<sup>6</sup> total/mL)

{% hint style="success" %}

## Target 0.5–4 million cells/mL for fast results

The more things to count, the faster we are certain about the concentration. Give BactoBox® something to work with and it triggers the *Fast results* feature :fast\_forward:.

Make a dilution series and [**measure the most diluted sample first**](/advanced/advanced-sample-preparation/hit-the-right-concentration/dilute-1-100.md#measure-the-most-diluted-sample-first). Aim for 0.5–4 million cells/mL.
{% endhint %}

The figure below shows how the LoD influences the BactoBox® output. The figure uses *total/mL* as an example but the very same thing is true for *cells/mL*.

<img src="https://2483617760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCaBGkox4Fd7NCFFCF47X%2Fuploads%2Fgit-blob-b9e86b103ae6188fd076834ae13046a58ed02a08%2Flimit-of-detection--effect-on-bactobox-output.excalidraw.svg?alt=media" alt="Limit of detection (LoD) and how they influence the BactoBox® output." class="gitbook-drawing">

{% hint style="info" %}

## Don't know the concentration of your sample?

Make a dilution series and [**measure the most diluted sample first**](/advanced/advanced-sample-preparation/hit-the-right-concentration/dilute-1-100.md#measure-the-most-diluted-sample-first). This avoids clogging your BactoBox® setup. It also avoids carry-over from your previous sample vial.

Once you are above the lower limit of detection (30 000 cells/mL), target 0.5–4 million cells/mL.
{% endhint %}

## Above the upper limit

Cross the upper limit and BactoBox® can no longer tell the particles apart, so it stops with an error instead of a result. A concentration above 5 000 000 particles/ml also risks clogging the flow cell.

<div data-with-frame="true"><figure><img src="https://2483617760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCaBGkox4Fd7NCFFCF47X%2Fuploads%2Fgit-blob-21cac63400f74b8d1618b2aa95a6feee7b80fe62%2Fscreenshot--error-3000.png?alt=media" alt="BactoBox® error screen: Error 3000, too many particles (above 5 000 000 particles/ml). Discard sample, clean device and use a higher dilution."><figcaption><p>Above the upper limit, BactoBox® shows Error 3000 instead of a result.</p></figcaption></figure></div>

Discard the sample, clean the device, and measure again at a higher dilution.

## Single cell at a time

The following figure shows how both too *few* and too *many* cells cause trouble.

<figure><img src="https://2483617760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCaBGkox4Fd7NCFFCF47X%2Fuploads%2Fgit-blob-4f679bd84d4fa6715122ec17ab145b7ff1eb1eb0%2Flod-figure--electric-field.excalidraw.svg?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/measurements-explained/limits-of-detection.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.
