Hi Tim, hoping to have fully understand your questions these are my answers
1) yes 2) yes 3) yes, you have to organize tour data as miniseed seiscomp or BUD daily archives: they are not event oriented. 4) as regards seiscomp archives filenames must be such as: BO.BO01..S1E.D.2015.30 (network,station,channel,year,day of the year) Daily archives data must be put in directories like this (eg.DOS) L:\SEISMO\ARC\2015\BO\BO01\S1E.D (in this directory all the 2015 daily archives of network BO, station BO01, channel S1E.D, and so on) In SEISAN.DAT archives must be declared so (one channel ==> one line) # archive ARC_CHAN BO07 S1ZBO ARC_CHAN BO07 S1EBO ARC_CHAN BO07 S1NBO ARC_CHAN BO01 S1ZBO ARC_CHAN BO01 S1EBO ARC_CHAN BO01 S1NBO ARC_CHAN BO02 S1ZBO ARC_CHAN BO02 S1EBO ARC_CHAN BO02 S1NBO ARC_CHAN BO03 S1ZBO ARC_CHAN BO03 S1EBO ARC_CHAN BO03 S1NBO You can look continuously at archives data by using the command MULPLT==>ARC==>yyyymmdd. (notice that if you have a number of networks data declared as archives all the data of a particular time interval will be shown altogether). I generally save events waveforms by using out or outw commands and later record them in the database to be picked and located. Having archives dataset you can also use CONDET command to detect events automatically. -----Messaggio originale----- Da: [email protected] [mailto:[email protected]] Per conto di [email protected] Inviato: 29 July 2015 04:14 A: [email protected] Oggetto: seisan Digest, Vol 89, Issue 9 Today's Topics: 1. SEISAN, continuous waveforms (Sickbert, Tim) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jul 2015 01:07:15 +0000 From: "Sickbert, Tim" <[email protected]> Subject: [seisan] SEISAN, continuous waveforms To: "[email protected]" <[email protected]> Cc: "Yihun, Manahloh" <[email protected]>, "Abdel Salam, Mohamed" <[email protected]>, "Campbell, Nathan" <[email protected]> Greetings. We are working to set up an earthquake seismology research lab at Oklahoma State University. A brief inspection of available data showing a rapid increase in seismic activity in north-central Oklahoma since about 2009 would show our motivation (figure below). We have ten broadband triaxial seismographs (Guralp CMG-6TDs) rather densely deployed (long axis of the research area is about 100 km) in north-central Oklahoma. Our instruments are offline: they are logging data and we have to visit the stations to collect them. In addition we are using data from the USGS and Oklahoma Geological Survey (OGS) available through IRIS. Thus we want to analyze raw waveform data from about twenty seismic stations to locate, and analyze all earthquakes possible. We had been using Seismic Handler (SHM) to pick onsets and analyze events but we are not entirely satisfied with it. OGS and others have recommended SEISAN. I have worked through most of the tutorial with the embedded TEST data, and some of the training (seitrain.pdf) with the additional data. I very much like what SEISAN can do. The documentation, however, does not seem to me to directly address our application. Ideally, we want to simultaneously display fractions of 24-hour-long continuous waveform files from about twenty stations, zoom in on shorter time segments, pick onsets, locate and analyze events, determine magnitudes and maybe moment tensors, and save the appropriate S-files for cataloging and further analyses. I have been able to load individual miniSEED files into MULPLT. However, I have not yet been able to load more than one of our continuous waveform files at a time. My reading of "seisan.pdf," "seisan-tutorial.pdf," and "seatrain.pdf" lead me to think that I have to build BUD or SeisComP archives for SEISAN to access the data. The SEISAN documentation regarding these archives also seems to imply that they are event-oriented, unlike our situation where we want to manually, visually, perform the initial analyses of the continuous waveform files. Thus I have a few questions: 1) Is SEISAN appropriate for what we are trying to do? 2) Do the documents I have clearly present the information I need to set up the database(s) for our application? 3) Do I need to archive our data into BUD or SeisComP to be able to use it? 4) Do you have any other or additional recommendations on how we should manage our data to make it available to SEISAN (especially MULPLT)? Thanks! Tim [cid:[email protected]] Tim Sickbert Devon Labs Coordinator Boone Pickens School of Geology 105 Noble Research Center Oklahoma State University Stillwater OK 74078 (405) 744-6358 [email protected]<mailto:[email protected]> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/html Size: 9924 bytes Desc: not available URL: <http://mailman.uib.no/private/seisan/attachments/20150729/c6133372/attachment.txt> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 83832 bytes Desc: image003.png URL: <http://mailman.uib.no/private/seisan/attachments/20150729/c6133372/attachment.png> ---------------------------------------------------------------------- Send seisan mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mailman.uib.no/listinfo/seisan or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of seisan digest..." _______________________________________________ seisan mailing list [email protected] http://mailman.uib.no/listinfo/seisan End of seisan Digest, Vol 89, Issue 9 ************************************* eni spa Sede Legale Piazzale Enrico Mattei, 1 00144 Roma - Italia Capitale sociale euro 4.005.358.876,00 i.v. Codice Fiscale e Registro Imprese di Roma n. 00484960588 Partita IVA n. 00905811006 R.E.A. Roma n. 756453 Sedi secondarie: Via Emilia, 1 e Piazza Ezio Vanoni, 1 20097 San Donato Milanese (Milano) – Italia eni.com<http://www.eni.com> ________________________________ Message for the recipient only, if received in error, please notify the sender and read http://www.eni.com/disclaimer/ _______________________________________________ seisan mailing list [email protected] http://mailman.uib.no/listinfo/seisan
