1 / 9

The Impact of Small Quakes and Noise Events: Understanding and Possible Solutions

Explore the causes and consequences of small quakes and noise events, and discover ways to make systems smarter to mitigate their effects. Learn about the limitations of current systems and how to fine-tune criteria for generating accurate ShakeMaps.

ralbertson
Download Presentation

The Impact of Small Quakes and Noise Events: Understanding and Possible Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. When Good Quakes Go BadOrHow Do Small Quakes End Up Being BigAndWhy Can’t Something Be Done About It? David Oppenheimer Presented to CISN Steering and Advisory Committees at Caltech, 27 September 2007

  2. Where do Noise Events Come from? • Case 1 • Bad radio repeater at Oroville causes interference on 7 stations • Automated picks associate into Cape Mendocino “quake” • Coda durations last for 300-400s (M5)

  3. Where do Noise Events Come from? • Case 2 • Small quake occurs at Geysers • Automated “picks” are ok, but Oroville noise adds 2 bad picks. • No codas on BG stations. Oroville again causes codas of 300-400s (M5)

  4. Chronology of Event #40201796

  5. Solutions • Make picker smarter • RT differentiation of noise from signal • Squash bad magnitudes faster • Stifle ShakeCast generation

  6. Making systems smarter

  7. Making systems smarter

  8. Making systems smarter… Or, better, eliminate the problem

  9. What have we learned? • Fine tune criteria for generating ShakeMaps • ShakeCast needs to get smarter • Need to dynamically remove bad stations from system • Clients ascribe (too?) high level of reliability to CISN products. • CISN staff should work with clients to explain limitations

More Related