Test of SeedLink/Seiscomp v2.1 ############################## Software and manual downloaded from www.gfz-potsdam.de/seisc SeiscomP is the collection of programs; clients like (Slinktool, slarchive, slqPlot) and the server program Seedlink. Installing the Seedlink server was fast and easy. It is described in the Seiscomp 2.1 manual. So read the manual first. Note! Manual says it is the same whitch user to install with. This is not true. Install it with a user called sysop, using other user name the 24hour gif image traces will not work. Part of software have hard coded user sysop. My system ######### An 3ch Earth Data digitizer, 100SPS is connected to Com1. A geophon connected to ch1. Ch2 and ch3 unconnected. You goes through some questions regarding how you want it installed. Some of the setup questions Digiserver (for triggering): yes Stream preoccessing scheme : edata_100 Data port: /dev/ttyS0 Somehow I did not get setup to work with 19200 baud, so I used 38400 baud instead that worked. Received bad mod header; the log reported. (Seedlink to slow?) Triggered HH stream: yes Install permanent slqplot daemon for GIF-file creation: yes The SOM (Station Operation Manager) is started up automaticaly, but I do not see the menu in console. If you do a: ssh sysop@localhost enter password. Then the menu shows up. Stream proccessing schema ######################### This was the tricky part of the setup. You have to setup the streams.xml file (page 29 in manual) Say your ADC record at 100 SPS. Then you can define streams at 100,50,25.. SPS. Program remove samples. This can be useful if there is a bad communication link. In streams.xml you set up whitch streams are available (number of channels and different SPS rate). There are some conventions defined: HH = 100 SPS SH = 50 SPS BH = 25 SPS LH = 12.5 SPS VH so HHZ is Z (vertical) component of 100SPS Note: the entry point of my setup was edata_100 (defined earlier). I made my own generic_3x100 (copying a lot from generic_6x100) For testing without GPS lock ############################# In /config/plugins.ini set pctime=1 for testing. Triggers ######## The trigger algoritme uses Pyhton language. I first installed SeedLink on Linux distribution Fedora Core 1. Here there was a error messages in the interaction between Python and Seedlink. I did not investigated this further, instead I installed Suse Linux 9.2 on the PC. Now there are no Python error messages. The triggers are detected (see it in seedlink log file) but not written to the trigger directory. slqplot (ploting trace) ######################## Is poorly documented. So I have not beeing able to used it. Have been able to plot traces from other stations using A Lomax's SeisGram2K, but it would not plot data from my Seedlink server. Unresolved issue. The visible evidence that my system is recording is the gif images. (Helicorder emulation). Shaking sensor are seen on gif images. slarchive ########## Save continuous data in a SDS file structur (seed apendix A of manual). Default ringbuffer of 50 days. It is one of the questions in the installation. Nice possibility, SeedLink can read SeisAn file structures and stream it to internet. So others can receive data by connecting to SeedLink. José 22/2-2005