🚀 New: 100-Day Hydrographic Mastery Course is LIVE! Enroll Now →
▲
☏

📡 Day 62: Low-Frequency Sonar and Deep Sea Ray Tracing

Day 62: Deep‑Sea Ray‑Tracing & Sonar – Masterpiece Edition | River Warrior

📡 DAY 62: DEEP‑SEA RAY‑TRACING & SONAR

⏱️ Estimated Reading Time: 15 Minutes | 🎓 Level: Professional Hydrographer / Acoustic Specialist

Bending Light (Sound) in the Abyss – Correcting Refraction for Deep‑Water Bathymetry

Instructor: Engr. Rokib Hossain | River Warrior Academy


🏠 Course Homepage

1. Why Ray‑Tracing Is Critical in Deep Water

In shallow water (<50 m), ignoring refraction may cause errors of a few centimetres. In deep water (>500 m), ignoring refraction can misplace the outer beams by tens of metres and create artificial slopes (“smile” or “frown”) that invalidate the survey. Ray‑tracing (or ray‑bending) is the process of calculating the true path of each acoustic ray through a water column with variable sound velocity.

Consequences of neglecting ray‑tracing:

  • ❌ Horizontal position errors of outer beams > 10 m at 2000 m depth.
  • ❌ Depth errors exceeding IHO tolerance (e.g., 5 m at 1000 m).
  • ❌ False slopes and artificial seafloor features.
  • ❌ Cross‑line mismatch > 5% of depth.
🧠 Golden Rule: In water deeper than 200 m, always use a full‑water‑column SVP (or CTD) and apply ray‑tracing in post‑processing. Real‑time corrections are often insufficient.

🌊 River Warrior Pro-Tip: Bay of Bengal Lesson

During a 2,000 m deep cable route survey, we initially used a surface‑to‑bottom SVP but applied a simplified constant‑gradient ray‑trace. The outer beams still showed a 5 m error. Switching to a “layer‑cake” algorithm (10 m layers) reduced the error to <0.5 m.

2. Physics of Ray‑Bending (Snell’s Law) in Deep Ocean

Snell’s Law describes how an acoustic ray bends when crossing a boundary between two layers of different sound velocity:

sin θ₁ / c₁ = sin θ₂ / c₂ = constant (p)

where p is the ray parameter. For a continuous velocity profile, the ray path is curved. The total horizontal displacement (DX) is integrated along the ray.

Ray‑Bending in Deep Water Transducer Ray‑bent (real) Straight ray (wrong) Seabed (bent ray corrects depth & position)

3. Deep‑Water SVP Strategy (CTD, Full Profile, Interpolation)

  • Use a CTD (Conductivity, Temperature, Depth) – measures T,S,P to calculate sound velocity. Preferred over SVP probe because salinity varies in deep ocean.
  • Full profile to seabed: Cast CTD to at least 10% below maximum survey depth. For 2,000 m depth, cast to 2,200 m.
  • Frequency: Every 12‑24 hours in stable oceanic conditions; every 4‑6 hours in dynamic regions (fronts, upwelling).
  • Interpolation: If SVP spacing is coarse, linearly interpolate between measured points. For ray‑tracing, use 1‑5 m depth increments.
🔬 In deep water, salinity changes below the thermocline are small but not negligible. CTD captures both temperature and salinity.

4. Ray‑Tracing Algorithms (Layer Cake, Constant Gradient)

.htmlLayer‑cake (refraction)那样Each layer has constant velocity; Snell applied at boundaries.那样High, even with sharp thermoclines.那样Medium
AlgorithmDescriptionAccuracySpeed
Constant gradient那样Assume linear velocity between measured layers.那样Good for smooth profiles (deep ocean).那样Fast
Full ray‑tracing (integration)那样Solve ray equations numerically (Runge‑Kutta).那样Highest, uses continuous profile.那样Slow

Most commercial software (Qimera, CARIS) uses layer‑cake or constant gradient. For extreme accuracy (e.g., scientific surveys), use full integration.

📊 Ray‑Bending Error Simulator (Deep Water)

Estimate the horizontal position error of an outer beam (30° from nadir) due to incorrect SVP:

Water depth (m): Surface sound velocity (m/s): Bottom sound velocity (m/s): Beam angle from nadir (degrees):

Horizontal error ≈ 14.2 m (without ray‑tracing)

Assumes linear velocity gradient from surface to bottom. Real profiles are more complex.

5. Sonar Optimisation for Long Range (Low Frequency, Pulse Length, Power)

To achieve deep penetration, MBES parameters must be adjusted:

  • Low frequency (12‑30 kHz): Less attenuation, longer range. But lower resolution (footprint larger).
  • Long pulse length (FM chirp): Increases energy, improves SNR. Trade‑off: range resolution degrades.
  • High power: Use maximum transmit power (within transducer limits).
  • Ping rate: Lower in deep water (e.g., 0.5‑1 Hz) to allow time for returns from seabed.
  • Swath angle: Reduce to 90‑110° for deep water; outer beams are heavily attenuated.
🌊 For depths > 3000 m, consider using a deep‑tow MBES (lowered near seabed) to reduce spreading loss.

6. Field Workflow for Deep‑Water Refraction Correction

1️⃣ Before survey: download world ocean database SVP as backup.
2️⃣ Deploy CTD to full depth; record profile.
3️⃣ Load SVP into acquisition software for real‑time correction (if available).
4️⃣ After survey, re‑process with high‑resolution ray‑tracing.
5️⃣ Compare with cross‑lines to validate correction.

7. Case Study: Bay of Bengal Deep‑Sea Ray‑Tracing (2026)

Project: 3,000 m deep ocean survey for a telecommunications cable route.

  • Challenge: Strong thermocline at 300‑600 m (temperature drop from 25°C to 8°C) caused severe ray‑bending.
  • Solution: CTD casts every 12 hours; processed with layer‑cake ray‑tracing (10 m layers) in Qimera.
  • Comparison: Without ray‑tracing, outer beams showed a 25 m horizontal shift. After correction, the seabed topography became consistent with sub‑bottom profiles.
  • Result: Survey passed IHO Order 1b with flying colours; cable route safe.
📈 The time spent on CTD casts (2 hours per day) was negligible compared to the cost of re‑surveying a misplaced cable route.

8. Deep‑Sea Ray‑Tracing Checklist

  • CTD or SVP cast to at least 10% below max depth.
  • Profile includes temperature, salinity, pressure (CTD).
  • Ray‑tracing algorithm selected in processing software (layer‑cake or constant gradient).
  • Vertical resolution of SVP ≤ 10 m for depths < 500 m, ≤ 20 m for deeper.
  • Real‑time correction applied (if software supports).
  • Post‑processing re‑run with full ray‑tracing.
  • Cross‑line analysis performed – difference < 0.5% of depth.
  • Outer beam “smile” or “frown” checked and corrected.
  • Documentation: SVP file name, cast time, algorithm used.
  • If using constant gradient, verify linearity of profile.

Click items to track progress (saved in browser).

9. Resources & Software

.htmlCARIS HIPS (SVP Manager)那样Refraction correction, CUBE with ray‑tracing那样teledynecaris.com.htmlNOAA World Ocean Atlas (WOA)那样Climatological SVP for planning那样ncei.noaa.gov.htmlSeaBird CTD那样High‑accuracy CTD for deep water那样seabird.com
ToolPurposeLink
QPS Qimera (Ray‑tracing module)那样Layer‑cake, constant gradient, full integration那样qps.nl/qimera

10. Frequently Asked Questions

Can I use a surface sound velocity (SVS) alone for deep water?
No – SVS only gives surface value; it cannot correct refraction from deep thermoclines. You need a full profile.
What is the difference between ray‑tracing and sound velocity correction?
Sound velocity correction adjusts depth using a single average velocity. Ray‑tracing calculates the actual curved path, correcting both depth and horizontal position.
How often should I cast a CTD in the deep ocean?
Every 12‑24 hours in stable water masses. If crossing fronts or eddies, cast more frequently (every 4‑6 hours).
My processing software has no ray‑tracing; can I manually correct?
Not practically. Upgrade to a professional package (Qimera, CARIS, Hypack) that includes ray‑tracing.
What is the maximum depth where ray‑tracing is still negligible?
For IHO Order 1a, ray‑tracing becomes mandatory below ~200 m. For Order 2, below ~500 m.

11. Action Items & Next Steps

  • 📌 Download a sample CTD profile from NOAA and load it into your processing software.
  • 📌 Use the ray‑bending simulator with different depths and beam angles.
  • 📌 Research the sound velocity profile in your local offshore area (e.g., Bay of Bengal).
  • 📌 Proceed to Day 63: PPP & Marine Geodesy.
© River Warrior – Day 62 of 100‑Day Hydrographic Mastery | Masterpiece Edition | Home

Comments