> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/aerial/aodt/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/aerial/aodt/_mcp/server.

# Telemetry

After connecting to a database and loading results, the viewer displays
ray-traced signal paths as 3D polylines between RUs and UEs.

![Rays tab showing signal strength controls and raypath visualization](https://files.buildwithfern.com/aerial.docs.buildwithfern.com/aerial/aodt/7ba5f19cfac28c747e43698b832b1a7623684f8274195cdf584fad7e814e6e91/docs/assets/ui/viewer-rays-signal-controls.png)

## Interpreting Raypaths

Each raypath follows the path geometry recorded by the EM solver — direct,
reflected, diffracted, or scattered segments. Color indicates received power
in dBm, ranging from dark purple (weaker) to yellow (stronger).

The viewer loads raypaths for antenna element pair (0, 0) only. Other antenna
element combinations are not visualized.

## Using Dynamic Range

The **Max dynamic range** slider is the primary tool for interpreting signal
coverage. Start with a narrow range (20 to 40 dB) to isolate the strongest
paths, then widen it to reveal weaker signals. This helps identify dominant
propagation paths and coverage gaps.

RU and UE filter selections are persisted per database namespace, so switching
between namespaces restores your previous filter state.

## Time-Indexed Data

Each time record in the database includes a global `time_idx`, `batch_idx`,
`slot_idx`, and `symbol_idx`. UE and scatterer positions update at each time
step, and raypaths are filtered to the current index. Use the timeline to step
through the simulation and observe how signal paths change as entities move.

Select a UE or scatterer in the **Entities** tab to see its recorded positions
as a paginated table with time index, longitude, latitude, and altitude.

## Scope

The viewer visualizes ray geometry, received power, entity positions, and 3D
building geometry. For tabular result inspection (CIR values, CFR data,
exported Parquet fields), see [Results and Data](/results-and-data).

## Related Pages

* See [UI](/ui) for the full viewer layout and workflows.
* See [Results Schemas](/results-schemas) for the Parquet tables produced by
  simulation runs.
* See [Interactive Mode](/dynamic-mode) for retrieving CIR results into NumPy
  during a run.