andrius
this kind of problem is nearly always component and station name problem. also in this case. inside the gse file the statrion name is righ justified instead of left justified so only moving the station name one character left will fix the problem. this is probably a mistake in the sara software, seem to remeber this from before. but not so easy to fix. wavtool can change the station code but then data must be in seisan format. you can also edit the GSE file.
jens On Tue, 23 Jun 2015, Andrius Pacesa wrote:
Dear Seisan community, A few years ago Lithuanian Geological Survey purchased 5 unit of simple portative seismometers SARA SL-07 and 3 units of more sophisticated seismometers SARA SL-06. At that time we started using SARA SL-07 and were quite happy with this equipment. I created response file (SEISAN FAP format) and it worked quite ok. I attach files of LGS4 (SL-07)seismometer and corresponding response files which work fine (2015-05-29-0412-45S.LIT___003; LGS4_SH_E.2013-05-01-0000_SEI; LGS4_SH_N.2013-05-01-0000_SEI; LGS4_SH_Z.2013-05-01-0000_SEI). Now we want to start using portative seismometers SARA SL-06 too. This seismometer has installed web interface ?Seismonux?. I found the best way is to set it record in GSE 2.1 waveform format. Then I made response file for this device (GSE2 FAP format). I tried to get ground response view but received replay from mulplt ?No response info for LGS7 SH Z, etc.?. My first suspicion was related with different component naming in SARA SL-06 unit and response file. SARA SL-06 allows to use just 3 symbols for component name (SHZ, SHN, SHE) , while ?RESP? module requires 4 symbols for component naming (e.g. SH Z) and do not allow to use just 3 symbols. Inside the GSE waveform file and response file (GSE2 FAP format) station name and names of components looks slightly different e.g. ?LGS7 SHZ? in waveform file and ?LGS7 SHZ? inside response file. I attach files I am speaking about (2015-06-11-0602-19S.LGS7_003.GSE; LGS7_SH_E.2011-02-01-0000_GSE; LGS7_SH_Z.2011-02-01-0000_GSE). Then I got an idea I can use WAVETOOL module to covert waveform file from GSE to SEISAN and correct component naming. I used command like: wavetool ?wav_in_file 2015-06-11-0602-19S.LGS7_003GSE ?chandef wavetool_in_1.txt I got output waveform file wavetool_1_out.SEI. It was plotted with ?mulplt? but again I got replay ?No response info for LGS7 SH Z, etc.? while SEISAN FAP files were presented in my working directory and in CAL directory too. I made some change in channel definition file wavetool_in_2.txt but still got the same result. I attach channel definition files (wavetool_in_1.txt and wavetool_in_2.txt) and produced SEISAN files (wavetool_1.out_SEI and wavetool_1.out_SEI). It worth notice that inside the output SEISAN waveform files I found quite strange station and component names ?LGSSH Z7; LGSSH N7; LGSSH E7? while station name and components are depicted correctly on mulplt (LGS7 SHZ). Dear colleagues maybe some of you had similar problems and managed to tackle with them. Any response or suggestion will be more than welcome. All these trials I made on Windows 7 and SEISAN 10. I also have Linux installation of SEISAN. Maybe results on Linux could be different? Or maybe there is some kind of bug in the code? And one parallel question. Can GSE waveform file collaborate with response file written in SEISAN FAP or ZAP format, or it should be written just in GSE format? Best regards, Andrius Pacesa Seismologist Lithuanian Geological Survey
_______________________________________________ seisan mailing list [email protected] http://mailman.uib.no/listinfo/seisan
