> 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/fed-batch/compare-cell-state-across-scales.md).

# Compare cell state across scales

When a process performs differently at another scale, compare cell size between scales. During expression, we observe cells often make the most product in a narrow size band.

A process that worked in one vessel often behaves differently in another. Mixing, oxygen transfer and feeding change with scale, and the cells respond. Titer shows that something changed. It does not show when, or how.

## What BactoBox® shows

The count and CIZE describe the state of the cells at every sample. During expression, we observe that cells often make the most product in a narrow size band. We have seen CIZE settle on a plateau after induction in multiple customer processes. Cell size can therefore explain why one scale performs better or worse than another.

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2FEh6WEXFetruCo5obumMq%2Ff2-size-band-v3.svg?alt=media" alt="Illustration in two panels. Left, CIZE after induction: the reference scale stays inside a shaded best band, while the new scale drifts above it. Right, product per cell against CIZE: a peak inside the best band, with the reference at the top and the new scale lower on the right."><figcaption><p>Illustration. Map product per cell against CIZE in reference runs to find the band for the process.</p></figcaption></figure>

## Step by step

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2Fo3WLtAZMNopjMG3D1jBs%2Ff2-steps-v3.svg?alt=media" alt="Four steps. 1, map cells/mL and CIZE at the reference scale. 2, run the new scale with the same sampling. 3, overlay the two runs. 4, find where they part, and look at feed, oxygen and mixing at that point."><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Map the reference scale

Follow the count and CIZE through a run at the scale that works. Note when the feed starts, when induction happens and when the harvest is, and measure the titer. See [Track a growth curve](https://help.sbtinstruments.com/mpd/track-growth-curve.md).
{% endstep %}

{% step %}

### Run the new scale

Sample the new scale at the same process times. In fed-batch, note the culture volume at each sample too.
{% endstep %}

{% step %}

### Overlay the two runs

Plot the count and CIZE of both scales against time from feed start, or from induction.
{% endstep %}

{% step %}

### Find where they part

Look at what changed at that point, for example the feed, oxygen or mixing. Then adjust, so that the new scale reaches the same cell state, the size band where product per cell was highest, not the same OD or clock time.
{% endstep %}
{% endstepper %}

## The result

A measured target for scale-up. The cell state is matched at each stage of the run, not a proxy. The same steps work for a batch process.

{% 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/fed-batch/compare-cell-state-across-scales.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.
