6 Tsunami Simulations

Individual Contributions

Justus Dreßler: all members contributed equally

Thorsten Kröhl: all members contributed equally

Julius Halank: all members contributed equally

6.1 2010 M 8.8 Chile Event

6.1.1 Visualize the Input data

_images/6_Chile_Bath.png

Bathymetry of the Chilean coast.

_images/6_Chile_Displ.png

Displacement of the 2010 M8.8 Chile Event.

6.1.2 Simulate the tsunami event and visualize the output

Disclaimer: Due to performance issues / time constraints the simultion was only run for 1000m and 500m resolutions. The Data for 250m Resolution is just extrapolated from the 500m Resolution (2x each dimension, 8x updates).

The computational demands for the simulations are approximated by the following table:

Resolution

1000m (5h)

500m (5h)

250m (5h)

Height (Cells)

2950

5900

11800

Width (Cells)

3500

7000

14000

Timesteps

11393

22793

45572

Cellupdates

0.47 * 10^12

3.76 * 10^12

30.1 * 10^12

Cellupdates were calculated as \(Height \cdot Width \cdot Timesteps \cdot 4\). (4 for the 4 directions in each update)

The first wave leaves the computational domain after roughly 4 hours.

Simulation of the 2010 M8.8 Chile Event with 1000m Resolution for 10h.

Simulation of the 2010 M8.8 Chile Event with 500m Resolution for 1.5h.

Simulation of the 2010 M8.8 Chile Event with 500m Resolution for 1h. The height of the waves is scaled by a factor of 20000 and the bathymetry is scaled by a factor of 20.

We noticed our simulation breaking down near 1h when the wave hit the stones sticking out of the ocean (see image below). Our running theory is that the stones are to shallow in the water and the rarefaction wave following the shockwave reduces the waterheight to a very low value. This causes the FWave solver to break down (specifically the t_real l_uL = i_huL / i_hL; calculating the particle velocity). that would explain the sudden explosion in height around these areas after roughly 2h (the big wave centered on the stones). One could probably fix this by increasing the \(\delta\) value in the TsunamiEvent2d setup, we didn’t have time to test this.

_images/6_Chile_shallow_stones.png

The problematic region in our simulation (500m Resolution).

Another bug happened around 2h in the 1000m simulation, when the wave hit the coast in the south of Chile. We identified the location as the following piece of land:

_images/6_chile_bug2.png

Trapped cell in Chile (1000m Resolution).

We identified a bug in our FWave solver that sometimes caused inaccurate updates to the left / bottom cell so that might be the cause. Due to a lack of time (and loss of data on the reproducing simulation) we couldn’t verify if the faulty FWave solver was indeed the cause. But that bug should be the cause of the total corruption of the simulation past 4h.

6.2 2011 M 9.1 Tohoku Event

6.2.1 Simulate the tsunami event and visualize the output

The computational demands for the simulations are approximated by the following table:

Resolution

1000m (10h)

500m (5h)

250m (5h)

Height (Cells)

1500

3000

6000

Width (Cells)

2700

5400

10800

Timesteps

24566

24617

45572

Cellupdates

0.4 * 10^12

1.6 * 10^12

12.8 * 10^12

We see the simulation is significantly faster than the Chile Event due to the smaller size.

The first wave leaves the computational domain after roughly 10000 seconds (2.8 hours). (Tested in the 1000m 5h simulation)

Simulation of the 2011 M9.1 Tohoku Event with 1000m Resolution for 10h.

Simulation of the 2011 M9.1 Tohoku Event with 500m Resolution for 5h.

Similarly to the Chile Event we also see the simulation breaking down in very shallow water regions (the light red regions in the following image).

_images/6_tohoku_bath.png

Bathymetry of the Tohoku coast.

Deep red are all regions above 0m, light red are all regions between 0m and -15m and white are all regions deeper than -15m.

The simulation interestingly only breaks down in a very small region on the coast and the error doesn’t propagate (much) further (since the regions get treated as landmass after the breakdown).

_images/6_tohoku_2698.png

500m Simulation at t=2698s as the last timestep before the breakdown happens.

We see that the very shallow region currently has a deep negative waterheight (the deep blue) which we hypothize is the cause of the breakdown in the next frame.

_images/6_tohoku_2878.png

500m Simulation at t=2878s as the first timestep after the breakdown happens.

Interestingly it has very strict outlines and remains relatively contained as problem.

_images/6_tohoku_17990.png

500m Simulation at t=17990s as the last timestep.

We see the breakdown barely propagated outwards and seemingly didn’t affect the rest of the simulation much at all.

6.2.2 Check simulation results in the town of Sõma

Historic Data for Sõma is available by the NOAA Database.

The NOAA Database lists a travel time of 9 minutes for the first wave to reach Sõma, which is significantly faster than our simulation. We don’t know what the NOAA’s criteria is for the travel minutes so the difference might be due to that. The Database also lists a maximum height of \(9.3m\).

With the linked data we tried to approximate the wavespeed of the first wave too.

First we averaged the bathymetry between the epicenter (0,0) and Sõma (-54.6km, -127.6km) to get a rough estimate of the average depth between the two points. We got a value of \(-255.61418m\). The height should be the additive inverse of this value, so \(255.61418m\). With the provided formula the wavespeed would be \(\sqrt{9.80665 * 255.61418} = 50 \frac{m}{s}\). Sõma lies \(\sqrt{54.6^2 + 127.6^2} = 138.8km\) away from the epicenter. So the wave takes \(\frac{138.8km}{50 \frac{m}{s}} = 2776s \approx 46min\) to reach Sõma.

In our simulation we placed a station at (-54600m, -127600m) and measured h, hu and hv.

_images/6_Soma_h.png

height at Sõma over 5h (1000m resolution, plotted every 30s)

_images/6_Soma_hhuhv.png

height, momentum_x and momentum_y at Sõma over 5h (1000m resolution, plotted every 30s)

We see that the first wave reaches Sõma at roughly \(2400s \approx 40min\), so slightly earlier than calculated. This is likely a result of the calculation being from the epicenter to Sõma while the displacement extends nearer to Sõma. Since both are pretty close too each other so we feel relatively confident in our simulation.

According to the simulation Sõma saw a maximum height of roughly \(6.25m\).