Concepts · The why, in plain language

Concepts Explained

You don't need an acoustics degree to use MuirWave — but understanding these five ideas makes every readout obvious. Read it once and the numbers stop being mysterious. No maths required; the app does that.

§01

The one idea underneath everything

All of underwater acoustics is really a single question: a sound starts out at some loudness, weakens as it travels, and competes with background noise — can it still be heard? That balance is the sonar equation, and every panel in MuirWave is one term of it.

How loud it starts (source level)    how much it weakens (transmission loss)    the background noise  =  how detectable it is

MuirWave computes each term from the real ocean at your pin. The rest of this page explains the two that do the heavy lifting: transmission loss (how the sea bends and weakens sound) and the sound-speed profile (why it bends the way it does).

§02

The sound-speed profile — why sound bends

Sound doesn't travel in straight lines underwater. Its speed changes with depth — warmer, shallower water carries sound faster; cold deep water slower; then pressure speeds it up again very deep. Sound rays always bend towards slower water, so this profile shapes where sound goes.

Sound speed → (faster) Depth → (deeper) sound-channel axis (slowest) warm surface — fast deep — pressure speeds it up
The sound-speed profile (SSP). The speed of sound versus depth. The slowest layer — the sound-channel axis — acts like a lens: sound bends toward it and can travel enormous distances trapped inside it.

MuirWave builds this profile at your pin from ocean climatology (or live data, with MuirWave Live). It's the single most important input — change the profile and the whole prediction changes. The Water Column panel shows it for any spot.

§

Measured beats modelled

Models are the best guess available before you sail. Once you're on station with a bathythermograph or a live noise display, you have something better — and MuirWave treats it that way.

Enter a measured layer depth or measured noise points and they outrank every model tier — live feed included — for as long as you keep them switched on. The model keeps running underneath (live data keeps fetching, the comparison curves stay on the plots), so reverting never lands you on stale data, and the gap between model and measurement stays visible: that disagreement is field intelligence, not an error to hide.

The ◆ solid-brass chip
A brass outline on a chip means live data answered. A solid brass fill with a ◆ glyph means your own observation is driving the solver — deliberately unmistakable from the live look, because those are the two states you must never confuse.
Perishable in time and space
An observation carries its clock and its position. The chip's age token is green under 6 hours, amber to 24, then STALE — and it ambers on distance once you're ~30 nm from where you measured. Stale truth keeps driving (no pop-ups, ever); REVERT TO MODEL waits in the chip inspector.
Honest limits. A layer entry assumes a fully-mixed layer and applies along the whole bearing; a noise point says nothing about frequencies more than a decade away, so the warp fades back to the model there. MuirWave states both rather than pretending otherwise.
§03

Transmission loss, rays & convergence zones

Transmission loss (TL) is simply how much a sound has weakened by the time it reaches a given point — bigger TL means quieter. Because rays bend (§02), sound doesn't fade smoothly: it focuses in some places and thins out in others.

sea surface seabed source convergence zone — loud again shadow zone — little sound
Ray paths. Sound leaves the source in many directions; refraction curves the rays so they thin out in a shadow zone, then refocus range after range in a convergence zone (CZ) where a signal can suddenly be loud again. MuirWave's Ray Path plot draws exactly this for your scenario.
CZ
Convergence zone
A ring of range where refracted rays refocus — sound is unexpectedly strong. MuirWave marks the first CZ (CZ1) and its spacing. Glossary ›
BB
Bottom bounce
Sound that reflects off the seabed to reach farther. Its strength depends on the sediment type at your pin. Glossary ›
DE
Depth excess
Whether the water is deep enough below the sound channel for reliable convergence zones. See the colour bands.
§04

Detection & the sound field

Put the loudness, the loss and the noise together and you get how detectable a source is at each point. MuirWave can paint this across the map as a field — a bird's-eye view of where a source would and wouldn't be heard.

On the Ray Path plot you can switch what's drawn: RAYS shows the ray paths, FIELD shows the continuous detection/loss field, and BOTH overlays them. The structure of the field comes from transmission loss; its overall level comes from the source and receiver you set.

The map heat-field paints absolute detectability against a threshold, so brighter genuinely means "more detectable here" — it isn't normalised away from the real decibels.
The Ray Path plot in BOTH mode: the ray fan overlaid on the continuous detection signal-excess field, warm colours where a source is hard to detect and cool-green where it is detectable, with the 0 dB detection-edge line and a Detection Signal Excess colour key.
The sound field. The same scenario as Figure 2, now in BOTH mode: the ray fan sits over the continuous detection signal-excess field. Red is where the source falls below the detection threshold, green where it clears it; the dashed line is the 0 dB detection edge. Read the colour key at the bottom-left of the plot.
§05

Impact thresholds

For assessment work, the question flips: instead of "can I hear it?", it's "how far out could this sound affect an animal?" Regulators define thresholds — sound levels above which injury or a behavioural response is expected — that differ by species hearing group and by whether the sound is impulsive or continuous.

Where do the thresholds come from?

MuirWave uses the recognised criteria: NMFS 2024 or Southall et al. 2019 (selectable) for marine mammals (grouped by hearing sensitivity) and Popper et al. for fish and turtles. The exact values used appear in your methodology export.

What's an "impact range", then?

The distance from your source at which the received level drops below a given threshold. Inside that range the threshold is exceeded; outside it isn't. MuirWave computes one per threshold and hearing group — see the how-to.

Why does source type matter so much?

MuirWave distinguishes impulsive (pile driving, airguns), non-impulsive (vibratory piling, drilling) and continuous (turbines, shipping) sources — each is judged against a different threshold family, and accumulation over time is handled differently. Setting this correctly is essential for a defensible number.