Transcript No Slide Title

SIG: Synthetic Seismogram Exchange
Standards (formats & metadata)
Is it time to establish exchange standards for
synthetic seismograms?
David Okaya, USC
Tim Ahern, IRIS
Goal of SIG: initiate dialogue within IRIS community
Recommendation: international effort to make a prototype
IRIS Annual Workshop 12 June 2004
SIG: Synthetics Exchange Standards
David Okaya
Why an Exchange Standard?
Dogan Seber
Importance of Metadata for Synthetics
Linus Kamb
But we have a standard -- Can SEED
support synthetics?
Seiji Tsuboi
XML-SEED: its application to synthetic
seismogram database
Torild van Eck
FDSN perspective on synthetics
Heiner Igel
SPICE efforts on synthetics
Discussion
Why an Exchange Standard?
• Archive and exchange between seismologists, geoscientists
and (civil/earthquake) engineers.
• Interoperatbility with upcoming digital and information
technologies:
- digital libraries.
- interdisciplinary cross-correlations.
- data and metadata searching, mining (KR&R).
- visualization methods from Computer Sciences.
• NSF-Cyberinfrastructure (e.g., GEON, SCEC/ITR);
international efforts such as SPICE.
Characteristics of Synthetic Seismograms
• As simple as single station 1- or 3-component seismograms (1D).
• Linear or spatial arrays of seismograms (2D to 3D).
• Wavefront snapshot volumes (3D) over time (4D for movies).
Kb - Mb
• Volumes:
Mb - Gb
# nodes / dim.
# dimensions
# components
100's Mb - Gb - Terabytes
What Exists Now?
• Traditional: SAC, AH, SEGY, CSS, ascii, raw binary, + readme
pros: known formats, familiar to communities, translators exist.
cons: limited metadata, limited use for 3D/4D.
• SEED/miniSEED
pros: infrastructure already exists for archive/distribution
translators, utilities.
cons: lacks familiarity within synthetics community; needs
alteration for higher D and metadata.
• Other forms: e.g., netCDF
pros: established use within other natural sciences &
engineering; useful for computer interoperatbility.
cons: "non-seismological"; little opportunity to adjust.
What Do We Need?
• Can be more than one format (based on dimensionality)
- one for single station or limited set of seismograms.
- another for large volumes (x-y-t; x-y-z, x-y-z-t)
(may want to "object"-ify large blocks of synthetic data.
• Metadata
- waveform or snapshot volume information (readme info).
- algorithm, code version, authorship.
- provenance (computation history).
• Usage
- easy to convert into from native code format.
- translators need to exist or easy to create (by coding).
- metadata tools to create and import values (within codes).
Example: SCEC/ITR Use of Synthetics
• SCEC/ITR is a $10M / 5-year Information Technology project.
• Collaboration between SCEC, USGS, IRIS, with SDSC, ISI.
PIs: T. Jordan, J.B. Minster, R. Moore, C. Kesselman.
• "Community Modeling Environment" (CME):
- Develop for broad audience an integrated information
infrastructure for earthquake science.
- Grid computing, digital libraries, KR&R, visualization.
• Role of Synthetics:
- Physics-based simulation of ground motion for seismic
hazard analysis.
- Takes into account wave propagation through 3D
structure, source dynamics, and (non)-linear
site effects.
SCEC/ITR Community Modeling Environment
KNOWLEDGE REPRESENTATION
& REASONING
Knowledge Server
Knowledge base access, Inference
Translation Services
Syntactic & semantic translation
Knowledge Base
Ontologies
Curated taxonomies,
Relations & constraints
DIGITAL
LIBRARIES
Pathway Models
Pathway templates,
Models of simulation codes
Navigation &
Queries
Versioning,
Topic maps
Code
Repositories
FSM
RDM
AWM
Mediated
Collections
Federated
access
SRM
KNOWLEDGE
ACQUISITION
Acquisition Interfaces
Dialog planning,
Pathway construction
strategies
Pathway Assembly
Template instantiation,
Resource selection,
Constraint checking
Users
Data & Simulation
Products
Data Collections
GRID
Pathway Execution
Policy, Data ingest, Repository access
Pathway
Instantiations
Grid Services
Compute & storage management, Security
Computing
Storage
User
Choices
FD/FE
Inputs, Velocities, Code
Computation
Curation
Derived
Products
KNOWLEDGE REPRESENTATION
& REASONING
Knowledge Server
Knowledge base access, Inference
Translation Services
Syntactic & semantic translation
Knowledge Base
Ontologies
Curated taxonomies,
Relations & constraints
DIGITAL
LIBRARIES
Pathway Models
Pathway templates,
Models of simulation codes
Navigation &
Queries
Versioning,
Topic maps
Code
Repositories
FSM
RDM
AWM
Mediated
Collections
Federated
access
SRM
KNOWLEDGE
ACQUISITION
Acquisition Interfaces
Dialog planning,
Pathway construction
strategies
Pathway Assembly
Template instantiation,
Resource selection,
Constraint checking
Users
Data & Simulation
Products
Data Collections
GRID
Pathway Execution
Policy, Data ingest, Repository access
Pathway
Instantiations
Grid Services
Compute & storage management, Security
Computing
Storage
Do We Need a Standard?
• For individual work, not necessarily.
• Useful for exchange among seismologists.
• Essential for IT interoperability.
Suggestion: Develop a Prototype Standard
• Establish a small international working group to:
- define a strawman prototype.
- examine the issue of what metadata are needed.
- put under umbrella of FDSN (a la SEED).
- Volunteers?
SIG: Synthetics Exchange Standards
David Okaya
Why an Exchange Standard?
Dogan Seber
Importance of Metadata for Synthetics
Linus Kamb
But we have a standard -- Can SEED
support synthetics?
Seiji Tsuboi
XML-SEED: its application to synthetic
seismogram database
Torild van Eck
FDSN perspective on synthetics
Heiner Igel
SPICE efforts on synthetics
Discussion