March 25, 2002EarthScope CSIT Workshop Data Archiving and IT Issues for PBO Douglas Neuhauser UC Berkeley Seismological Lab Northern California Earthquake Data Center

March 25, 2002 EarthScope CSIT Workshop Plate Boundary Observatory n Measure broadband deformation across the western US. n Measure strain rate in 4D. n Determine forces responsible for plate boundary deformation.

March 25, 2002 EarthScope CSIT Workshop PBO Instrumentation n Continuous GPS. n Borehole strainmeters and related sensors. n Surface strainmeters and related sensors. n Borehole seismometers.

March 25, 2002 EarthScope CSIT Workshop Borehole Installations n 3 component tensor strainmeter n Pore pressure sensor. n Barometric pressure sensor. n Borehole seismometers.

March 25, 2002 EarthScope CSIT Workshop PBO Borehole Installation n Borehole contains strainmeters, seismometers, and other geophysical sensors. n GPS attached to borehole casing.

March 25, 2002 EarthScope CSIT Workshop Surface Strainmeter Installations n Laser interferometer for horizontal distance measurement. n Laser interferometers for pier anchors. n State-of-health sensors for data correction (vacuum pressure, laser frequency, etc.)

March 25, 2002 EarthScope CSIT Workshop Data Archive Issues for EarthScope n 1. What standard data processing should be performed on EarthScope data to create “standard products”?

March 25, 2002 EarthScope CSIT Workshop Seismic Data Processing n Minimal processing required (clock timing corrections). n Sensors directly measure ground motion (velocity or acceleration). n Sensors have well defined instrument responses. n SEED standard for data archiving and data distribution include data and response.

March 25, 2002 EarthScope CSIT Workshop GPS Data Processing

March 25, 2002 EarthScope CSIT Workshop Strain Data Processing n Multiple stages involved in processing strain data.

March 25, 2002 EarthScope CSIT Workshop Data Archive Issues for EarthScope n 2. How do we establish procedures for different stages of data processing? u Correct strain from pore pressure and atmospheric pressure channels? u Remove tides from strain data?

March 25, 2002 EarthScope CSIT Workshop Strain Data Processing Procedure

March 25, 2002 EarthScope CSIT Workshop Data Archive Issues for EarthScope n 3. How do we organize the data so that users know which data channels for an experiment are associated with each other, where there are several raw channels of the same type? u Tensor strain u Pore pressure u Barometric pressure u Temperature channels u Seismic channels u Various voltage / State-of-Health channels

March 25, 2002 EarthScope CSIT Workshop USGS Low Frequency Geophysical Network (UL) n Diverse set of geophysical experiments: u Strain (tensor, volumetric, wire) u Creep u Tilt (lake level, long baseline) u Well water levels u Electric potential n Each experiment has primary and auxiliary data channels.

March 25, 2002 EarthScope CSIT Workshop USGS Low Frequency Geophysical Network (UL) n Data used by and distributed to other researchers by the PI. n Data available in “raw” and “processed” versions. n Instrument responses often not well known.

March 25, 2002 EarthScope CSIT Workshop UL Data Archiving issues n 1. What format(s) to use for archive and distribution for raw and processed data? n How many versions of the data (“raw” and “processed”) should be archived? n How to make the data readily available to the community for use with other data sets?

March 25, 2002 EarthScope CSIT Workshop Data Archive Issues for EarthScope n 4. What data format(s) do we need for the various types of data? u How do we indicate what processing has been done to data channels? u SEED naming convention of NET, STATION, CHANNEL, and LOCATION may not provide sufficient diversity.

March 25, 2002 EarthScope CSIT Workshop UL Data Archive at NCEDC n Raw data time series archived in SEED format at NCEDC. u NETWORK name is UL. u STATION name is geographic site. u CHANNEL name designates type of measurement (instrument, sample rate, instrument bandwidth). u LOCATION name signifies experiment type and instance at the site.

March 25, 2002 EarthScope CSIT Workshop UL Data Archive at USGS n Automated “cleaned” data available from USGS in simple ASCII format. u Glitch and offset removal. u “Cleaned” primary data channels may be corrected by data from auxiliary data channels. u Minimal info about “cleaning” process provided with “cleaned” data. u Data distributed with USGS 4 character channel name.

March 25, 2002 EarthScope CSIT Workshop Data Archive Issues for EarthScope n 5. What data archive and distribution models are needed to provide users with integrated access to the complementary data sets? For example: u Will people want to integrate GPS data and strainmeter data? u What are data format and metadata requirements to accomplish this?

March 25, 2002 EarthScope CSIT Workshop NetDC Archive Model

March 25, 2002 EarthScope CSIT Workshop NetDC Archive Model

March 25, 2002 EarthScope CSIT Workshop GSAC Archive Model

March 25, 2002 EarthScope CSIT Workshop FISSURES Archive Model

March 25, 2002 EarthScope CSIT Workshop Data Archive Issues for EarthScope n 6. How do we address these issues in a framework that allows both people and inference or processing systems to make intelligent use of EarthScope data?