Dear Halpaap, I tried everything in the RESP files, and it didn’t work. Subtly start working, then stop working. Sometimes it works; others not. It’s a trial and error until it works and stops working suddenly, even with the same seismic station that it worked on the event before. Did you observe or have reports of this weird behavior? I guess the problem is related to the system operating (Windows 7) or something that goes wrong with SEISAN installed on my computer. Could re-install SEISAN fix the problem?
Yours, João Fontiela ********************* ********************* João Fontiela, Ph.D skype: fontiela email: [email protected] mobile phone +351 917 862 830 Professional contacts: email: [email protected] Tel: (+351) 266 745 354 ext: 25413 Fax: (+351) 266 745 394 Professional address: Universidade de Évora Instituto de Ciências da Terra Colégio Luís Verney Rua Romão Ramalho, 59 7000-671 Évora - Portugal ResearchGate: https://www.researchgate.net/profile/Joao_Fontiela > No dia 19/01/2021, às 10:58, Felix Halpaap <[email protected]> escreveu: > > Hi João, > > is it possible that this may be due the issue described in the email below > (thread from last fall)? This should of course only be possible if the Seisan > installation that you use was updated. Then the RESP file now needs to > contain the correct network and location code that correspond to the data in > the filename AND in the RESP-file itself (this changed compared to before). > > If this cannot be the issue, could you send a waveform file and RESP file for > testing? > > Cheers, > Felix > > > -- > Felix Halpaap | Postdoctoral Research Fellow | Dep. of Earth Science | > University of Bergen > Allégaten 41, 5007 Bergen, Norway | [email protected] > <mailto:[email protected]> | +47 55 58 34 11 | Office 2B18c > >> El vie., 25 sept. 2020 a las 4:48, Jens Havskov (<[email protected] >> <mailto:[email protected]>>) escribió: >> >> there is a change is how to use RESP files. in manual it is explained >> as: >> >> The RESP lename must match the waveform data, so if the waveform data >> does not include network >> code and location code, then lename must be e.g.: RESP..BER..BHZ >> So if the location code in the waveform data is '{' then the RESP >> lename must include the '{', like e.g.: >> RESP.NO.BER.--.BHZ >> And if the location code in the waveform data is empty ' ' then the RESP >> lename must be like:RESP.DK.BSD..BHZ >> >> hope this helps >> >> jens >> >> Den 2020-09-25 06:36 skreiv Enrique Rodolfo Chon: >> > Hi Alejandra, >> > >> > I usually use SAC PZ files to remove instrument response (easily >> > retrievable from IRIS if the station is registered), so I can't speak >> > to >> > RESP formatting issues. >> > >> > Like Dr. Hidalgo suggested, I would check your file naming convention >> > and >> > ensure that the distributed SEISAN functions can recognize it. The >> > different conventions are in the manual. >> > >> > Also (probably not the problem), but make sure your bash or sh >> > profile(s) >> > are looking in the right place for instrument response files. If you >> > followed the manual, it would be in the CAL directory. >> > >> > An example naming scheme for one of my SAC PZ >> > files: ARHZ_S__N.2014-05-14-1106_SAC >> > >> > Best, >> > >> > Enrique >> > >> > On Thu, Sep 24, 2020 at 9:18 PM Alejandra Martínez <[email protected] >> > <mailto:[email protected]>> >> > wrote: >> > >> >> Hi guys! >> >> >> >> I'm updating SEISAN in my PC. Location processes works fine but, when >> >> I >> >> try to calculate the magnitude through SPEC, SEISAN doesn't find the >> >> correspondent RESP file. It is possible that you made changes in the >> >> accepted format? or it could be a configuration error? The RESP files >> >> are >> >> attached so you can check if the format is correct. >> >> >> >> I hope you can help me. >> >> >> >> Thank you in advance, >> >> >> >> Alejandra >> >> >> >> -- >> >> *Alejandra Martínez* >> >> *Ingeniero Geofísico * >> >> >> >> *+58 414 377 63 92* >> >> *Caracas, Venezuela* >> >> >> >> _______________________________________________ >> >> seisan mailing list >> >> [email protected] <mailto:[email protected]> >> >> https://mailman.uib.no/listinfo/seisan >> >> <https://mailman.uib.no/listinfo/seisan> >> >> > > > On 2021-01-19 11:40, João Fontiela wrote: >> Greetings, >> >> Last week, SEISAN was working fine however, yesterday, when I re-start >> SEISAN, it stops reading amplitudes. MULPLT on all component mode doesn’t >> find the RESP file (figure [problem read RESP], pick amplitudes on >> horizontal components were on Friday, and the vertical one was yesterday) >> but in single trace mode, it reads (see attached figures). Additionally, in >> a single trace mode window, amplitudes read in broadband stations are >> higher compared to the ones read on all component mode. On short period >> instruments amplitudes is fine. All of this is very strange, changes in >> behavior happen overnight. >> >> Anyone has a tip to fix this problem or had a sim<problem reading >> RESP.PNG>ilar problem? If I re-install SEISAN fix the problem? >> >> Any help is welcome. >> <Bug reading RESP_II.PNG> >> Yours, >> João Fontiela >> >> >> ********************* >> ********************* >> João Fontiela, Ph.D >> skype: fontiela >> email: [email protected] <mailto:[email protected]> >> mobile phone +351 917 862 830 >> >> Professional contacts: >> email: [email protected] <mailto:[email protected]> >> Tel: (+351) 266 745 354 ext: 25413 >> Fax: (+351) 266 745 394 >> >> Professional address: >> Universidade de Évora >> Instituto de Ciências da Terra >> Colégio Luís Verney >> Rua Romão Ramalho, 59 >> 7000-671 Évora - Portugal >> >> ResearchGate: https://www.researchgate.net/profile/Joao_Fontiela >> <https://www.researchgate.net/profile/Joao_Fontiela> >> >> >> >> _______________________________________________ >> seisan mailing list >> [email protected] <mailto:[email protected]> >> https://mailman.uib.no/listinfo/seisan >> <https://mailman.uib.no/listinfo/seisan>
_______________________________________________ seisan mailing list [email protected] https://mailman.uib.no/listinfo/seisan
