24.11.2012 Views

Annual Meeting - SCEC.org

Annual Meeting - SCEC.org

Annual Meeting - SCEC.org

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Poster Abstracts<br />

HOW DOES DAMAGE AFFECT RUPTURE PROPAGATION ACROSS A FAULT STEPOVER? (A-074)<br />

H.M. Savage and M.L. Cooke<br />

We investigate the potential for fault damage to influence earthquake rupture at fault step-overs using a mechanical numerical<br />

model that explicitly includes the generation of cracks around faults. We compare the off-fault fracture patterns and slip<br />

profiles generated along faults with a variety of frictional slip-weakening distances and step-over geometry. Models with<br />

greater damage facilitate the transfer of slip to the second fault. Increasing separation and decreasing the overlap distance<br />

reduces the transfer of slip across the step over. This is consistent with observations of rupture stopping at step-over<br />

separation greater than 4 km (Wesnousky, 2006). In cases of slip transfer, rupture is often passed to the second fault before the<br />

damage zone cracks of the first fault reach the second fault. This implies that stresses from the damage fracture tips are<br />

transmitted elastically to the second fault to trigger the onset of slip along the second fault. Consequently, the growth of<br />

damage facilitates transfer of rupture from one fault to another across the step-over. In addition, the rupture propagates along<br />

the damage-producing fault faster than along the rougher fault that does not produce damage. While this result seems counter<br />

to our understanding that damage slows rupture propagation, which is documented in our models with pre-existing damage,<br />

these model results are suggesting an additional process. The slip along the newly created damage may unclamp portions of<br />

the fault ahead of the rupture and promote faster rupture. We simulate the M7.1 Hector Mine Earthquake and compare the<br />

generated fracture patterns to maps of surface damage. Because along with the detailed damage pattern, we also know the<br />

stress drop during the earthquake, we may begin to constrain parameters like the slip-weakening distance along portions of<br />

the faults that ruptured in the Hector Mine earthquake.<br />

PREPARING TRIAL MODELS OF SPATIAL VARIABILITY IN GEOTECHNICAL VELOCITIES FOR<br />

ASSESSING EFFECTS ON GROUND MOTIONS (B-058)<br />

W.H. Savran and J.N. Louie<br />

The Clark County Parcel Map provides us with a data set of geotechnical velocities in Las Vegas Valley, at an unprecedented<br />

level of detail. Las Vegas Valley is a basin with similar geologic properties to some areas of Southern California. We first<br />

analyze elementary spatial statistical properties of the Parcel Map. We then investigate the same spatial statistics from the<br />

peak ground velocity r226e226s226u226l226t226s226 226c226o226m226p226u226t226e226d226 226f226r226o226m226<br />

226 o 226 n 226 e 226 226 m 226 o 226 d 226 e 226 l 226 226 ( 226 B 226 l 226 a 226 c 226 k 226 226 H 226 i 226 l 226 l 226 s 226<br />

226F226a226u226l226t226)226 226t226h226a226t226 226i226n226c226o226r226p226o226r226a226t226e226 226t226h226e226<br />

226P226a226r226c226e226l226 226M 226a 226p226 226a226s226 226p 226a 226r226a226m226e226t226e226r226s226.226<br />

226 W 226 e 226 226 c 226 o 226 n 226 f 226 i 226 g 226 u 226 r 226 e 226 226 f 226 i 226 n 226 i 226 t 226 e 226 -<br />

226 d 226 i 226 f 226 f 226 e 226 r 226 e 226 n 226 c 226 e 226 226 s 226 e 226 i 226 s 226 m 226 i 226 c 226 226 w 226 a 226 v 226 e 226<br />

226p226r226o226p226a 226g226a226t226i226o226n 226 226m226o226d226e226l226s 226 226a226t 226 2260 226. 2265226<br />

226 H 226 z 226 226 w 226 i 226 t 226 h 226 226 L 226 L 226 N 226 L 226 s 226 226 E 226 3 226 D 226 226 c 226 o 226 d 226 e 226 , 226<br />

226u226t226i226l226i226z226i226n226g226 226t226h226e226 226P226a226r226c226e226l226 226M226a226p226 226a226s226<br />

226i226n226p226u226t226 226p226a226r226a226m226e226t226e226r226s226 226t226o226 226c226o226m226p226u226t226e226<br />

226 a 226 226 P 226 G 226 V 226 226 d 226 a 226 t 226 a 226 226 s 226 e 226 t 226 226 f 226 r 226 o 226 m 226 226 t 226 h 226 e 226<br />

226e 226a226r226t226h226q226u 226a226k 226e 226 226s226c 226e 226n226a 226r226i226o226.226 226 226T226h226e 226<br />

226 r 226 e 226 s 226 u 226 l 226 t 226 i 226 n 226 g 226 226 P 226 G 226 V 226 226 i 226 s 226 226 f 226 r 226 a 226 c 226 t 226 a 226 l 226<br />

226 o 226 v 226 e 226 r 226 226 t 226 h 226 e 226 226 s 226 a 226 m 226 e 226 226 s 226 p 226 a 226 t 226 i 226 a 226 l 226<br />

226f226r226e226q226u226e226n226c226i226e226s226 226a226s226 226t226h226e226 226V226s22632260226 226d226a226t226a226<br />

226s226e226t226s226 226a226s226s226o226c226i226a226t226e226d226 226w226i226t226h226 226t226h226e226i226r226<br />

226 r 226 e 226 s 226 p 226 e 226 c 226 t 226 i 226 v 226 e 226 226 m 226 o 226 d 226 e 226 l 226 s 226 . 226 226 226 T 226 h 226 e 226<br />

226 f 226 r 226 a 226 c 226 t 226 a 226 l 226 226 d 226 i 226 m 226 e 226 n 226 s 226 i 226 o 226 n 226 226 i 226 s 226<br />

226s226y226s226t226e226m226a226t226i226c226a226l226l226y226 226l226o226w226e226r226 226i226n226 226a226l226l226<br />

226o226f226 226t226h226e226 226P226G226V226 226m226a226p226s226 226a226s226 226o<br />

EARTHQUAKE AGES AND DISPLACEMENTS, FRAZIER MOUNTAIN PALEOSEISMIC SITE (A-141)<br />

K.M. Scharer, R.J. Weldon, B.C. Gibson, and A.R. Streig<br />

The Frazier Mountain paleoseismic site is located on a poorly understood section of the southern San Andreas fault, mid-way<br />

between the well-known Carrizo Plain and Mojave sites of Bidart Fan and Pallett Creek. Emerging paleoseismic evidence<br />

indicates that earthquakes along this stretch repeat at a similar pace, with an average interval of ~122 years between A.D. 1000<br />

226 | Southern California Earthquake Center

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!