---
title: "Tunang in the planner"
description: "What Tunang knows about the plan you have open, what a what-if returns, and how a suggestion gets into the plan."
---

> 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.

# Tunang in the planner

import { AssistantCard } from "@/components/react/ChatScreens";

**Ask AI** in the planner header opens Tunang beside the dive you are working
on. A question can be about this dive rather than a hypothetical, and it asks
for nothing it already has.

## What it already knows

- Every level, with its depth and bottom time.
- Every gas, with its role, switch depth and ppO₂ limit.
- The decompression settings: algorithm, GF pair, last stop depth, stop spacing,
  water type, altitude, and closed-circuit setpoints.
- The results: maximum depth, runtime, time to surface (TTS), first stop, CNS
  and OTU.
- The computed ascent, segment by segment, with the gas at each.
- Every warning the plan is carrying.

## Asking "what if"

*"What would GF 25/60 do to this dive?"*

The planner runs the dive again with that one thing altered, and returns a card
carrying a schedule rather than an estimate.

Runtime and TTS carry their change against the plan you started from, beside
maximum depth, first stop, CNS and every warning the dive holds. Tunang states
the trade-off in words.

Three things can vary:

- **Levels**: a replacement set of depths and bottom times.
- **GF Low** and **GF High**: whole percentages.
- **The three CCR setpoints**: descent, working and deco in bar, on a
  closed-circuit plan only.

Everything else, the algorithm included, is inherited unchanged.

**Apply to Plan** writes the variation in; the previous version is kept first,
so the change is reversible. A card for a whole dive carries **Open in
Planner**, which loads and saves that plan. Read the schedule and the warnings
against your own training and tables before using either: a card answers one
question, it does not judge the dive.

## What it will not do

- **It cannot change gases.** Asked about a different mix, it explains the
  consequence and asks you to change the setting yourself.
- **One variation per question.** A question containing three gets one computed,
  the rest discussed.
- **It does not authorise anything.** It is not a replacement for formal
  training, agency standards or dive judgement, and it must never say a dive is
  safe.
- **It must not ignore a warning.** It names the risk instead: the MOD of each
  gas against the depth it is breathed at, hypoxic gases at the surface, gas
  density at maximum depth, switch depths against MOD, CNS above 80 %, OTU above
  300, a GF High above 90 or a GF Low below 20, and, on closed circuit, a
  diluent ppO₂ limit above 1.1 bar.

## Next

[Reviewing a plan](/planning/reviewing) is where a variation's schedule is read;
[plan warnings](/planning/warnings) are what it has to address.

Source: https://docs.divelogic.ai/assistants/planner/index.mdx