4.8. E9 - Tsunami

The Cascadia Subduction Zone (CSZ) separates the Juan de Fuca and North America plates, stretching approximately 1,000 km between California and British Columbia, Canada. A rupture of the CSZ may result in a megathrust earthquake and a subsequent tsunami. This example considers a tsunami event in the city of Seaside, located along the northern Oregon coast. A highlight of this example is that it shows how user-provided fragility functions are employed in the SimCenter workflow. The building inventory consists of 4744 buildings of different types and construction materials. For the tsunami hazard, the results of a Probabilistic Seismic-Tsunami Hazard Analysis (PSTHA; Park et. al. 2017), with a recurrence interval of 500 years, is employed. The building inventory, tsunami hazard raster, and building fragility functions are all from the Seaside testbed, made available by the Center of Excellence for Risk-Based Community Resilience Planning (CoE) as part of their Interdependent Networked Community Resilience Modeling Environment (IN-CORE) platform. They can be accessed online on the IN-CORE Web Tools website (https://incore.ncsa.illinois.edu/doc/incore/webtools.html).

1. Set the Units in the GI panel as shown in Fig. 4.8.1 and check interested output files.

   

   Fig. 4.8.1 R2D GI setup.

2. Set the Event Raster File in the HAZ panel to the “E9Tsunami/input_data/IMs/500yr/Tsu_500yr_Hmax.tif” in the “IMs” folder. The app would automatically load the hazard (Fig. 4.8.2). And the Units of Event Input File should be “meter”. In addition, set the coordinate reference system of your hazard raster.

   

   Fig. 4.8.2 R2D HAZ setup.

3. Select GIS File to BIM in the ASD panel and set the Import Path to “E9Tsunami/input_data/GISBuildingInventory/Seaside_Buildings.gpkg” (Fig. 4.8.3). Specify the building IDs that you would like to include in the simulation (e.g., 1-4744 for the entire inventory - note this may take very long time to run on a local machine, so it is suggested to first test with a small sample like 1-100 locally and then submit the entire run to DesignSafe - see more details in Fig. 4.8.10).

   

   Fig. 4.8.3 R2D ASD setup.

4. Set the Regional Mapping and SimCenterEvent in the HTA panel (e.g., Fig. 4.8.4). In this case, because we are using a raster for a hazard, select “Site Specified.” The raster will be sampled at each asset location.

   

   Fig. 4.8.4 R2D HTA setup.

5. Set the “Building Modeling” in MOD panel to “None”.

   

   Fig. 4.8.5 R2D MOD setup.

6. Set the “Building Analysis Engine” in ANA panel to “IMasEDP”.

   

   Fig. 4.8.6 R2D ANA setup.

7. Set the “Damage and Loss Method” in DL panel to “User-provided fragilitites”. Note please place the ruleset scripts and fragility functions in their individual folders so that the application could copy and load them later.

   

   Fig. 4.8.7 R2D DL setup.

8. Set the “UQ Application” in UQ panel to “None”.

   

   Fig. 4.8.8 R2D UQ setup.

After setting up the simulation, please click the RUN to execute the analysis. Once the simulation completed, the app would direct you to the RES panel (Fig. 4.8.9) where you could examine and export the results.

Fig. 4.8.9 R2D RES panel.

For simulating the damage and loss for a large region of interest (please remember to reset the building IDs in ASD), it would be efficient to submit and run the job to DesignSafe on Stampede2. This can be done in R2D by clicking RUN at DesignSafe (one would need to have a valid DesignSafe account for login and access the computing resource). Fig. 4.8.10 provides an example configuration to run the analysis (and please see R2D User Guide for detailed descriptions). The individual building simulations are paralleled when being conducted on Stampede2 which accelerate the process. It is suggested for the entire building inventory in this testbed to use 15 minutes with 96 Skylake (SKX) cores (e.g., 2 nodes with 48 processors per node) to complete the simulation. One would receive a job failure message if the specified CPU hours are not sufficient to complete the run. Note that the product of node number, processor number per node, and buildings per task should be greater than the total number of buildings in the inventory to be analyzed.

Fig. 4.8.10 R2D - Run at DesignSafe (configuration).

Users could monitor the job status and retrieve result data by GET from DesignSafe button (Fig. 4.8.11). The retrieved data include four major result files, i.e., BIM.hdf, EDP.hdf, DM.hdf, and DV.hdf. R2D also automatically converts the hdf files to csv files that are easier to work with. While R2D provides basic visualization functionalities (Fig. 4.8.9), users could access the data which are downloaded under the remote work directory, e.g., /Documents/R2D/RemoteWorkDir (this directory is machine specific and can be found in File->Preferences->Remote Jobs Directory). Once having these result files, users could extract and process interested information - the next section will use the results from this testbed as an example to discuss more details.

Fig. 4.8.11 R2D GET from DesignSafe.