Rick Benson Saturday, Aug 14, 14:00 August 13-19, 2010Data Management Workshop Foz do Iguassu- Brazil

Metadata & RESP files SEED Notes and Shortcuts August 13-19, 2010Data Management Workshop Foz do Iguassu- Brazil

Data Preservation is Important EOS Policy Statement

Why is metadata important? November 8-17, 2009 They are the Rosetta Stone- making it possible to decode information well into the future Increases accessibility: “tell me where sites are in a region”, or “what are station names in an area”, or “what instruments operate in a region”, etc. Retention of context- who operates instruments, etc Remember: People forget! Carefully created, they create both short and long-term benefits by capturing “tribal knowledge” when it’s still available, like equipment (serial numbers), sample rates, gains, documenting an accurate history of ground motion Data Management Workshop Foz do Iguassu- Brazil

November 8-17, 2009 Metadata In(di)gestion Functionally, we use “technical” metadata, in that it is used to describe how the seismic system behaves, and limited software description (like compression, etc) Functionally, we use “technical” metadata, in that it is used to describe how the seismic system behaves, and limited software description (like compression, etc) metadata can be shared in dataless SEED, which makes metadata “portable” amongst heterogeneous systems Whenever anything changes at a site, new metadata should be exchanged with archives or other networks using it Data Management Workshop Foz do Iguassu- Brazil

First: Registering Network and Stations  To request a FDSN network code, start here for either a permanent or temporary network code:  To register your stations with the World Data Centers ISC and NEIC, start here: This should be done before sharing data or parametric data with other agencies. November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

SEED Comments:  SEED format designed for data exchange and archiving. Only now becoming more common in processing, so format conversion likely required.  Coordinates in decimal degrees  and NOT ’6’’  Elevation in Meters  Velocity and displacement in Meters  Acceleration in meters/sec 2 November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

SEED v2.4 Manual November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

Introduction to SEED  Recommended reading for an overview of SEED is this Chapter from the SEED manual, which is also located on your USB stick. Includes notes about Design Goals and Strategies, Recommended Uses, and conventions. November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

Channel naming convention for common sensors: November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil A gain of 250 V/m/s was somewhat arbitrarily chosen as the division between 'High gain' and 'Low gain' for velocity sensors. Those 250 V/m/s and higher would use “H” as the instrument code, those less than 250 V/m/s would use “L”.

High Gain vs. Low Gain November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

Notes about SEED “channels”  For consistency with the SEED manual, “L” is recommended as the instrument code for the 4.5 Hz geophone sensor, though in practice it is considered a geophone. Example: LLE, LLN, LLZ  The SEED manual recommends “P”, the geophone code, for sensors with a natural frequency of Hz and higher. Example: LPE, LPN, LPZ  For accelerometers, the use of the broad-band band codes "H" and "B" for the band code of the channel name are recommended. While the term "broad-band" is typical with respect to the flat portion of the response curve of velocity sensors, its use is logical for accelerometers, considering their responses are flat with respect to acceleration. Example: HNE,HNN, HNZ November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

RESP format files and info  The program RDSEED creates and supports the format   For Windows Users: Jrdseed   Created on command line with syntax like this  Rdseed –fR ‘SEED_volume’ OR  rdseed -f PBMOout.seed –R gives the same output November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil Files are named like this RESP.AF.GSN.01.LHE

What’s in a RESP file?  The Response is carefully derived from first principles: ground motion (meters) -> sensor -> Volts -> electronics -> volts -> Analog-to-digital converter -> counts -> digital filters -> counts  Therefore, RESP files contain all the digital filter information,  Something that SAC Pole/Zero (PZ) files do not November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

Example RESP file, cascade November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil Stage 1= Sensor In this case, KS Borehole in Boshof, South Africa Goes from M/S ground Motion to Volts

Stage 2 = Datalogger November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil Volts are converted To counts

Stage 3-n = Digital Filtering & Downsampling November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil Transfer function type

Reporting Filter Delays & Decimation November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil

Overall Gain (also called Sensivitity) November 8-17, 2009Data Management Workshop Foz do Iguassu- Brazil The very last stage in the response cascade is the overall gain of the whole system, which is the Multiple of all stage gains at the same frequency, and called Stage 0

Where can I get RESP files?  These are produced using ‘rdseed’:  Rdseed –fR SEED.volume (either dataless or full)  Viewed using “metadata aggregator” or at the channel level.  IRIS will soon have a Web Service located at where one service will be RESP file returns August 13-19, 2010Data Management Workshop Fox do Iguassu- Brazil