> 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/seed-train/design-the-seed-train.md).

# Design the seed train

A consistent seed gives consistent growth. Study how the seed grows, then adjust it so each transfer falls at a convenient time.

Each seed step is a batch culture that feeds the next vessel. The seed sets how the step grows, how long the lag lasts and when the culture reaches the transfer point. Seed the same number of cells, in the same state, and the step grows the same way every time. That makes the seed train predictable.

## Choose a seed, study it, adjust it

Start from the current seed. Count it, and follow its growth through the step. The curve shows when the culture reaches the transfer point. If that falls at an awkward time, adjust the seed. A heavier seed reaches the transfer point sooner, a lighter one later. A seed taken while its cells still divide starts with a shorter lag.

## The state of the cells sets the lag

We seeded four flasks of *E. coli* from four starters, each at a different point on its growth curve.

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2F3OM5MV6jYihCvBA5kWhq%2Fs1-starter-lag-v3.svg?alt=media" alt="Cells/mL over five hours in four E. coli flasks, each seeded at about 1 × 10^6 cells/mL. Seeded from an early exponential starter, the count rose after 10 minutes. From an agar colony, after 34 minutes. From early and late stationary starters, after 83 and 100 minutes. Once growing, all four divided about every 20 minutes."><figcaption><p><em>E. coli</em> in LB at 37 °C, shake flasks. The lag is the time before the count started to rise.</p></figcaption></figure>

Cells from a dividing culture started dividing again within 10 minutes. Cells from a stationary culture took up to 100 minutes. Once growing, all four divided at the same rate. Take the seed from the same point on its curve every time, and the lag stays the same.

## What BactoBox® shows

The count shows how many cells are seeded, the lag, how fast each step divides and where division slows. CIZE adds a fingerprint of the cells at transfer. The same count and CIZE at transfer means cells in the same state from run to run. To dose the same number of cells into each step, see [Inoculum standardization](https://help.sbtinstruments.com/inoc/).

## Step by step

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2FGc4nfGKxNR4Oxvz4OgxY%2Fs1-steps-v3.svg?alt=media" alt="Four steps. 1, choose a seed and count it every time. 2, follow its growth through the step. 3, adjust the seed so the transfer point falls inside a convenient window. A heavier seed shifts the curve earlier. 4, keep the seed consistent. The same seed gives the same curve."><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Choose a seed and count it

Start from the current seed. Count it right after inoculation, and note the count and CIZE of the culture it came from.
{% endstep %}

{% step %}

### Follow its growth

Track the curve until division stops, sampling every hour or every two hours. Count the first hours of the next vessel too, to see its lag. See [Track a growth curve](https://help.sbtinstruments.com/mpd/track-growth-curve.md).
{% endstep %}

{% step %}

### Adjust the seed to fit the day

From the curve, find when the culture reaches the transfer point, while the growth rate is still close to its highest. Calculate the growth rate between samples from the count. Divide the natural log of the ratio of two counts by the hours between them. Where it starts to fall, growth is slowing, and the next step will start with a lag. If the transfer point falls at an awkward time, change the seed. Seed more cells to get there sooner, or fewer to get there later.
{% endstep %}

{% step %}

### Keep the seed consistent

Seed the same number of cells, from a culture in the same state, every time. Count each seed and compare it with the reference. A fed-batch that starts with fewer cells than the feed profile assumes is overfed in its first hours. Adjust the transfer volume, or the feed.
{% endstep %}
{% endstepper %}

## The result

A seed train that grows the same way every run, with transfers at chosen times. Measure again when the strain, medium or vessels change.

{% 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/seed-train/design-the-seed-train.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.
