> 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/encyclopedia/track-growth-curve/1-100-dilution-post-inoculation.md).

# 1:100 dilution after inoculation

Once the shake flask is inoculated, immediately collect a sample to obtain a measurement as close to T<sub>0</sub> as possible.

{% stepper %}
{% step %}
**Prepare the sample for BactoBox® measurement**

1. Use a serological pipette to transfer a sample from the shake flask to a vial.
2. Use a permanent marker to label the vial cap with the sampling time.
3. Return the shake flask to the incubator shaker.
4. Start a 30-minute countdown to remind you to collect the next sample.
5. Vortex 30 seconds at max speed to disaggregate[^1] bacteria.
6. Dilute 1:100 in diluent by adding 101 µL of sample to 10 mL of diluent. Vortex 10 sec., max speed.
7. Transfer the tubing kit to the diluted sample.

{% hint style="success" %}

#### Put the flask back in the incubator shaker immediately after collecting the sample.

Collect the sample quickly to ensure prompt return. Minimize the time the flask is outside the incubator shaker to avoid drops in temperature and dissolved oxygen levels.
{% endhint %}

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2F8piuuzvCkxywD2Dg1Ipe%2FT0_prepare.avif?alt=media&#x26;token=037eee1a-7813-4b9a-91f9-ebbab8c0baf5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Measure the diluted sample on BactoBox®**

1. Add metadata:
   1. Dilution: <kbd>100</kbd>.
   2. Label: <kbd>E\_coli\_growth</kbd>.
2. Click the <kbd><mark style="background-color:purple;">Measure<mark style="background-color:purple;"></kbd> button in Access.
3. Once measurement is done, click the label <kbd>E\_coli\_growth</kbd> above the chart to visualize the growth curve data.

<figure><img src="https://142487182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FseAjVXi9YrPNSfdp1OXS%2Fuploads%2Fgit-blob-e6c8af5c79469eda7fb9e623276375cdbdfbd130%2FT0_measure.avif?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}

## Do you get the error *conductivity too high*?

Some cultivation media have very high conductivity and a 1:100 dilution in standard diluent is not sufficient to bring the diluted sample within the accepted conductivity limits.

You can typically solve this issue by using a 1:201 dilution: Simply add 50 µL of sample to 10 mL of diluent. For more information, please see the section [Hit the right conductivity](/advanced/advanced-sample-preparation/hit-the-right-conductivity.md).
{% endhint %}
{% endstep %}

{% step %}
**Clean the device**

1. Transfer the tubing kit to the disinfection vial.
2. Click <kbd>Clean</kbd>.
   {% endstep %}
   {% endstepper %}

## Summary

You now know the bacterial concentration at T<sub>0</sub>. Next we will collect a sample for every 30 min and keep repeating the 1:100 dilution scheme for lag and early exponential growth stage.

[^1]: Break up clumps or chains of cells


---

# 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/encyclopedia/track-growth-curve/1-100-dilution-post-inoculation.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.
