---
title: "Reading a logged dive"
description: "Every reading on a downloaded dive, what the computer meant by it, and how a dive comes to be associated with the plan you dived it against."
---

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

# Reading a logged dive

import { DiveRecord } from "@/components/react/LogScreens";

A downloaded dive opens on two tabs: **Graph**, the recorded profile with the
headline numbers underneath, and **Configuration**, the settings the dive was
flown with. The header carries the dive number, the computer's date and time
stamp, the mode, and up to three metrics: **Duration**, **Max depth** and **Avg
depth**.

Depths are shown in the unit the computer was set to, metres or feet, because
that is what it recorded; DiveLogic does not convert them. Rates use the same
unit per minute.

## Graph

The section header reads **Dive Profile** with how many readings the dive holds
and how often they were taken, for example `1042 samples @ 10s`. That spacing
sets how finely every number below can resolve the dive. Beneath the profile, an
instrument strip carries whichever of these the dive holds:

- **Max depth**: deepest point of the dive.
- **Avg depth**: mean depth, worked out from the recording.
- **Duration**: total dive time.
- **O₂ CNS**: the oxygen clock at the end of the dive, as a percentage. It
  changes tone at 80 % and again at 100 %.
- **GF**: the gradient factor pair the computer was set to, low/high.

## Configuration

**Dive Summary** repeats depth, duration and CNS, and adds **Max Ascent**, **Avg
Ascent**, **Max Descent** and **Avg Descent**. Where a computer left the rates at
zero, DiveLogic works them out from the recording. No rate can beat the reading
spacing behind it: a ten-second log cannot resolve a two-second surge.

**Computer Settings** were recorded at the start of the dive:

- **Serial**: the computer's serial number.
- **Firmware**: firmware version at the time of the dive.
- **Mode**: `CC/BO`, `OC Tec`, `Gauge`, `OC Rec`, `Freedive` and so on. A `Gauge`
  dive carries no decompression information, because the computer was not
  calculating any.
- **GF**: the gradient factors the computer was decompressing on, low/high.
- **Surface Pressure**: in mbar, which is how the computer knew its altitude.
- **Battery**: battery voltage at the start of the dive.

**Gas Mixes** lists up to five slots, `Gas 1` to `Gas 5`, each with the oxygen
percentage and, where present, the helium percentage. Empty slots are hidden.
These are the mixes the computer was configured with, not the mixes breathed;
what was breathed is in the recording.

## Associating a dive with a plan

There is no attach control in the dive view. The association is made in the
post-dive review, which matches each of your plans against your downloaded dives
on maximum depth, runtime and the calendar day, then keeps the matched plan and
dive together as one record.

## Next

[Starting a review](/post-dive/starting-a-review) covers the matching rules.

[Oxygen exposure](/theory/oxygen-exposure) describes the CNS clock.

Source: https://docs.divelogic.ai/log/reading-a-dive/index.mdx