> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomscale.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Finding Your Data

> How gateway recordings are grouped into growths, where to find them, and how timestamps line up

Each RHEED stream and each tool log becomes its own data item in Atomscale. Atomscale then groups the items from one growth onto a single **physical sample**, so the growth appears on the **Monitor** page with RHEED and tool state together.

## Link Integrations to the Growth Instrument

Atomscale needs to know which instrument each integration serves. Set this once per integration, before the growths you want grouped:

**1. Set the Growth Instrument**

On the desktop app's **Integrations** page, click None in the **Growth Instrument** column of
the RHEED camera and the Tool Log Streamer, and choose the same instrument for both. If
your instrument isn't listed, click + New growth instrument at the bottom of the picker, then
\+ Growth Instrument, and enter an **Instrument Label** and **Instrument Name**.
Choosing the linked instrument again clears the link.

You can also set it remotely, even while the gateway is offline: in the web app, click
Gateways in the icon rail on the far left, click the gateway (listed under its Windows computer name), and use the
same column in its **Integrations** table.

New data items take the integration's instrument when they're created. Changing the link later doesn't change existing items.

## How a Growth Comes Together

```text theme={null}
RHEED stream starts
  └─► new sample "MBE-1 · 2026-10-09 13:36"
                 ▲
Tool log that ───┘  (same Growth Instrument)
started with the run

Run ends ─► real growth?
             ├─ yes ─► name completed, growth note
             └─ no ──► items taken off the sample
```

* **RHEED.** When a stream starts, Atomscale puts it on a new physical sample named after the instrument and start time, so it appears on **Monitor** right away. Without a Growth Instrument link, the integration's or gateway's name is used instead. Streams from the same instrument within 10 minutes of each other, such as one growth split by a camera restart, join the same sample.
* **Tool logs.** A tool log joins a RHEED stream's sample when both integrations are on the same **Growth Instrument** and the tool log started at most 10 minutes before the stream. A tool log without a Growth Instrument link, or one that has no matching RHEED stream, stays without a sample. An EpiTrend hour joins any growth it overlaps.
* **When the run ends**, Atomscale checks that it was a real growth: at least 10 minutes long in total, and, when the tool log records source shutters, at least one source shutter opened. A run that passes gets its sample's name completed from the run and a growth note. A run that doesn't, such as a quick camera check, is taken off its sample. Such short recordings are deleted after 14 days unless you give them a sample, tag, or note.
* **Your choices win.** If you set or remove a data item's physical sample yourself, Atomscale doesn't change it.

If the tool log records recipe and step names (see [Recipe Columns](https://docs.atomscale.ai/gateway/tool-state/parsing-schema.md#recipe-columns)), the growth's process steps are named after the running recipe.

## Where to Look

| Place | What you find |
| - | - |
| **Monitor** (web app) | Growths in progress and recent growths, with their RHEED and tool state. |
| **Data** (**Data Catalog** in Data Ingestion mode) | Every data item. |
| A data item's page | Its status, live chart or frames, and its **Physical Sample**, which you can change. |

To add an item that stayed without a sample, such as a tool log from before the integration was linked, open it and set its **Physical Sample** to the growth's sample.

## Timestamps and Clocks

RHEED frames and tool log rows must share one timeline to line up. The gateway handles most of this itself:

* **The gateway measures its clock** against Atomscale's when it starts, every 5 minutes, and whenever the computer's clock changes. It never changes the computer's clock.
* **RHEED timestamps** are always corrected by that measurement.
* **Tool logs on the gateway's own disk** are corrected the same way, once per data item when it starts.
* **Tool logs read from a network share** keep the clock of the computer that wrote them, which the gateway can't measure. Keep that computer synchronized to a time server.
* **Timestamps without a UTC offset** are read in the gateway computer's time zone.
* If the gateway can't measure its clock, for example when it starts offline, data uploads uncorrected and the activity log says so.

> [!TIP]
>
> The simplest setup is a gateway running on the tool's control computer, reading logs from its own
> disk. When the tool computer and the gateway are different computers, synchronize both to the same
> time server.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.