SIG: Synthetic Seismogram Exchange Standards (formats & metadata)

1. Goal of SIG: initiate dialogue within IRIS community Recommendation: international effort to make a prototype SIG: Synthetic Seismogram Exchange Standards (formats & metadata) Is it time to establish exchange standards for synthetic seismograms? David Okaya, USC Tim Ahern, IRIS IRIS Annual Workshop 12 June 2004

2. 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

3. 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.

4. •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 Mb - Gb 100's Mb - Gb - Terabytes Characteristics of Synthetic Seismograms •Volumes: # nodes / dim. # dimensions # components

5. 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.

6. •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). What Do We Need?

7. 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.

8. KNOWLEDGE REPRESENTATION & REASONING Knowledge Server Knowledge base access, Inference Translation Services Syntactic & semantic translation Knowledge Base Ontologies Curated taxonomies, Relations & constraints Pathway Models Pathway templates, Models of simulation codes DIGITAL LIBRARIES Navigation & Queries Versioning, Topic maps Mediated Collections Federated access KNOWLEDGE ACQUISITION Acquisition Interfaces Dialog planning, Pathway construction strategies Pathway Assembly Template instantiation, Resource selection, Constraint checking Code Repositories FSM RDM AWM SRM Users Data & Simulation Products Data Collections GRID Pathway Execution Policy, Data ingest, Repository access Grid Services Compute & storage management, Security Pathway Instantiations Storage Computing SCEC/ITR Community Modeling Environment

9. FD/FE User Choices Derived Products Inputs, Velocities, Code Computation Curation KNOWLEDGE REPRESENTATION & REASONING Knowledge Server Knowledge base access, Inference Translation Services Syntactic & semantic translation Knowledge Base Ontologies Curated taxonomies, Relations & constraints Pathway Models Pathway templates, Models of simulation codes DIGITAL LIBRARIES Navigation & Queries Versioning, Topic maps Mediated Collections Federated access DIGITAL LIBRARIES Navigation & Queries Versioning, Topic maps Mediated Collections Federated access KNOWLEDGE ACQUISITION Acquisition Interfaces Dialog planning, Pathway construction strategies Pathway Assembly Template instantiation, Resource selection, Constraint checking KNOWLEDGE ACQUISITION Acquisition Interfaces Dialog planning, Pathway construction strategies Pathway Assembly Template instantiation, Resource selection, Constraint checking Code Repositories FSM RDM AWM SRM Users Data & Simulation Products Data Collections GRID Pathway Execution Policy, Data ingest, Repository access Grid Services Compute & storage management, Security GRID Pathway Execution Policy, Data ingest, Repository access Grid Services Compute & storage management, Security Pathway Instantiations Storage Computing

10. 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? Do We Need a Standard? • For individual work, not necessarily. • Useful for exchange among seismologists. • Essential for IT interoperability.

11. 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