Spring 1998 After discussions with John Anderson and those who attended the organizational meeting Jan. 21 I propose the following proceedures and format for the class. 1. All seismology students will be required to audit the class and participate in weekly record reading sessions. 2. This year we will emphasize retrieving seismograms from internet sources. The first few sessions will emphasize proceedures for doing this, and will feature presentations by Glenn Biasi, Gene Ichinose, Arturo, and others? who have some experience doing this. 3. Starting about mid-February students will be assigned responsibility to collect data for the earthquakes of the week, and at least one other interesting earthquake if there are none ocurring during the week, and preparing to lead discussion and analysis of the seismograms on the subsequent Wednesday. At that time Jim Brune and others will give a half hour lecture on interpretation of seismograms at the beginning of the class. 4. Copies of notes will be made for some of the lectures by Jim Brune. The notes have a list of references on interpretation of seismograms. These references will be on file in the Seismology office for students to check out.
These web sites provide useful information for waveform data shopping. Data can be obtained by either applying for a research Unix shell account or by anonymous web access.
(katrin@scec.gps.caltech.edu) or one may request an account on the
Southern California Earthquake Center Data Center by:
telnet scec.gps.caltech.edu
login: bulletin
(email:doug@seismo.berkeley.edu)
or one may request an account by:
telnet quake.geo.berkeley.edu
login: bulletin
passwd: board
telnet dmc.iris.washington.edu
login: bulletin
passwd: board
When sitting down to construct a data set, one should consider gathering this information:
Instrument |
Gain |
Orientation |
|---|---|---|
| S,V - short period | H - high | Z - vertical |
| B - broadband (10-20 sps) | L - low | N - north |
| L - long period (1 sps) | F - very low | E - east |
| A - accelerometer (100 sps) | S - strong motion | . |
| E - extremely long period (0.001 sps) | . | . |
| H - high broadband (80-100 sps) | . | . |
| V - very long period | . | . |
| U - ultra long period (0.01 sps) | . | . |
For example, the file name 1997.312.10.13.07.4280.COLA.LHZ.SAC
has the format {year}.{julian_day}.{hour}.{minutes}.{seconds}.{millisec}.{station_id}.{component}.{data_format}
year=1997
julian_day=312
hour=10;minutes=13;seconds=07;millisec=4280
station_id=COLA
component=LHZ (L=long period instrument, H=high gain, Z=vertical component)
data_format=SAC (seismic analysis code binary format)
19980128225304) or by year, jullian day, hour, minute, and second
(e.g. 1998.028.22.53.04).
The SEED format is used by many data centers. A SEED file can be very large (several to hundreds of megabytes) and contains waveform data, trigger information, and instrument responses.

What is PlotStack? This program reads a list of SAC format files and plots a record section or
shot gather (Seismograms plotted as distance versus time). New options
include plotting in kilometers, degrees, reduced travel time, and various
amplitude gain controls. The dist and gcarc header values need to be in the SAC header and if
merging datasets from different seismic networks, you might need to do a SYNCH (SYNCHRONIZE) command in SAC.
Graphics supports X11, postscript, color postscript, tcl, and xfig. Other SAC tools include:
sacinfo - output sac header values quickly in the unix shell (SunOs version)
OriginSac - quickly inserts origin times into sac files and shift (SunOs version)
(SunOS to LINUX or LINUX to SunOS) - a big - little endian conversion for SAC (linux version)

Here is an example of the June 9th 1994, Mw=8.0 Bolivia Earthquake. This earthquake captured the interest of many people
not just because of its depth (627 km), but also because ground motions were felt as far away as North America.

This plot uses a reduction velocity of 10 (km/sec). A Reduction velocity allows phases which travel
at that velocity to plot at an infinite apparent velocity (i.e. no moveout or dt/dx=0). This is
simply done by shifting traces by tshift where tshift equals distance divided by reduction velocity.
Notice in this plot that most phases plot where dt/dx is negative which usually means they travel
faster than 10 km/sec for local and regional record sections. This is not the case here because
we are assuming a flat earth with this reduction velocity and not taking into account the spherical shape of the earth.
The fastest velocities may occur in the lower
mantle around Vp=13 km/sec.
More on reduction velocity later...



This is the CUSP data from the Ridgecrest earthquake plotted using a 8 km/sec reduction velocity. Notice the point at distance delta=170km and reduced time (tau=6.5sec). There is a change in Pg moveout. This is where the Pn begins to arrive. Remember tau is reduced time and not actual two way travel time. Before delta=170km is the Pg and beyond 170 km is the Pn phase arrivals. The Pn plots a little faster than 8km/sec because it has a slight negative moveout (the slope dt/dx is negative). It turns out that plotting at a reduction velocity of 8.2km/sec gives a zero slope for Pn and a revised crustal thickness of z=33.5km. Kanamori et al. (19??) was the original one who did this for southern California and found that the crust is usually around z=32 km thick.
The time when Pn arrives appears highly variable. This may be due to arrivals at different azimuths, where the crustal thicknesses varies in southern California, from like fast cold crustal roots under mountain ranges, or slow hot asthenosphere intruding into the lower crust. Caution... The lateral travel path of Pn results in the fact that Pn is a very emmergent phase and difficult to pick accurately relative to Pg. The crust-mantle interface apparently does vary in depth. This is called Moho Topography) and the depth to Moho varies from z=10 in the Salton Trough to > 40 km under the Peninsular Ranges.
|
|
Author: G. A. Ichinose | ||||||
| UNR Seismology Lab Homepage |