Normal Mode (Mineos Package) Tutorial

Author: Guy Masters

I/O and documentation: Misha Barmin

1. Background and theory of normal mode syntheticseismograms provided by Guy this AM.

2. Brief overview of the code: 4 programs, I/O flow.3. To Run the Code: Inputs needed, CSS data base

description & Antelope interface.4. Example outputs.5. Utilities: e.g., conversion to SAC waveforms.6. Users run programs….. Led by Misha…..

Status & Documentation

Status of the code: the code is being Beta tested right now. Version 1.0 has not been completely bench-marked. The official version will become available from CIG (www.geodynamics.org) in about a month. Please don’t take the code home. If you do take thecode home, DO NOT DISTRIBUTE IT, and replace it with the official version soon to become available from CIG.

Documentation you should have: Mineos Version 1.0 (Draft) User’s ManualTutorial: The Mineos Package

2. The Code

Minos_bran -- computes the eigenfunctions and

eigenfrequencies.

Eigcon -- renormalizes the eigenfunctions and

outputs into an extension of CSS. (.eigen relation)

Four programs in the Mineos Package:

Green -- computes Green functions. (.wfdisc)

Syndat -- computes the synthetic seismograms.

(.wfdisc)

EigenfunctionSystem

SyntheticSeismogramSystem

2. I/O Flow

Eigenfunction System

2. I/O Flow

Synthetic Seismogram System

3. To Run the Code: Inputs Needed

1. 1D model. (four models provided for the tutorial)2. Station:channel list: .sitechan & .site from CSS3.0.3. CMT solution: cmt_event -- unformatted ascii file.

(Similar to Guy’s locale file.)

To create .sitechan & .site:• Research: comparing with data, use a SEED volume

and run RDSEED or sd2db or seed2db.• Teaching: utility simpledit helps.

To create cmt_event:Simple unformatted file. Create by hand. (A later versionwill have a utility for converting from Harvard CMT file.)

Center for Seismic Studies 3.0 Relational Data Base Schema

Relational Data Base Terminology:File = “Relation”Row = “tuple”Specific set of columns = “Field”Connecting tables = “Join”

Disadvantage of utilizing CSS3.0: • Although in ascii, the relations are formatted files and

format must be followed religiously.• Relevant information sometimes requires multiple files.

(e.g., .site & .sitechan; .origin, .centryd, .moment)

Advantage: • Core schema is well defined and documented.• Processing/Viewing software exists (Antelope).• Format interconversion software exists.• Easily extendable.

Center for Seismic Studies 3.0 Relational Data Base Schema

.wfdisc --> waveforms on disk

.site

.sitechan -- also connects to .sensor

.sensor

.instrument

.event

.origin -- needed onlyto create SAC files.

.centryd

.moment

Extension: .eigen relation --> eigenfunctions on disk.

Our Approach: hybrid -- take core relations from CSS3.0 & minimally extend it, but also represent event information with a simple unformatted ascii file.

Event information: unformatted file event_cmt.

4. Example Outputs

Outputs:Eigcon: .eigen relation --> eigenfunctions on disk.

Utility preigen prints chosen eigenfunctions.

Green: .wfdisc relation --> multiplexed Greenfunctions on disk.

Syndat: .wfdisc relation --> synthetic seismogramson disk. Units: ground motion (nm/sec), no instrument responses.

Waveforms viewable with Antelope’s dbe or dbpick.

Example: event in S. China, spheroidal & toroidal, 0 < n < 150, 0 < f < 166 mHz, 0 < l < 10000.These results are in directory /Demo1

Phase arrivals generated by dbpick using iaspei model.

Phase arrivals generated by dbpick using iaspei model.

5. Utilities

simpledit -- to create .site & .sitechan tables.

preigen -- prints chosen eigenfunctions.

create_origin -- creates an .origin table from a cmt_eventtable.

css2sac -- reads .origin, .site, .sitechan, and .wfdisc andcreates SAC waveform files with fully populatedheaders.