<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd" xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>00000cab a22000003a 4500</leader>
  <controlfield tag="001">UP-99796217610304224</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20231008000655.0</controlfield>
  <controlfield tag="006">a    grb    001 u|</controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">120514s        xx     d | ||r |||||   ||</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">DENG</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1="0" ind2=" ">
   <subfield code="a">Liao, S.</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">Physically compliant, conditionally simulated spatially variable seismic ground motions for performance-based design.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">pp. 891-919</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
   <subfield code="a">The performance-based design of lifeline systems requires spatially variable seismic excitations at the structures' supports that are consistent with prescribed seismic ground motion characteristics and an appropriate spatial variability model?such motions can be obtained through conditional simulation.  This work revisits the concept of conditional simulation and critically examines the conformity of the generated motions with the characteristics of the target random field and observations from data recorded at dense instrument arrays. Baseline adjustment processing techniques for recorded earthquake accelerograms are extended to fit the requirements of simulated and conditionally simulated spatially variable ground motions. Emphasis is placed on the use of causal vs acausal filtering in the data processing. Acceleration, velocity and displacement time histories are evaluated in two example applications of the approach. The first application deals with a prescribed synthetic time history that incorporates nonstationarity in the amplitude and frequency content of the motions and depends on earthquake magnitude, source?site distance and local soil conditions; this example results in zero residual displacements. The second application considers as prescribed time history a recording in the vicinity of a fault and yields nonzero residual displacements. It is shown that the conditionally simulated time histories preserve the characteristics of the prescribed ones and are consistent with the target random field. The results of this analysis suggest that the presented methodology provides a useful tool for the generation of spatially variable ground motions to be used in the performance-based design of lifeline systems.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Seismic ground motions.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Spatial variability.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Conditional simulation.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Amplitude and phase variability.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Record processing.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Causal and acausal filtering.</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Earthquake engineering &amp; structural dynamics.</subfield>
   <subfield code="g">35, 7 (2006).</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FO</subfield>
  </datafield>
  <datafield tag="852" ind1=" " ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DENG</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Article</subfield>
  </datafield>
 </record>
</collection>
