From mplasencia at ogs.trieste.it Wed Feb 2 07:05:35 2011 From: mplasencia at ogs.trieste.it (Milton P. Plasencia Linares) Date: Wed, 02 Feb 2011 16:05:35 +0100 Subject: [SAC-HELP] Spectrogram save files Message-ID: <20110202160535.93181msu6djxyvun@webmail.ogs.trieste.it> Hi, I try the spectrogram commands OK, i want save the plot in files postscript or another format, how i can accomplish this?. Regards, Milton ********************************** Milton P. PLASENCIA LINARES Dipartimento Centro di Ricerche Sismologiche Istituto Nazionale di Oceanografia e di Geofisica Sperimentale - OGS Borgo Grotta Gigante 42/C (34010) Sgonico - TRIESTE - ITALIA Tel: +39-040-2140136 Fax: +39-040-327307 E-mail: mplasencia at ogs.trieste.it ASAIN (Antarctic Seismographic Argentinean Italian Network) ********************************* ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From mplasencia at ogs.trieste.it Wed Feb 2 10:24:33 2011 From: mplasencia at ogs.trieste.it (Milton P. Plasencia Linares) Date: Wed, 02 Feb 2011 19:24:33 +0100 Subject: [SAC-HELP] spectrogram save files Message-ID: <20110202192433.87755kz6a22exy75@webmail.ogs.trieste.it> Thanks to all, I used year ago this command and did not remember to use, Ray pointed me in the correct direction. Cheers, M ********************************** Milton P. PLASENCIA LINARES Dipartimento Centro di Ricerche Sismologiche Istituto Nazionale di Oceanografia e di Geofisica Sperimentale - OGS Borgo Grotta Gigante 42/C (34010) Sgonico - TRIESTE - ITALIA Tel: +39-040-2140136 Fax: +39-040-327307 E-mail: mplasencia at ogs.trieste.it ASAIN (Antarctic Seismographic Argentinean Italian Network) ********************************* ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From cpzeiler at miners.utep.edu Wed Feb 2 19:57:07 2011 From: cpzeiler at miners.utep.edu (cpzeiler at miners.utep.edu) Date: Wed, 2 Feb 2011 20:57:07 -0700 Subject: [SAC-HELP] Picking error help in SAC... Message-ID: I am petitioning the help of SAC users to understand pick error. The intial phase of the project is to compare unfiltered events picked by different users. While this is more a test of the users ability to pick seismograms, at a later time we will incorporate other software and determine if there is a bias in the methodologies of establishing picks made by different software, along with algorithms used to process the events with in a software package. We first need to establish a base line and I encourage all that have 20-40 minutes to pick the intial data set. Please contact me at cpzeiler at miners.utep.edu to recieve the SAC waveforms and feel free to visit the project page at http://www.geo.utep.edu/pub/zeiler/SPEAR.html. Thank you for your consideration and contributing to the seismological community, Dr. Cleat Zeiler cpzeiler at miners.utep.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From beabria at gmail.com Sat Feb 5 12:22:39 2011 From: beabria at gmail.com (Aubreya Adams) Date: Sat, 5 Feb 2011 14:22:39 -0600 Subject: [SAC-HELP] Sac i/o problem with fortran Message-ID: <2440967F-E3B8-4261-A3C2-16ECFC3CF3F3@gmail.com> Hello, I have recently upgrade from a PowerPC to an Intel Mac (10.6.6) and am trying to recompile some fortran codes that call upon sac i/o functions. When I try to compile the codes, I get following warning about the sac library and resulting errors: ld: warning: in /usr/bin/sac/lib/sacio.a, file was built for unsupported file format which is not the architecture being linked (i386) Undefined symbols: "_getfhv_", referenced from: _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o "_rsac1_", referenced from: _MAIN__ in cc7sScyY.o ld: symbol(s) not found collect2: ld returned 1 exit status In all other aspects, sac seems to be working fine on my new computer. Do any of you have insights into how I might address this problem? Thank you, Aubreya Adams -------------- next part -------------- An HTML attachment was scrubbed... URL: From snoke at vt.edu Sat Feb 5 12:56:47 2011 From: snoke at vt.edu (Arthur Snoke) Date: Sat, 5 Feb 2011 15:56:47 -0500 (EST) Subject: [SAC-HELP] Sac i/o problem with fortran In-Reply-To: <2440967F-E3B8-4261-A3C2-16ECFC3CF3F3@gmail.com> References: <2440967F-E3B8-4261-A3C2-16ECFC3CF3F3@gmail.com> Message-ID: The gcc in OS 10.6 has a default of 64 bits, in contrast with the 32 bit default for earlier Mac OS. Hence, when we released 101.4, we provided two Mac binaries, one a "fat" binary that works on PPC and i386 macs but is 32 bit so has compatibility problems on 10.6, and one that is built on 10.6 but not downward compatible. If you build SAC from sources on 10.6, it will interface with the 64 bit gcc -- and Fortran routines that are native 64 bits or have been built with the -m64 compiler option. I recently upgraded my gfortran from a 2009 version that had a default -m32 to one that has the -m64 default. On Sat, 5 Feb 2011, Aubreya Adams wrote: > Hello,I have recently upgrade from a PowerPC to an Intel Mac (10.6.6) > and am trying to recompile some fortran codes that call upon sac i/o > functions. ?When I try to compile the codes, I get following warning > about the sac library and resulting errors: ld: warning: in > /usr/bin/sac/lib/sacio.a, file was built for unsupported file format > which is not the architecture being linked (i386) Undefined symbols: > ??"_getfhv_", referenced from: ????_MAIN__ in cc7sScyY.o ????_MAIN__ in > cc7sScyY.o ????_MAIN__ in cc7sScyY.o ????_MAIN__ in cc7sScyY.o > ?_MAIN__ in cc7sScyY.o ????_MAIN__ in cc7sScyY.o ??"_rsac1_", referenced > from: ????_MAIN__ in cc7sScyY.o ld: symbol(s) not found collect2: ld > returned 1 exit status In all other aspects, sac seems to be working > fine on my new computer. ?Do any of you have insights into how I might > address this problem? Thank you, Aubreya Adams > > From beabria at gmail.com Sat Feb 5 16:42:48 2011 From: beabria at gmail.com (Aubreya Adams) Date: Sat, 5 Feb 2011 18:42:48 -0600 Subject: [SAC-HELP] Sac i/o problem with fortran In-Reply-To: References: <2440967F-E3B8-4261-A3C2-16ECFC3CF3F3@gmail.com> Message-ID: As you advised, I downloaded a compiler with the -m64 default, and that resolved the problem. Thank you for your help! On Feb 5, 2011, at 2:56 PM, Arthur Snoke wrote: > The gcc in OS 10.6 has a default of 64 bits, in contrast with the 32 bit default for earlier Mac OS. Hence, when we released 101.4, we provided two Mac binaries, one a "fat" binary that works on PPC and i386 macs but is 32 bit so has compatibility problems on 10.6, and one that is built on 10.6 but not downward compatible. If you build SAC from sources on 10.6, it will interface with the 64 bit gcc -- and Fortran routines that are native 64 bits or have been built with the -m64 compiler option. I recently upgraded my gfortran from a 2009 version that had a default -m32 to one that has the -m64 default. > > > On Sat, 5 Feb 2011, Aubreya Adams wrote: > >> Hello,I have recently upgrade from a PowerPC to an Intel Mac (10.6.6) and am trying to recompile some fortran codes that call upon sac i/o functions. When I try to compile the codes, I get following warning about the sac library and resulting errors: ld: warning: in /usr/bin/sac/lib/sacio.a, file was built for unsupported file format which is not the architecture being linked (i386) Undefined symbols: >> "_getfhv_", referenced from: _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o >> _MAIN__ in cc7sScyY.o _MAIN__ in cc7sScyY.o "_rsac1_", referenced from: _MAIN__ in cc7sScyY.o ld: symbol(s) not found collect2: ld returned 1 exit status In all other aspects, sac seems to be working fine on my new computer. Do any of you have insights into how I might address this problem? Thank you, Aubreya Adams >> From vkarpinsky at mail.ru Tue Feb 8 02:21:58 2011 From: vkarpinsky at mail.ru (Vladimir Karpinsky) Date: Tue, 08 Feb 2011 13:21:58 +0300 Subject: [SAC-HELP] read_css again-2 Message-ID: <4D511946.8070009@mail.ru> Hello, I am sorry to inform you, that I have trouble with reading CSS 3.0 files again. There are no errors while reading data, but data are reading incorrectly. Here: http://geo.phys.spbu.ru/~karp/sac_css/ I put 3 files with data and plots obtained by SAC and WSG. I see difference between data types in my wfdisc file and wfdisc file that create writecss: we use s4 (SUN IEEE integer), writecss create t4 (SUN IEEE single precision real). Help of readcss says that s4 is also supported by SAC, may be I have specify type of data manually or there is another way to convert s4 to t4. -- Best regards, Vladimir. From reza.emamy at gmail.com Sun Feb 13 10:30:58 2011 From: reza.emamy at gmail.com (Reza Emami) Date: Sun, 13 Feb 2011 22:00:58 +0330 Subject: [SAC-HELP] post to sac_help list Message-ID: reza.emamy at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From warrenc at stanford.edu Mon Feb 14 16:05:59 2011 From: warrenc at stanford.edu (Warren Caldwell) Date: Mon, 14 Feb 2011 16:05:59 -0800 Subject: [SAC-HELP] bug fix in readsac.m (missing fclose) Message-ID: Hi all, I believe I've found a bug (unbalanced fopen/fclose) in readsac.m. When I read in a large number of sac files in Matlab using F=readsac(* list-of-files-tens-**long*), Matlab hangs and crashes. I fixed it in sac-101.2/utils/readsac.m by adding an fclose statement as follows: Original (first line is line 243): if ~ismember(B(7), 1:6) % non-native byte order [comp, mxsize, endian] = computer; Changed: if ~ismember(B(7), 1:6) % non-native byte order *fclose(fid);* % close original 'fid' since we are about to create a new 'fid' [comp, mxsize, endian] = computer; Without this fclose, Matlab opens each file without closing the previous one. I had to make the same change in sac-101.4/utils/readsac.m. Cheers, Warren -- ~~~~~~~~~~~~~~~~~~~~~~~~~ Warren Caldwell Stanford Geophysics pangea.stanford.edu/~warrenc -------------- next part -------------- An HTML attachment was scrubbed... URL: From nabelek at coas.oregonstate.edu Tue Feb 15 13:44:40 2011 From: nabelek at coas.oregonstate.edu (Nabelek John) Date: Tue, 15 Feb 2011 13:44:40 -0800 Subject: [SAC-HELP] missing sac_header.h file in sac sac-101.4 In-Reply-To: References: Message-ID: <833D4187-8FDE-45CE-A2D5-A91939B0AE17@coas.oregonstate.edu> Hi I am trying to compile sac 101.4 in order to link some external programs against the current sac libraries. I have a problem with sac-101.4/src/coda/sac_code.c, which requires sac_header.h. This header file does not exist in my source distribution and thus sac_code.c does not compile, which in turn results in 'Undefined symbols: "_initialize_header"' error when I compile my codes. Is there someone who has the sac_header.h file and can you forward it to me? Thanks. -John From savage at uri.edu Wed Feb 16 07:18:17 2011 From: savage at uri.edu (Brian Savage) Date: Wed, 16 Feb 2011 10:18:17 -0500 Subject: [SAC-HELP] bug fix in readsac.m (missing fclose) In-Reply-To: References: Message-ID: <3A4A543F-A23E-471F-B53C-0BEE9FEDB05C@uri.edu> Warren, Thank you for the fix. We will be including this in the upcoming 101.5 version. Brian Savage savage at uri.edu On Feb 14, 2011, at 7:05 PM , Warren Caldwell wrote: > Hi all, > > I believe I've found a bug (unbalanced fopen/fclose) in readsac.m. > > When I read in a large number of sac files in Matlab using > F=readsac(list-of-files-tens-long), Matlab hangs and crashes. I > fixed it in sac-101.2/utils/readsac.m by adding an fclose statement > as follows: > > Original (first line is line 243): > if ~ismember(B(7), 1:6) % non-native byte order > [comp, mxsize, endian] = computer; > > Changed: > if ~ismember(B(7), 1:6) % non-native byte order > fclose(fid); % close original 'fid' since we are about to > create a new 'fid' > [comp, mxsize, endian] = computer; > > Without this fclose, Matlab opens each file without closing the > previous one. I had to make the same change in sac-101.4/utils/ > readsac.m. > > > Cheers, > Warren > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~ > Warren Caldwell > Stanford Geophysics > pangea.stanford.edu/~warrenc > > _______________________________________________ > sac-help mailing list > sac-help at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/sac-help From savage at uri.edu Thu Feb 17 07:35:47 2011 From: savage at uri.edu (Brian Savage) Date: Thu, 17 Feb 2011 10:35:47 -0500 Subject: [SAC-HELP] missing sac_header.h file in sac sac-101.4 In-Reply-To: <833D4187-8FDE-45CE-A2D5-A91939B0AE17@coas.oregonstate.edu> References: <833D4187-8FDE-45CE-A2D5-A91939B0AE17@coas.oregonstate.edu> Message-ID: <20A43B85-134C-43A5-904A-7796EBE4C48A@uri.edu> All, This problem below has been resolved following discussion between myself and John. The sac_code.c file is not compiled into the sac libraries or executable and should not be as it includes older and possibly buggy copies of SAC reading and writing routines. It is an older file that will be removed in the next version to avoid confusion. John, thank you. Brian On Feb 15, 2011, at 4:44 PM, Nabelek John wrote: > Hi > > I am trying to compile sac 101.4 in order to link some external > programs against the current sac libraries. > > I have a problem with sac-101.4/src/coda/sac_code.c, which requires > sac_header.h. This header file does not exist in my source > distribution and thus sac_code.c does not compile, which in turn > results in 'Undefined symbols: "_initialize_header"' error when I > compile my codes. > > Is there someone who has the sac_header.h file and can you forward > it to me? > > Thanks. > > -John > _______________________________________________ > sac-help mailing list > sac-help at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/sac-help > From f.darbyshire at gmail.com Thu Feb 17 07:50:48 2011 From: f.darbyshire at gmail.com (Fiona Darbyshire) Date: Thu, 17 Feb 2011 10:50:48 -0500 Subject: [SAC-HELP] SAC macro for power-spectral-density (noise) plots for seismograph stations Message-ID: Hello, Several years ago, I tried making power-spectral-density plots for noise characteristics of temporary seismograph stations, but it's been many years since I did this, and I have forgotten the details. One of my colleagues just sent me a copy of my original macro to ask me about it, and I find myself second-guessing myself as to whether I did it right originally. Here's the relevant section of the macro and my query: cut 0 1000 r 2011.038.17.00.00.0000.CN.YUK1..HHZ.D.SAC cut off transfer from polezero subtype yuk1.pz to none freqlim 0.005 0.006 40 45 dft divomega keepam xlim 0.01 50 div 27.38613 sqr add 1e-12 log10 mul 10 loglin p2 When I look more closely at the TRANSFER documentation, I see that if I transfer to NONE, the result should be a displacement seismogram. But the divomega in the frequency domain is an integration, so presumably I was thinking of converting from velocity to displacement there... does that mean I've effectively integrated twice? (I also can't remember what the division by 27.3 was for, though my suspicion is that it was some kind of normalisation...) If anyone can advise me on this, or anyone has a better SAC macro for PSD that they're willing to share, please let me know! Thanks very much, Fiona Darbyshire Universit? du Qu?bec ? Montr?al From yannik.behr at vuw.ac.nz Wed Feb 23 17:40:12 2011 From: yannik.behr at vuw.ac.nz (Yannik Behr) Date: Thu, 24 Feb 2011 14:40:12 +1300 Subject: [SAC-HELP] differences in instrument response Message-ID: <4D65B6FC.1080902@vuw.ac.nz> Hi, I am removing the instrument response first using a pole-zero file (SAC format) and then a RESP file (both extracted from the same DatalessSEED volume). The resulting traces show a phase shift of around 0.5 s. Is there anything wrong with the way I'm correcting for the instrument response? I have attached the script that I used to test this. Best, Yannik -- Yannik Behr PhD Student in Seismology School of Geography, Environment, and Earth Sciences Victoria University of Wellington P.O. Box 600 Wellington 6015 New Zealand yannik.behr at vuw.ac.nz ph. +64 (4) 463 5233 8369 fax.+64 (4) 463 5186 -------------- next part -------------- A non-text attachment was scrubbed... Name: check_response.sh Type: application/x-sh Size: 1071 bytes Desc: not available URL: From mplasencia at ogs.trieste.it Wed Feb 23 20:26:16 2011 From: mplasencia at ogs.trieste.it (Milton P. Plasencia Linares) Date: Thu, 24 Feb 2011 05:26:16 +0100 Subject: [SAC-HELP] differences in instrument response In-Reply-To: <4D65B6FC.1080902@vuw.ac.nz> References: <4D65B6FC.1080902@vuw.ac.nz> Message-ID: <20110224052616.17666xgxj28jirc8@webmail.ogs.trieste.it> Hi Yannik, Please, take into account the Correction time delay in the Response file, milton at macton:Downloads $ cat RESP.NZ.CRLZ.10.HHZ | grep Correction B057F08 Correction applied (seconds): 0.000000E+00 B057F08 Correction applied (seconds): 6.234400E-03 B057F08 Correction applied (seconds): 3.975000E-02 B057F08 Correction applied (seconds): 1.187500E-01 B057F08 Correction applied (seconds): 2.375000E-01 the total delay is: 4.0223438e-01 s I wait this help you, Milton ********************************** Milton P. PLASENCIA LINARES Dipartimento Centro di Ricerche Sismologiche Istituto Nazionale di Oceanografia e di Geofisica Sperimentale - OGS Borgo Grotta Gigante 42/C (34010) Sgonico - TRIESTE - ITALIA Tel: +39-040-2140136 Fax: +39-040-327307 E-mail: mplasencia at ogs.trieste.it ASAIN (Antarctic Seismographic Argentinean Italian Network) ********************************* Quoting "Yannik Behr" : > Hi, > > I am removing the instrument response first using a pole-zero file (SAC > format) and then a RESP file (both extracted from the same DatalessSEED > volume). The resulting traces show a phase shift of around 0.5 s. Is > there anything wrong with the way I'm correcting for the instrument > response? I have attached the script that I used to test this. > > Best, > Yannik > > > -- > Yannik Behr > PhD Student in Seismology > School of Geography, Environment, and Earth Sciences > Victoria University of Wellington > P.O. Box 600 > Wellington 6015 > New Zealand > > yannik.behr at vuw.ac.nz > > ph. +64 (4) 463 5233 8369 > fax.+64 (4) 463 5186 > > -- > This email was Anti Virus checked by INOGS Antivirus filter. > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.