Reading Pressure Gradients Before They Cascade
- Published
- Reading time
- 2 min
- Author
- Mateo Ferreira
Why the Bathys engine treats hydrostatic loading as a topology problem, and how cascaded pressure-hull thresholds turn a slow drift into an early warning.
A pressure sensor on a single mooring tells you one thing: the hydrostatic load at that point, right now. A pressure sensor on fourteen moorings, read as a graph, tells you something far more useful: where the load is going.
Pressure as topology
Every Bathys mooring reports pressure at 4 Hz. The engine does not evaluate those readings in isolation. It builds a topology of the array (which moorings are up-slope of which, which share a sediment fan, which sit on the same acoustic relay path) and evaluates gradients along that topology.
A 0.3 dbar rise at one mooring is noise. The same rise propagating down-slope across three moorings in twelve minutes is a sediment slope beginning to load. That is the signal the pressure-mapping module exists to surface.
Cascaded thresholds
Each mooring carries three pressure-hull thresholds:
- Nominal: the rated operating envelope of the hull.
- Watch: 85 % of rated, where the engine begins logging at 20 Hz and opens an event in the anomaly console.
- Release: the point at which the autonomous ballast release policy is allowed to act without an operator.
The word cascaded matters. Thresholds are not evaluated per mooring; a Watch condition on an up-slope mooring lowers the Watch threshold on every mooring below it by a configurable margin. A slope that is loading gets more sensitive as the load travels.
The 85 % question
Operators ask why Watch sits at 85 % rather than 90 %. The answer is latency. From the moment a gradient crosses Watch to the moment an operator sees it on the console is roughly 12 ms of acoustic link plus whatever the operator is doing. From Watch to Release on a fast slope failure can be under four minutes. Five percent of headroom is the difference between deciding and reacting.
What we measured in the Mariana array
Across the first three weeks of the Mariana deployment the engine opened seven Watch events. Two escalated to Release conditions; both moorings were held by operator override after the console showed the gradient flattening. Five closed on their own. None reached the rated hull limit.
That is the behaviour we want: the system gets loud early, and the human stays in the loop.
