SimCenter Forum

Hi Huy,

Let me add a slight clarification to the detailed response Jinyan provided: Although Hazus does not have storm-surge specific fragility and loss functions, the hurricane technical manual describes that the functions developed for flood should be used for this purpose. We have those available and they are applied in the wind+storm surge example.
In other words, as long as you have a Peak Inundation Height intensity measure available, you can use the auto-population script in the example to apply the Hazus fragilities and estimate damage and losses from storm surge.

Another relevant detail is the combination of wind and inundation losses. It is important to combine these without double counting. We use the combination methodology described in the Hazus Hurricane Technical Manual and this process is automatically performed in the background.

I hope this helps, let me know if you have any questions.

Adam

Hi Jia,

Example 2 uses the MDOF_LU tool to generate an idealized finite element model for each building and obtain the peak floor acceleration (PFA) and peak interstory drift ratio (PID) at each floor. The tool was developed by Prof. Xinzheng Lu's research group.

The capabilities are described to some extent in the appendix of this publication: http://dx.doi.org/10.1016/j.advengsoft.2014.01.010 .

You can also take a look at the source code here: https://github.com/NHERI-SimCenter/SimCenterBackendApplications/tree/master/modules/createSAM/MDOF-LU
Most assumptions are coded into the Building.cpp and HazusSAM_Generator.cpp files.

Now, to answer your specific questions:

1, Take a look at the CalcBldgPara function in HazusSAM_Generator.cpp. The four code levels are enumerated as integers ranging from 0 to 3 and you'll see how the Zone, Year of Construction, and Structure Type are used to obtain the design level. The developers aimed to implement the logic presented in the Hazus Earthquake Model; please let us know if you experience any errors in their implementation.

2, The damage is stored in the DM_*.csv file (where * is replaced by the range of building IDs). Example 2 uses the fragility functions from the Hazus Earthquake Model to simulate damages; this yields Damage States ranging from 0 to 4. 0 corresponds to no damage, while 1-2-3-4 corresponds to slight, moderate, extensive, and complete, just like you described in your question. Damage state 4 has two mutually exclusive sub-states (see some clarification on this in the end*), complete damage and collapse. Following the Hazus methodology, complete damage does not yield injuries, while collapse results in injuries and fatalities. Complete damage is encoded as DS 4_1, while collapse is encoded as DS 4_2.
You shall see the likelihood of observing each damage state in the structural and non-structural components of each building. If you are looking for each damage realization, you'll need to check the "Output EDP, DM, DV, every sampling realization" in the General Information (GI) panel of R2D (see here: https://nheri-simcenter.github.io/R2D-Documentation/common/user_manual/usage/desktop/R2DTool/GI.html). Afterward, you'll see a realizations.hdf5 file among the results that provides a specific damage state for each realization for each building. Let me know if you need more information on how to extract the information from this file.

3, PID in the EDP file refers to Peak Interstory Drift Ratio. As far as I can tell, this is in line with the PBE tool training video and has no unit.

Let me know if you have further questions.

Adam


* Additional information on mutually exclusive damage states:
Currently, R2D uses Pelicun 2.6 to simulate damage and loss. This earlier version of Pelicun followed the FEMA P-58 naming convention and assigned Damage State Groups (DSG) to fragility functions and each DSG could have one or more Damage States in it. This led to the DS_X_Y type of identification where X refers to the DSG and Y refers to the DS.
For the sake of clarity, with Pelicun 3, I updated this naming convention using Limit States instead of DSG. So, the results of an analysis performed by Pelicun 3 will show LS_X to identify the limit states or DS_Y to identify the damage states. I wanted to mention this detail here because Pelicun 3 will be available in R2D this April and it will completely replace Pelicun 2.6 in the near future.

Hi Navid,

The consequence models for unsafe placards and injuries are not yet implemented in Pelicun 3.

As for unsafe placards, in our experience, there is consensus in both the researcher and practitioner community that the current methodology in FEMA P58 provides unrealistic estimates. A new, more complex methodology is developed by the ATC 138 project and will be released in the near future. At that point, we plan to implement a methodology in Pelicun that supports both the old and the new approach to calculating unsafe placards to support benchmarking and evaluation of the impact of changes.
The current methodology is available in Pelicun 2.6, but let us know if you found having it available in Pelicun 3 useful for your work. If we have sufficient interest in the current method, we can increase its priority and get it implemented before the ATC 138 project concludes.

As for injuries, we are developing an enhanced version of the methodology in Pelicun 2. We have the supporting datasets already available in Pelicun 3, but the implementation of the methodology is in progress. We plan to have injury calculations available by July 2023.

Let me know if you have further questions.

Adam

Hi Nikoch,

If you're interested in the database under PBE 3.0, you can find it as part of pelicun, here: https://github.com/NHERI-SimCenter/pelicun/tree/master/pelicun/resources
The fragility_DB_FEMA_P58_2nd CSV and JSON files have the fragility function data; and the bldg_repair, bldg_injury, and bldg_redtag files have the consequence function data.

Let me know if you are interested in the old version of the data we used under PBE 2.x and I am happy to send that to you.

Adam

Hi Anne,

sorry for joining this conversation a little late.

When I suggested the uq module, I meant the uq module of Pelicun. That supports truncated distributions out of the box.

The rejection sampling that Sang-ri suggested works for a single variable. It is somewhat inconvenient that you need a larger sample to make sure you have enough data left after rejecting the points outside your domain of interest, but that is not a big issue. However, when you want a correlated multivariate truncated distribution, rejections can lead to a very different correlation structure than what you get if you define them using a Gaussian copula between the truncated marginals. Neither solution is 'correct', but the two solutions are different.

Re Frank's question, I think lower and upper limits on any random variable could be useful to have in quoFEM.

Adam

Hi Sejin,

The currently available modules consider wind-borne debris using the approach from HAZUS: the debris environment is characterized for every building (one of four possibilities), and the (building level) damage state at any given wind speed is influenced by the selected environment. This is a crude but efficient approach that does not take advantage of any local simulation.

You can certainly:
- Introduce more sophisticated archetypes that better represent the aerodynamic characteristics of various buildings and debris environments.
- Introduce a more sophisticated mapping of available information on the built environment to debris environment classes
- Add a debris trajectory module to R2D.

The first two options are relatively straightforward. The complexity of the last one depends on the methodology you plan to use to model the creation (i.e. after buildings or the environment are damaged) and path of debris in the area. If you can tell us a bit more about that methodology, I can give you more information about the complexity of implementing it in our backend and in R2D.

Adam

Hi Andrés,

Sounds good! Don't hesitate to reach out if you have any questions or run into issues.

Adam

Hi Pooya,

Thanks for drawing my attention to this issue. I've added a few demand types so that everything listed in the fragility database is now supported by Pelicun. Specifically, I've added these new types:

* Peak Link Rotation Angle - LR
* Peak Link Beam Chord Rotation - LBR
* Peak Floor Displacement - PFD
* Peak Effective Drift Ratio - EDR

Let me know if there is any other demand type you would find useful to have in Pelicun.

Adam