> 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/mpd/batch/find-when-growth-stops.md).

# Find when growth stops

Know when the cells stop dividing, to transfer and harvest on time.

Many decisions in a batch process hang on one moment, when the cells stop dividing. When the cells are the product, harvest there. In a seed train, transfer before it. In an expression system, it matters when the cells can no longer divide, because of metabolic burden, stress or a toxic product. That limits how much product they can still make.

## Where optical density goes wrong

Optical density (OD) often keeps rising after division has stopped. The cells grow larger, or store carbon, without dividing. A process timed on the OD plateau is timed on the wrong signal.

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2Fgn59DhwnnE7BlrUcphpn%2Fb1-division-stops-v3.svg?alt=media" alt="Three panels over 24 hours for one E. coli culture. Cells/mL levels off at 9.7 hours. Over the next four hours OD600 rises by 60 %, while the count rises only 13 %. CIZE reaches its lowest value at 9.7 hours, then rises as the cells grow larger."><figcaption><p><em>E. coli</em> in a chemically defined medium with 10 mL/L glycerol, in a shake flask. This flask stopped dividing at 9.7 hours. Across the three glycerol levels of the study, division stopped at about 9.6 hours. See <a href="https://help.sbtinstruments.com/mpd/workflows/best-medium.md">Screen growth media</a>.</p></figcaption></figure>

## What BactoBox® shows

The count stops rising when division stops. CIZE adds context. In a batch culture, CIZE falls through exponential growth and stops falling when division stops. If the cells keep taking up carbon without dividing, CIZE then rises, as in the figure above. Read together, the two show the end of growth as it happens, and what the cells do after it.

## Step by step

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2FXsTAHXCI0PTAe2r7i4gc%2Fb1-steps-v3.svg?alt=media" alt="Four steps. 1, track the curve past the end of growth. 2, find where the count stops rising, two points within about 10 %. 3, check that CIZE has stopped falling. It may then rise. 4, set the timing. Harvest at that point, or transfer before it."><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Track past the end of growth

Follow one culture as in [Track a growth curve](https://help.sbtinstruments.com/mpd/track-growth-curve.md). Sample every hour or every two hours, depending on how fast the culture grows. Keep going until the count has clearly stopped rising.
{% endstep %}

{% step %}

### Find where the count stops

Compare each sample with the one before. In general, two samples in a row that differ by less than 10 % can be considered stable. How close they must be depends on how often samples are taken and how fast the culture grows, so the threshold belongs to the process at hand. Technical replicates make the call easier. In our worked example we used 5 % per hour, which is 10 % between samples two hours apart. The [protocol for Identify harvest time](https://help.sbtinstruments.com/mpd/workflows/mpd1/protocol.md) shows the calculation. Take the earliest stable point as the end of growth.
{% endstep %}

{% step %}

### Check CIZE

CIZE should have stopped falling. If it rises while the count holds, the cells are growing larger without dividing.

If the count levels off and then rises again, the culture may have moved on to a second carbon source. Take one more sample a few hours later to be sure.
{% endstep %}

{% step %}

### Set the timing

Decide what the end of growth means for the process. Harvest there, or transfer before it. Measure again when the strain, medium or vessel changes.
{% endstep %}
{% endstepper %}

## The result

The time the culture stops dividing, read on the cells and not on a proxy.

If culturability matters for the product, harvest soon after growth stops. Cells lose culturability in decline phase, and the count does not show it.

Scaling a batch process to a larger vessel? Compare the count and CIZE between the scales, as in [Compare cell state across scales](https://help.sbtinstruments.com/mpd/fed-batch/compare-cell-state-across-scales.md).

## See it in practice

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-corn">:corn:</i> <strong>Identify harvest time</strong></td><td>Real-time counts show when growth stops.</td><td><a href="https://help.sbtinstruments.com/mpd/workflows/mpd1.md">Identify harvest time</a></td></tr><tr><td><i class="fa-ranking-star">:ranking-star:</i> <strong>Screen growth media</strong></td><td>Division stopped at the same time at three glycerol levels, while OD kept rising.</td><td><a href="https://help.sbtinstruments.com/mpd/workflows/best-medium.md">Screen growth media</a></td></tr></tbody></table>

{% hint style="info" %}
The process owner runs the experiments and makes the decisions. We help read what happens in the culture. [Contact us](https://sbtinstruments.com/contact) to plan a study.
{% 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/mpd/batch/find-when-growth-stops.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.
