From sheila at blacknest.gov.uk Tue Feb 9 08:20:31 2010 From: sheila at blacknest.gov.uk (Sheila Peacock) Date: Tue, 09 Feb 2010 16:20:31 +0000 Subject: [data-issues] pressure units in SEED files Message-ID: <4B718B4F.2020801@blacknest.gov.uk> Hello, We want to create SEED files of infrasound data, for which the quantity is pressure rather than acceleration, velocity or displacement. "rdseed" seems to be unable to cope with SEED header information (in blockette 34) that is not "M", "M/S" or "M/S**2". How should we proceed? Regards, Sheila Peacock AWE Blacknest From rick at iris.washington.edu Tue Feb 9 09:24:10 2010 From: rick at iris.washington.edu (Rick Benson) Date: Tue, 9 Feb 2010 09:24:10 -0800 Subject: [data-issues] pressure units in SEED files In-Reply-To: <4B718B4F.2020801@blacknest.gov.uk> References: <4B718B4F.2020801@blacknest.gov.uk> Message-ID: <9D07AA89-F336-4B1A-A94A-99C829AE52B3@iris.washington.edu> Hello, Sheila- Im glad you are utilizing SEED for these timeseries data, and the units of pressure are well accomodated within SEED and rdseed if the SEED file is written correctly. The abbreviation dictionary stores these blockette 34's, and what you need to do is create a new entry called 'pascals' and then refer to this abbreviation lookup code in the blockette 52. These are the SI units for pressure that are recommended. An example for a pressure sensor with HDO channel naming convention (The D is the instrument type for pressure) can be found for the New Mexico Tech infrasound sensor using the "mda" interface (metadata aggregator) http://www.iris.edu/mda/YD/DOM/09/HDO?timewindow=2007/01/07%2000:00:00-2007/01/13%2023:59:59 and take a look at the "View RESP" that should give you some guidance about SEED responses for these, too. I can build you a full SEED volume and send to you if that helps, or just submit a breq_fast asking for station DOM from YD net using location code 09 and channel HDO. Let me know if this doesn't help enough and we'll try to get you more info and help in any way we can. I am also available for checking on SEED formatting and verification at any time, so stay in touch and hope this helps. Cheers, Rick On Feb 9, 2010, at 8:20 AM, Sheila Peacock wrote: > Hello, > > We want to create SEED files of infrasound data, for which the > quantity is pressure rather than acceleration, velocity or displacement. > "rdseed" seems to be unable to cope with SEED header information > (in blockette 34) that is not "M", "M/S" or "M/S**2". How should > we proceed? > > Regards, > Sheila Peacock > AWE Blacknest > _______________________________________________ > data-issues mailing list > data-issues at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/data-issues ================ Rick Benson Director of Operations IRIS DMC (206)547-0393 ext. 119(office) rick at iris.washington.edu From rob at iris.washington.edu Tue Feb 9 09:28:01 2010 From: rob at iris.washington.edu (Robert Casey) Date: Tue, 9 Feb 2010 09:28:01 -0800 Subject: [data-issues] [rdseed] pressure units in SEED files In-Reply-To: <4B718B4F.2020801@blacknest.gov.uk> References: <4B718B4F.2020801@blacknest.gov.uk> Message-ID: <0134F930-898D-4E9E-874F-EAA18BB82102@iris.washington.edu> Thanks for letting us know if this problem, Sheila. I am actually surprised that rdseed doesn't work well with this data. Chris (our developer), could you please look into this issue and let us know what you find? -Rob On Feb 9, 2010, at 8:20 AM, Sheila Peacock wrote: > Hello, > > We want to create SEED files of infrasound data, for which the > quantity is pressure rather than acceleration, velocity or > displacement. > "rdseed" seems to be unable to cope with SEED header information > (in blockette 34) that is not "M", "M/S" or "M/S**2". How should > we proceed? > > Regards, > Sheila Peacock > AWE Blacknest > _______________________________________________ > data-issues mailing list > data-issues at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/data-issues From rob at iris.washington.edu Tue Feb 9 09:34:39 2010 From: rob at iris.washington.edu (Robert Casey) Date: Tue, 9 Feb 2010 09:34:39 -0800 Subject: [data-issues] pressure units in SEED files In-Reply-To: <4B718B4F.2020801@blacknest.gov.uk> References: <4B718B4F.2020801@blacknest.gov.uk> Message-ID: Hi Sheila- Could you identify for us what the units are specifically? Just want to make sure we are talking about the same kind of pressure units. -Rob On Feb 9, 2010, at 8:20 AM, Sheila Peacock wrote: > Hello, > > We want to create SEED files of infrasound data, for which the > quantity is pressure rather than acceleration, velocity or > displacement. > "rdseed" seems to be unable to cope with SEED header information > (in blockette 34) that is not "M", "M/S" or "M/S**2". How should > we proceed? > > Regards, > Sheila Peacock > AWE Blacknest > _______________________________________________ > data-issues mailing list > data-issues at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/data-issues From tim at iris.washington.edu Tue Feb 9 14:38:57 2010 From: tim at iris.washington.edu (Tim Ahern) Date: Tue, 9 Feb 2010 14:38:57 -0800 Subject: [data-issues] pressure units in SEED files In-Reply-To: References: <4B718B4F.2020801@blacknest.gov.uk> Message-ID: <2A2F1988-4DC2-475F-BE96-BA5ED2A7ADBF@iris.washington.edu> Sheila If you can send us a sample SEED file it may help us. I have personally extracted data in pascals, and micropascals using rdseed in the past so there might be something else tripping up rdseed. Can you point us to a sample SEED file. Thanks Tim Program Manager, IRIS Data Management System IRIS DMC 1408 NE 45th Street #201 Seattle, WA 98105 (206)547-0393 x118 (206) 547-1093 FAX On Feb 9, 2010, at 9:34 AM, Robert Casey wrote: > > Hi Sheila- > > Could you identify for us what the units are specifically? Just want to make sure we are talking about the same kind of pressure units. > > -Rob > > On Feb 9, 2010, at 8:20 AM, Sheila Peacock wrote: > >> Hello, >> >> We want to create SEED files of infrasound data, for which the >> quantity is pressure rather than acceleration, velocity or displacement. >> "rdseed" seems to be unable to cope with SEED header information >> (in blockette 34) that is not "M", "M/S" or "M/S**2". How should >> we proceed? >> >> Regards, >> Sheila Peacock >> AWE Blacknest >> _______________________________________________ >> data-issues mailing list >> data-issues at iris.washington.edu >> http://www.iris.washington.edu/mailman/listinfo/data-issues > > _______________________________________________ > data-issues mailing list > data-issues at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/data-issues From sheila at blacknest.gov.uk Thu Feb 18 05:09:05 2010 From: sheila at blacknest.gov.uk (Sheila Peacock) Date: Thu, 18 Feb 2010 13:09:05 +0000 Subject: [data-issues] multiple segments from same station in SEED files Message-ID: <4B7D3BF1.1020202@blacknest.gov.uk> We are trying to develop software to write our data in SEED files when the time span includes either a gap in the data or a change of metadata (e.g. a change in seismometer gain or orientation). As far as I can see, there is no problem in principle with a SEED volume containing several segments of data from the same station/channel/location-code, but I have not been able to find an example yet of a SEED file containing more than one segment of data per channel. I did find one where there are two (overlapping) segments from the same channel distinguished only by the "data header/quality indicator" (p. 98 of manual) being "R" for one and "Q" for the other. Do list members know whether a SEED volume containing two or more segments of data from the same station/channel/ location-code/quality-indicator can be decoded by "rdseed" and other such programs, and would be acceptable to IRIS? I am assuming that repeats of Blockette 52 (for orientation changes), 53 (for pole-zero changes), and 58 (for channel sensitivity/gain changes) for each data segment would be the correct way to denote changes in the channel metadata, with items 22 and 23 of Blockette 52 holding the start- and end-dates of the metadata being in force. If not, then is the only way to track the metadata change to issue a whole new SEED volume at the time of the change? I also assume that it would be incorrect to use items 22 and 23 of Blockette 52 just to denote the edges of gaps in the data where there are no metadata changes, and that the start time in the "Fixed section of Data Header" (p. 98) should be used for that. Advice would be most welcome, as "digging" blindly for SEED files in the hope of finding one that shows what I'm looking for would be time-consuming. Thanks! Regards, Sheila Peacock Blacknest.