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

# Run a fluid analysis

> Define a fluid domain and operating conditions, then evaluate flow and pressure results.

Ask Adam to prepare or inspect a CFD case for a specific engineering question. State whether you care about pressure drop, flow distribution, aerodynamic force, cooling, or another output.

## Define the operating point

Provide the geometry revision and length units, fluid properties and their source, flow rate or other driving conditions, pressure reference, and output locations. Specify heat sources and thermal boundaries when temperature matters.

The model must distinguish internal or external flow, laminar or turbulent behavior, steady or transient behavior, and any compressibility or multiple regions required by the case.

```text title="Set up an internal-flow comparison" wrap theme={null}
Compare pressure drop through the attached duct revisions A and B at the same specified volumetric flow rate of [value and units]. Use [fluid] at [temperature] with sourced properties. Identify inlet and outlet measurement planes, construct the fluid region, and justify the flow model from the operating conditions. Check the available solver, propose a mesh and convergence plan, and keep the physical conditions fixed between revisions.
```

## Check the case before running

Confirm the mesh occupies fluid space and that inlet, outlet, wall, and interface regions survived export. Inspect pressure and velocity conventions, backflow settings, wall treatment, and thermal conditions where relevant.

```text title="Inspect boundary assignments" wrap theme={null}
Inspect this CFD case before running. List every mesh boundary and its velocity, pressure, turbulence, and thermal conditions where applicable. Confirm the fluid region, length scale, pressure convention, and total inlet flow. Identify missing or conflicting conditions and explain the expected direction of flow.
```

## Monitor the engineering quantity

Track the requested pressure drop, force, or temperature during the run, alongside solver diagnostics. Check mass balance and, for thermal cases, the relevant energy balance. Evaluate sensitivity to mesh, domain size, and time step as appropriate.

A residual threshold alone does not establish a stable engineering result. For transient flow, define the averaging interval and explain how startup behavior is handled.

## Deliver useful results

Request the native case, mesh and settings, logs, raw fields, and a table of measured quantities. Plots should identify units, pressure convention, time or averaging interval, and any derived conversions.

```text title="Explain a completed CFD result" wrap theme={null}
Read the existing case and results without rerunning them. Report the achieved time, solver completion, mass balance, and pressure drop between the agreed planes. Show the averaging method and pressure units. Flag incomplete convergence or missing evidence, and provide labeled plots using comparable ranges for both revisions.
```

For thermal or coupled studies, confirm the required energy model and field transfer explicitly. A flow solution alone does not establish solid temperatures or structural response.

Continue with [Meshing](https://docs.adam.new/cae/meshing.md), [Results and comparison](https://docs.adam.new/cae/results.md), or [Troubleshooting](https://docs.adam.new/cae/troubleshooting.md).


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