Day 48: Patch Test Calibration – Masterpiece Edition | River Warrior

📏 DAY 48: PATCH TEST CALIBRATION

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

Fine‑tuning Multibeam Alignment – Roll, Pitch, Yaw, Latency

Instructor: Engr. Rokib Hossain | River Warrior Academy

🏠 Course Homepage

1. Why Patch Test Is Critical

The patch test is the final calibration step for a multibeam echosounder after physical installation. It determines residual angular misalignments (roll, pitch, yaw) and time delay (latency) that cannot be removed by mechanical alignment alone. Without a patch test, systematic errors will corrupt your data – causing cross‑line mismatch, depth errors, and horizontal shifts.

Typical magnitudes: roll offset < ±0.5°, pitch < ±0.3°, yaw < ±0.5°, latency < 20 ms.

🧠 Golden Rule: Perform a patch test at the beginning of every project and after any sensor reinstallation. Do not skip it – even if you think the alignment is perfect.

🌊 River Warrior Pro-Tip: Jamuna Bridge Patch Test

Before the Jamuna bridge pier survey, we ran a patch test and discovered a 0.4° roll offset. After correction, cross‑line differences dropped from 0.25 m to 0.08 m – turning a failing survey into IHO Order 1a compliant.

2. Parameters: Roll, Pitch, Yaw, Latency

.htmlPitch那样Depth difference when sailing opposite directions那样Two opposite lines over a slope.htmlYaw (heading)那样Lateral shift of outer beams (mustache)那样Two opposite lines over a small isolated target.htmlLatency那样Along‑track shift proportional to speed那样Two lines over target at different speeds

Parameter	Effect	Detection method
Roll那样Asymmetric swath (port deeper, starboard shallower)那样Single line over a slope, compare left/right depths

3. Data Collection: Choosing a Test Site

Depth: At least 10‑15 m (deeper gives more sensitivity). Avoid very shallow (<5 m) where near‑field effects dominate.
Seabed: A sloping area (2‑5° slope) for roll/pitch; a small isolated target (rock, concrete block, wreck) for yaw/latency.
Conditions: Calm weather, low currents, good GNSS coverage.
Repeatability: The target must be visible in all passes.

📌 If no natural target exists, you can deploy a temporary target (e.g., a weighted metal cone or concrete block).

4. Line Patterns for Each Parameter

Roll: One line perpendicular to the slope, constant speed (4‑6 knots). Length ≥ 500 m.
Pitch: Two lines in opposite directions over the same slope, same speed. Start second line at the end point of the first (reciprocal).
Yaw: Two opposite lines passing directly over the isolated target, same speed. Ensure the target is at mid‑line.
Latency: Two lines over the same target, same direction, at two different speeds (e.g., 4 knots and 8 knots).

🧮 Patch Test Simulator (Effect of misalignment)

Simulate the effect of roll, pitch, yaw, or latency on depth/position:

Parameter: Value:

Simulated error: ~0.07 m depth difference (roll)

Based on depth = 15 m, speed = 5 knots (for latency).

5. Processing & Computing Corrections

Most processing software (Qimera, Hypack, CARIS) includes a patch test module. Steps:

Load the roll line. The software plots port vs starboard depths. Adjust roll until the slope becomes consistent.
Load the two pitch lines. Align the two profiles by adjusting pitch angle.
Load the two yaw lines. Compute lateral shift of the target; convert to yaw angle.
Load the two latency lines (different speeds). Compute along‑track shift; convert to latency.
Iterate – sometimes pitch and yaw interactions require a second pass.

💡 In Qimera, use the “Patch Test” tool under ‘Tools’. It guides you step by step.

6. Applying Corrections in Software

After the patch test, enter the computed offsets into your MBES configuration file or acquisition software. Typical fields:

Roll offset: Positive = starboard side down relative to vessel.
Pitch offset: Positive = transducer facing forward relative to level.
Yaw offset: Positive = transducer pointing to starboard relative to vessel’s centreline.
Latency: Positive = ping delayed after GNSS timestamp.

⚠️ Always double‑check sign conventions with your software manual. A wrong sign will double the error.

7. Verification with Cross‑Lines

After applying corrections, re‑run a short cross‑line (perpendicular to main lines) over a flat area. Compute differences as in Day 47. The mean difference should be < 0.1 m and standard deviation < 0.15 m for Order 1a. If still high, re‑evaluate patch test values.

8. Case Study: Jamuna River Patch Test (2025)

System: Kongsberg EM 2040, 400 kHz, mounted on 12 m survey boat.

Test site: Sloping area (depth 12‑20 m) and a concrete block (known location).
Initial mechanical alignment: inclinometer used, but residual errors remained.
Patch test results:
- Roll offset: +0.27°
- Pitch offset: –0.12°
- Yaw offset: +0.18°
- Latency: 18 ms
After correction: Cross‑line standard deviation dropped from 0.28 m to 0.11 m – meeting IHO Order 1a.

🌊 The patch test took 2 hours of data collection and 1 hour of processing – time well spent to guarantee data quality.

9. Patch Test Checklist

Test site identified (slope + isolated target).
Weather conditions calm (waves <0.3 m).
Roll line collected (perpendicular to slope).
Pitch lines collected (opposite directions over slope).
Yaw lines collected (opposite directions over target).
Latency lines collected (same direction, two speeds).
Lines processed in patch test software.
Corrections computed and applied to system config.
Verification cross‑line run and stats acceptable.
Patch test values documented in survey report.

Click items to track progress (saved in browser).

10. Resources & Software

.htmlTeledyne CARIS HIPS那样Patch test module, visual comparison那样teledynecaris.com.htmlHypack Patch Test Wizard那样Step‑by‑step, real‑time display那样hypack.com.htmlKongsberg SIS (installation)那样SIS patch test utility那样Kongsberg

Software / Resource	Patch Test Features	Link
QPS Qimera那样Patch Test tool, automated calculation那样qps.nl/qimera

11. Frequently Asked Questions

Do I need a patch test if I used a laser alignment tool during installation?

Yes, mechanical alignment can only achieve ~0.2° accuracy. Patch test refines to 0.05° or better.

How often should a patch test be repeated?

At every new survey area if depth conditions change significantly, or after any sensor removal/reinstallation.

Can I perform a patch test in shallow water (5 m)?

Possible but less accurate. Errors scale with depth – shallow water makes angular offsets harder to detect. Deeper (15‑30 m) is preferred.

What is the difference between latency and time delay?

Same concept – the time between GNSS timestamp and sonar ping. Typical range 0‑50 ms.

My software shows no patch test tool; can I do it manually?

Yes – export profiles to CSV and calculate manually using spreadsheet, but it's tedious. Better to use proper software.

12. Action Items & Next Steps

📌 Plan a patch test for your MBES: select a test site and design line patterns.
📌 Use the simulator to understand how different offsets affect depths.
📌 If you have access to MBES software, run a patch test on a demo dataset.
📌 Proceed to Day 49: Speed of Sound & Refraction.

🛠️ Day 48: Patch Test Calibration and Verification