<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Sanaz Rezaeian</dc:contributor>
  <dc:contributor>Andrew James Makdisi</dc:contributor>
  <dc:contributor>Nico Luco</dc:contributor>
  <dc:creator>N. Simon Kwong</dc:creator>
  <dc:date>2024</dc:date>
  <dc:description>The seismic response of concrete dams depends on both the horizontal (H) and vertical (V) components of ground motion (GM), and excluding the V components when conducting response history analyses (RHAs) may underestimate the seismic fragility. Although V components of GM time series could be selected to be consistent with the hazard, hazard curves for the V component (or for short, V hazard curves) are rarely available for evaluating such hazard consistency. One of the challenges in developing V hazard curves in the U.S. Geological Survey (USGS) National Seismic Hazard Model (NSHM) is the lack of ground motion models (GMMs) that directly estimate intensity measures (IMs) for the V component of GM. In this study, we compare alternative approaches of developing V hazard curves. Using a case study in California, we compare V hazard curves computed from GMMs for the V component of GM against those from applying GMMs for the V/H ratios and those from selecting multicomponent time series that are consistent with the H hazard. We discuss and invite feedback on issues such as availability of GMMs, applicability of GMMs, and choice of inputs for ground motion selection and modification (GMSM).</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:language>en</dc:language>
  <dc:publisher>International Association for Earthquake Engineering</dc:publisher>
  <dc:title>Challenges in developing vertical hazard for seismic analysis of concrete dams</dc:title>
  <dc:type>text</dc:type>
</oai_dc:dc>