Tsunami buoy A3Monitoring & AlertsTEWS-A3
Tsunami buoy A3 · suction anchor · TEWS-A3Project section · Monitoring & Alerts

Monitoring & Alerts

Normal 1 open incident · 3 monitors live · data fresh 04:52:10 IST

Live signals

live · Satellite telemetry · shore gateway (read-only)
Bands from design basis v1 and the Tsunami watch rule · select a signal to see where it comes from

Incident 3 · Mw 7.1 Andaman · tsunami detected

opened 04:12:21 · acknowledged · control plan waiting for approval
  1. Tsunami watch v1monitor · L2 for event mode onlyopened 04:12:21 · tsunami raised 04:32:10
    AdvisoryAlert record · Incident 3

    Tsunami at A3: BPR-3 de-tided pressure 4.6 cm at 04:31:40, above the 3 cm detection threshold

    Rule
    tsunami-watch/detect revision 3 · de-tided pressure > 3 cm for 3 samples at 15 s
    Evidence window
    04:31:25–04:31:55 · 3 samples at 15 s · peak 4.6 cm at 04:31:40
    Source
    Mw 7.1 Andaman Sea · 04:12:08 · 212 km from A3 · depth 28 km
    Warning message
    National warning-centre feed · 04:33:10 · 90 s after arrival
    Band source
    Tsunami watch rule revision 3 · advisory 3 cm (detection) · alarm 10 cm
    Linked
  2. EElidyneproposal04:14:30
    L1execute with approval · spawns an investigation from this incident

    Forecast the tsunami at A3 and check the anchor after the shaking

    Start Investigation 2 “Mw 7.1 Andaman · A3 response” · plan v1 · 0.9 CU · runs on meridian-hpc
    1. Run 7: source inversion of the Mw 7.1 rupture, long-wave propagation to A3: arrival time and amplitude
    2. Run 8: anchor + mooring twin v2 re-run with the recorded seabed motion: post-event capacity and factor of safety
    3. Compare both with the measured pressure, tension and tilt
    Readstwin v2 · 5 streams · regional seismic catalogue
    Writesa twin revision, not adopted
    Estimate0.8–0.9 CU · reserved at p90
    Approved by you · 04:15 · 0.9 CU reserved
  3. Runs 7–8 · Investigation 2Run 7 finished 04:21 · Run 8 finished 04:360.9 CU of 0.9 reserved · meridian-hpc

    Run 7 forecast at A3, observed · Run 8: post-event capacity , factor of safety

    Run 8 fits the tilt and the tension peak with clay about 6 % weaker near the caisson tip (su −6 %). That clay update is recorded, not adopted: monitoring keeps twin v2 until gate G3 accepts it.
  4. EElidyneexplanation · answered from records04:38grounded in 5 records

    Did the anchor hold through the shaking?

    At 04:13:40, 79 s after the seabed trigger, the anchor + mooring twin v2 forecast a top-tension peak of from the seabed motion recorded so far. The load cell read at 04:14:02: a residual of , inside the twin's 95 % band. Caisson tilt went from to , half the 1.0° advisory band, and has not moved since 04:15.

    Run 8 re-ran the twin with the full recorded seabed motion. Post-event capacity is against the design value: a factor of safety of against the 185 kN cyclone demand, where the owner's criterion is 2.0. The fit asks for clay about 6 % weaker near the tip, which is what shaking at 212 km should do to soft pelagic clay of sensitivity 3.

    The anchor held, inside the twin's bandThe clay update (su −6 % near the tip) waits for gate G3 with A. Rao.
    Observed top tensionTwin v2 · forecast 04:13:40 · 95 % bandRun 8 · recorded seabed motion · 95 % bandAdvisory 150 kN
    Figure 1. Mooring top tension, 04:10–04:20, against the twin v2 forecast and its 95 % band. Shaded column: shaking at A3, 04:12:21–04:13:50. The dashed band is Run 8, the twin re-run with the recorded seabed motion, added at 04:36. The 100-year cyclone design peak is 185 kN.
    Hover the figure, or focus it and use the arrow keys, to read one sample.
    Checked and set aside
    • Load-cell fault: the redundant cell LC-2 read 94 kN at 04:14:02, within 2 % of LC-1.
    • Buoy excursion: GNSS offset 38 m at 04:14, inside the 120 m watch circle; the line did not go slack.
    • Tilt sensor: both inclinometer axes agree within 0.05°, steady at 0.5° since 04:15.
    • Not ruled out: further softening near the tip from aftershocks. The largest so far is Mw 5.4 at 04:47, 0.04 g at the seabed; Anchor integrity watch stays on the tilt and tension bands.
    Updated 04:36 by Run 8 of Investigation 2: post-event capacity 596 kN, factor of safety 3.2. The clay update stays proposed until gate G3.
    1 Telemetry window 04:10–04:20 · 2 Twin v2 forecast, 04:13:40 · 3 Tilt and seabed accelerometer, 04:12–04:16 · 4 Design basis v1, G4 14 Jan 2027 · 5 Run 8, Investigation 2 · 6 Run 7, Investigation 2 · 7 BPR-3 window 04:31–04:33
  5. EElidynelive control plan · Workbench04:40
    Proposal · nothing has runplan v1 · checked · 0 holes

    Return to normal mode

    Steps
      One press approves the whole plan. Nothing runs until you execute it.
    • EElidynemonitor review04:46
      Shadow · never acts

      Tsunami watch v2 (proposed, running in shadow since 06:00 on 15 Sep · never acts)

      Compared with v1, live, on the same 5 streams over the last 24 h (04:52 on 21 Sep to 04:52 today).

      Last 24 hv1 livev2 shadow
      Alerts raised52
      Later cleared as noise30
      Valid alerts missed00
      Tsunami arrival raised04:32:1004:31:55 · 15 s earlier
      valid alertcleared as noise
      ›What changed in v2 · 3 rule changes
      • Detection: 2 samples above 3 cm with a rise of more than 1 cm per 15 s, instead of 3 samples above 3 cm. Today's arrival would have been raised 15 s sooner.
      • Seabed trigger: two axes above 0.15 g, or one axis for 3 consecutive samples. Single-axis spikes stay quiet.
      • De-tiding: tide model refitted on 180 days of BPR-3 records, so spring-tide residuals stay under 3 cm.
      ›All 5 alerts, side by side
      WhenWhatv1v2Outcome
      Promotion needs your approval · the L2 grant carries over unchanged
    Run an analysis on live data
    Incident 3 · TEWS-A3 · since 04:12
    Instant answers from records · Workbench plans a Run for approval