From alireza.alinaghi at gmail.com Thu Dec 1 05:40:50 2011 From: alireza.alinaghi at gmail.com (Alireza Alinaghi) Date: Thu, 1 Dec 2011 14:40:50 +0100 Subject: [SAC-HELP] Cannot read css files with new version sac 101.5 Message-ID: Dear Colleagues and Friends: With the new version of SAC 101.5, I have problems reading CSS files. I get the following error: *SAC> readcss 1523.wfdisc* *No wfdisc file(s) found in the specified directory* * ERROR 1301: No data files read in.* I must add that with the old versions of SAC I did not have this problem. Is this a bug? Thank you in advance. Alireza -------------- next part -------------- An HTML attachment was scrubbed... URL: From kadmiel at bgu.ac.il Wed Dec 14 11:05:21 2011 From: kadmiel at bgu.ac.il (Shahar Shani-Kadmiel) Date: Wed, 14 Dec 2011 11:05:21 -0800 Subject: [SAC-HELP] Error message in terminal using MacSAC on 10.7.2 Message-ID: <0EEE92DE-E4E3-4FC2-90C3-E143D701C86A@bgu.ac.il> Hi, I get these error messages in the terminal while using SAC: gd4[17290] : kCGErrorInvalidConnection: CGSGetWindowTags: Invalid connection gd4[17290] : kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. I'm using Version 10.6f-grh107 on OS X 10.7.2 Shahar From carltape at gi.alaska.edu Wed Dec 21 18:37:25 2011 From: carltape at gi.alaska.edu (Carl Tape) Date: Wed, 21 Dec 2011 17:37:25 -0900 Subject: [SAC-HELP] glibc detected (when trying to get polezeros using rdseed) Message-ID: Dear SAC-help: I just downloaded rdseedv5.1 and tried to extract waveforms, response, and PZ files for a file from IRIS. I got the error and behavior mentioned below by Anne Deschamps. I have sac 101.5 installed (though the pre-release version), with linux opensuse 11.3, 64-bit. I do know that it only happens if you ask to produce polezero files -- for waveforms or response files, no error. The exit looks like this: ... Writing IU.YSS.00.LHZ, 3600 samples (binary), starting 2004,361 00:55:50.7856 UT *** glibc detected *** rdseed: free(): invalid pointer: 0x000000000043b845 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x73286)[0x7f10ed8d3286] /lib64/libc.so.6(cfree+0x6c)[0x7f10ed8d802c] rdseed[0x42a55b] ... It sounded like I should not expect to see this with the latest version of sac. Thanks, Carl Tape ---------- Forwarded message ---------- From: Date: Wed, Sep 7, 2011 at 10:46 AM Subject: sac-help Digest, Vol 72, Issue 2 To: sac-help at iris.washington.edu ---------------------------------------------------------------------- Message: 1 Date: Fri, 2 Sep 2011 15:24:35 -0400 From: Brian Savage Subject: Re: [SAC-HELP] compiling sac_v101.3 on linux suse 64bits To: SAC HELP Cc: Anne Deschamps Message-ID: <65AEA0A5-FEAF-407E-B2A3-1CF0C693E2A2 at uri.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Anne, I would suggest getting version 101.4. The getline issue was fixed in this version. The message you reported comes from the glibc and is indicating a minor error in the program. These kinds of messages have shown up before and should be fixed. See http://www.iris.washington.edu/pipermail/sac-help/2009-August/000593.html on how to make the message go away. If you still see this message when using 101.4, I would like to know the set of commands you issue before exiting the program so this problem can be fixed. Brian Savage savage at uri.edu On Sep 1, 2011, at 1:56 PM, Anne Deschamps wrote: > Hi > > when we use the compile linux version (64bits) all is OK except that > at the end, when we leave the programm we have this error message > > *** glibc detected *** sac: free(): invalid next size (fast): > 0x00000000009fc570 *** > ======= Backtrace: ========= > /lib64/libc.so.6(+0x75018)[0x7fb05e59c018] > /lib64/libc.so.6(cfree+0x6c)[0x7fb05e5a0fec] > sac[0x5b27dd] > sac[0x5b2cd9] > sac[0x5a33c0] > sac[0x40dacf] > sac[0x43cf72] > sac[0x4128c3] > sac[0x40b1b0] > sac[0x40555c] > /lib64/libc.so.6(__libc_start_main+0xe6)[0x7fb05e545bc6] > sac[0x404efa] > ======= Memory map: ======== > 00400000-00604000 r-xp 00000000 00:14 1084254 /usr/local/soft_sismo/ > sac/sac_v101.3/bin/sac > 00703000-0072a000 rw-p 00203000 00:14 1084254 /usr/local/soft_sismo/ > sac/sac_v101.3/bin/sac > 0072a000-00a2b000 rw-p 00000000 00:00 0 [heap] > 7fb058000000-7fb058021000 rw-p 00000000 00:00 0 > 7fb058021000-7fb05c000000 ---p 00000000 00:00 0 > 7fb05d2c1000-7fb05d2d7000 r-xp 00000000 08:03 3244152 /lib64/ > libgcc_s.so.1 > 7fb05d2d7000-7fb05d4d6000 ---p 00016000 08:03 3244152 /lib64/ > libgcc_s.so.1 > 7fb05d4d6000-7fb05d4d7000 r--p 00015000 08:03 3244152 /lib64/ > libgcc_s.so.1 > 7fb05d4d7000-7fb05d4d8000 rw-p 00016000 08:03 3244152 /lib64/ > libgcc_s.so.1 > 7fb05d4d8000-7fb05d4dd000 r-xp 00000000 08:03 2859135 /usr/lib64/ > libXfixes.so.3.1.0 > 7fb05d4dd000-7fb05d6dc000 ---p 00005000 08:03 2859135 /usr/lib64/ > libXfixes.so.3.1.0 > 7fb05d6dc000-7fb05d6dd000 r--p 00004000 08:03 2859135 /usr/lib64/ > libXfixes.so.3.1.0 > 7fb05d6dd000-7fb05d6de000 rw-p 00005000 08:03 2859135 /usr/lib64/ > libXfixes.so.3.1.0 > 7fb05d6de000-7fb05d6e7000 r-xp 00000000 08:03 2859133 /usr/lib64/ > libXrender.so.1.3.0 > 7fb05d6e7000-7fb05d8e6000 ---p 00009000 08:03 2859133 /usr/lib64/ > libXrender.so.1.3.0 > 7fb05d8e6000-7fb05d8e7000 r--p 00008000 08:03 2859133 /usr/lib64/ > libXrender.so.1.3.0 > 7fb05d8e7000-7fb05d8e8000 rw-p 00009000 08:03 2859133 /usr/lib64/ > libXrender.so.1.3.0 > 7fb05d8e8000-7fb05d8f2000 r-xp 00000000 08:03 2859279 /usr/lib64/ > libXcursor.so.1.0.2 > 7fb05d8f2000-7fb05daf1000 ---p 0000a000 08:03 2859279 /usr/lib64/ > libXcursor.so.1.0.2 > 7fb05daf1000-7fb05daf2000 r--p 00009000 08:03 2859279 /usr/lib64/ > libXcursor.so.1.0.2 > 7fb05daf2000-7fb05daf3000 rw-p 0000a000 08:03 2859279 /usr/lib64/ > libXcursor.so.1.0.2 > 7fb05daf3000-7fb05dafe000 r-xp 00000000 08:03 3244057 /lib64/ > libnss_files-2.11.1.so > 7fb05dafe000-7fb05dcfe000 ---p 0000b000 08:03 3244057 /lib64/ > libnss_files-2.11.1.so > 7fb05dcfe000-7fb05dcff000 r--p 0000b000 08:03 3244057 /lib64/ > libnss_files-2.11.1.so > 7fb05dcff000-7fb05dd00000 rw-p 0000c000 08:03 3244057 /lib64/ > libnss_files-2.11.1.so > 7fb05dd00000-7fb05dd02000 r-xp 00000000 08:03 3575339 /usr/lib64/ > libXau.so.6.0.0 > 7fb05dd02000-7fb05df02000 ---p 00002000 08:03 3575339 /usr/lib64/ > libXau.so.6.0.0 > 7fb05df02000-7fb05df03000 r--p 00002000 08:03 3575339 /usr/lib64/ > libXau.so.6.0.0 > 7fb05df03000-7fb05df04000 rw-p 00003000 08:03 3575339 /usr/lib64/ > libXau.so.6.0.0 > 7fb05df04000-7fb05df1f000 r-xp 00000000 08:03 3575639 /usr/lib64/ > libxcb.so.1.0.0 > 7fb05df1f000-7fb05e11e000 ---p 0001b000 08:03 3575639 /usr/lib64/ > libxcb.so.1.0.0 > 7fb05e11e000-7fb05e11f000 r--p 0001a000 08:03 3575639 /usr/lib64/ > libxcb.so.1.0.0 > 7fb05e11f000-7fb05e120000 rw-p 0001b000 08:03 3575639 /usr/lib64/ > libxcb.so.1.0.0 > 7fb05e120000-7fb05e121000 r-xp 00000000 08:03 3575629 /usr/lib64/ > libxcb-xlib.so.0.0.0 > 7fb05e121000-7fb05e320000 ---p 00001000 08:03 3575629 /usr/lib64/ > libxcb-xlib.so.0.0.0 > 7fb05e320000-7fb05e321000 r--p 00000000 08:03 3575629 /usr/lib64/ > libxcb-xlib.so.0.0.0 > 7fb05e321000-7fb05e322000 rw-p 00001000 08:03 3575629 /usr/lib64/ > libxcb-xlib.so.0.0.0 > 7fb05e322000-7fb05e326000 r-xp 00000000 08:03 3244146 /lib64/ > libuuid.so.1.3.0 > 7fb05e326000-7fb05e525000 ---p 00004000 08:03 3244146 /lib64/ > libuuid.so.1.3.0 > 7fb05e525000-7fb05e526000 r--p 00003000 08:03 3244146 /lib64/ > libuuid.so.1.3.0 > 7fb05e526000-7fb05e527000 rw-p 00004000 08:03 3244146 /lib64/ > libuuid.so.1.3.0 > 7fb05e527000-7fb05e67c000 r-xp 00000000 08:03 3244040 /lib64/ > libc-2.11.1.so > 7fb05e67c000-7fb05e87b000 ---p 00155000 08:03 3244040 /lib64/ > libc-2.11.1.so > 7fb05e87b000-7fb05e87f000 r--p 00154000 08:03 3244040 /lib64/ > libc-2.11.1.so > 7fb05e87f000-7fb05e880000 rw-p 00158000 08:03 3244040 /lib64/ > libc-2.11.1.so > 7fb05e880000-7fb05e885000 rw-p 00000000 00:00 0 > 7fb05e885000-7fb05e8c3000 r-xp 00000000 08:03 3244109 /lib64/ > libncurses.so.5.6 > 7fb05e8c3000-7fb05eac3000 ---p 0003e000 08:03 3244109 /lib64/ > libncurses.so.5.6 > 7fb05eac3000-7fb05eac7000 r--p 0003e000 08:03 3244109 /lib64/ > libncurses.so.5.6 > 7fb05eac7000-7fb05eacd000 rw-p 00042000 08:03 3244109 /lib64/ > libncurses.so.5.6 > 7fb05eacd000-7fb05eb22000 r-xp 00000000 08:03 3244048 /lib64/ > libm-2.11.1.so > 7fb05eb22000-7fb05ed21000 ---p 00055000 08:03 3244048 /lib64/ > libm-2.11.1.so > 7fb05ed21000-7fb05ed22000 r--p 00054000 08:03 3244048 /lib64/ > libm-2.11.1.so > 7fb05ed22000-7fb05ed23000 rw-p 00055000 08:03 3244048 /lib64/ > libm-2.11.1.so > 7fb05ed23000-7fb05ed25000 r-xp 00000000 08:03 3244046 /lib64/ > libdl-2.11.1.so > 7fb05ed25000-7fb05ef25000 ---p 00002000 08:03 3244046 /lib64/ > libdl-2.11.1.so > 7fb05ef25000-7fb05ef26000 r--p 00002000 08:03 3244046 /lib64/ > libdl-2.11.1.so > 7fb05ef26000-7fb05ef27000 rw-p 00003000 08:03 3244046 /lib64/ > libdl-2.11.1.so > 7fb05ef27000-7fb05f05e000 r-xp 00000000 08:03 2859042 /usr/lib64/ > libX11.so.6.2.0 > 7fb05f05e000-7fb05f25e000 ---p 00137000 08:03 2859042 /usr/lib64/ > libX11.so.6.2.0 > 7fb05f25e000-7fb05f25f000 r--p 00137000 08:03 2859042 /usr/lib64/ > libX11.so.6.2.0 > 7fb05f25f000-7fb05f264000 rw-p 00138000 08:03 2859042 /usr/lib64/ > libX11.so.6.2.0Abort > > So I would like to compile the source to see if it can be better > > When I do so, I have the error message > In file included from ../../sac-101.3b/src/bbs/setbbv.c:12: > ../../sac-101.3b/inc/co.h:40: error: conflicting types for 'getline' > /usr/include/stdio.h:653: error: previous declaration of 'getline' > was here > make[1]: *** [bbs/setbbv.o] Error 1 > make: *** [all-recursive] Error 1 > > Is that any solution to go head.... > > Thanks > > Anne > -- > Anne Deschamps > G?oazur/CNRS > B?t 3, 250 rue A. Einstein > 06560 Sophia Antipolis > tel: +33 4 92 94 26 16 > secr?tariat : +33 4 92 94 26 02 > _______________________________________________ > sac-help mailing list > sac-help at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/sac-help > -------------- next part -------------- An HTML attachment was scrubbed... URL: From snoke at vt.edu Wed Dec 21 19:44:41 2011 From: snoke at vt.edu (Arthur Snoke) Date: Wed, 21 Dec 2011 22:44:41 -0500 (EST) Subject: [SAC-HELP] glibc detected (when trying to get polezeros using rdseed) In-Reply-To: References: Message-ID: I have trouble following your discussion, but there are problems both with RDSEED v5.1 and with running the compiled SAC v 101.5 on Linux (64 and maybe 32 bit). You say you are using the pre-release version of SAC 101.5. Bugs were fixed between then and the "real" release. I do not work with Linux, but my impression is that Linux, unlike Sun and Mac, keep only the libraries for the current release. Hence, on Mac, a binary built on 10.6 will run on 10.7 (or a 10.4 build will run on 10.5) and on Sun a build on 2.8 will (probably) run on 2.9 or 2.10 because Mac and Sun keep the old libraries. If a Linux binary does not work on your machine, try building it from sources. There are problems with RDSEED v5.1 with polezero files (see the TRANSFER help file for the final SAC v101.5 release). On some systems the END time is something like 1991, so it will not find your files. I got around that by manually changing the END times. (One can concatinate all the pz files and do a global change or you can use sed.) There are also occasionally exceptions that bomb RDSEED in v5.1. v5.2 is about to come out or you can use v5.0 if these fixes do not help. From rob at iris.washington.edu Thu Dec 22 08:44:19 2011 From: rob at iris.washington.edu (Robert Casey) Date: Thu, 22 Dec 2011 08:44:19 -0800 Subject: [SAC-HELP] glibc detected (when trying to get polezeros using rdseed) In-Reply-To: References: Message-ID: Hi Carl- If the issue is with rdseed 5.1, then that is a problem that IRIS DMC has to address. Can you send us a copy/paste of the input text to rdseed that you used, so that we can reproduce the error? This will probably not get resolved until the first couple of weeks of January, since most of the DMC staff is out on holiday. If I get any ideas about what's wrong, though, I'll contact you. Thanks for letting us know about this issue. As Arthur indicated, we have a v5.2 coming out that has some bug fixes, but I am not certain that this issue has been examined or resolved, so it will be good for us to address this while we still have the release candidate on the workbench. Happy Holidays, -Rob On Dec 21, 2011, at 6:37 PM, Carl Tape wrote: > Dear SAC-help: > > I just downloaded rdseedv5.1 and tried to extract waveforms, > response, and PZ files for a file from IRIS. I got the error and > behavior mentioned below by Anne Deschamps. I have sac 101.5 > installed (though the pre-release version), with linux opensuse > 11.3, 64-bit. I do know that it only happens if you ask to produce > polezero files -- for waveforms or response files, no error. > > The exit looks like this: > > ... > Writing IU.YSS.00.LHZ, 3600 samples (binary), starting 2004,361 > 00:55:50.7856 UT > *** glibc detected *** rdseed: free(): invalid pointer: > 0x000000000043b845 *** > ======= Backtrace: ========= > /lib64/libc.so.6(+0x73286)[0x7f10ed8d3286] > /lib64/libc.so.6(cfree+0x6c)[0x7f10ed8d802c] > rdseed[0x42a55b] > ... > > It sounded like I should not expect to see this with the latest > version of sac. > > Thanks, > Carl Tape > > ---------- Forwarded message ---------- > From: > Date: Wed, Sep 7, 2011 at 10:46 AM > Subject: sac-help Digest, Vol 72, Issue 2 > To: sac-help at iris.washington.edu > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 Sep 2011 15:24:35 -0400 > From: Brian Savage > Subject: Re: [SAC-HELP] compiling sac_v101.3 on linux suse 64bits > To: SAC HELP > Cc: Anne Deschamps > Message-ID: <65AEA0A5-FEAF-407E-B2A3-1CF0C693E2A2 at uri.edu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > > Anne, > > I would suggest getting version 101.4. The getline issue was fixed in > this version. > > The message you reported comes from the glibc and is indicating a > minor error in the program. These kinds of messages have shown up > before and should be fixed. > > See > http://www.iris.washington.edu/pipermail/sac-help/2009-August/000593.html > on how to make the message go away. > > If you still see this message when using 101.4, I would like to know > the set of commands you issue before exiting the program so this > problem can be fixed. > > Brian Savage > savage at uri.edu > > On Sep 1, 2011, at 1:56 PM, Anne Deschamps wrote: > > > Hi > > > > when we use the compile linux version (64bits) all is OK except that > > at the end, when we leave the programm we have this error message > > > > *** glibc detected *** sac: free(): invalid next size (fast): > > 0x00000000009fc570 *** > > ======= Backtrace: ========= > > /lib64/libc.so.6(+0x75018)[0x7fb05e59c018] > > /lib64/libc.so.6(cfree+0x6c)[0x7fb05e5a0fec] > > sac[0x5b27dd] > > sac[0x5b2cd9] > > sac[0x5a33c0] > > sac[0x40dacf] > > sac[0x43cf72] > > sac[0x4128c3] > > sac[0x40b1b0] > > sac[0x40555c] > > /lib64/libc.so.6(__libc_start_main+0xe6)[0x7fb05e545bc6] > > sac[0x404efa] > > ======= Memory map: ======== > > 00400000-00604000 r-xp 00000000 00:14 1084254 /usr/local/ > soft_sismo/ > > sac/sac_v101.3/bin/sac > > 00703000-0072a000 rw-p 00203000 00:14 1084254 /usr/local/ > soft_sismo/ > > sac/sac_v101.3/bin/sac > > 0072a000-00a2b000 rw-p 00000000 00:00 0 [heap] > > 7fb058000000-7fb058021000 rw-p 00000000 00:00 0 > > 7fb058021000-7fb05c000000 ---p 00000000 00:00 0 > > 7fb05d2c1000-7fb05d2d7000 r-xp 00000000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d2d7000-7fb05d4d6000 ---p 00016000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d4d6000-7fb05d4d7000 r--p 00015000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d4d7000-7fb05d4d8000 rw-p 00016000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d4d8000-7fb05d4dd000 r-xp 00000000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d4dd000-7fb05d6dc000 ---p 00005000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d6dc000-7fb05d6dd000 r--p 00004000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d6dd000-7fb05d6de000 rw-p 00005000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d6de000-7fb05d6e7000 r-xp 00000000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d6e7000-7fb05d8e6000 ---p 00009000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d8e6000-7fb05d8e7000 r--p 00008000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d8e7000-7fb05d8e8000 rw-p 00009000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d8e8000-7fb05d8f2000 r-xp 00000000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05d8f2000-7fb05daf1000 ---p 0000a000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05daf1000-7fb05daf2000 r--p 00009000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05daf2000-7fb05daf3000 rw-p 0000a000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05daf3000-7fb05dafe000 r-xp 00000000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dafe000-7fb05dcfe000 ---p 0000b000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dcfe000-7fb05dcff000 r--p 0000b000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dcff000-7fb05dd00000 rw-p 0000c000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dd00000-7fb05dd02000 r-xp 00000000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05dd02000-7fb05df02000 ---p 00002000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05df02000-7fb05df03000 r--p 00002000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05df03000-7fb05df04000 rw-p 00003000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05df04000-7fb05df1f000 r-xp 00000000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05df1f000-7fb05e11e000 ---p 0001b000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05e11e000-7fb05e11f000 r--p 0001a000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05e11f000-7fb05e120000 rw-p 0001b000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05e120000-7fb05e121000 r-xp 00000000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e121000-7fb05e320000 ---p 00001000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e320000-7fb05e321000 r--p 00000000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e321000-7fb05e322000 rw-p 00001000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e322000-7fb05e326000 r-xp 00000000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e326000-7fb05e525000 ---p 00004000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e525000-7fb05e526000 r--p 00003000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e526000-7fb05e527000 rw-p 00004000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e527000-7fb05e67c000 r-xp 00000000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e67c000-7fb05e87b000 ---p 00155000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e87b000-7fb05e87f000 r--p 00154000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e87f000-7fb05e880000 rw-p 00158000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e880000-7fb05e885000 rw-p 00000000 00:00 0 > > 7fb05e885000-7fb05e8c3000 r-xp 00000000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05e8c3000-7fb05eac3000 ---p 0003e000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05eac3000-7fb05eac7000 r--p 0003e000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05eac7000-7fb05eacd000 rw-p 00042000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05eacd000-7fb05eb22000 r-xp 00000000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05eb22000-7fb05ed21000 ---p 00055000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05ed21000-7fb05ed22000 r--p 00054000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05ed22000-7fb05ed23000 rw-p 00055000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05ed23000-7fb05ed25000 r-xp 00000000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ed25000-7fb05ef25000 ---p 00002000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ef25000-7fb05ef26000 r--p 00002000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ef26000-7fb05ef27000 rw-p 00003000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ef27000-7fb05f05e000 r-xp 00000000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0 > > 7fb05f05e000-7fb05f25e000 ---p 00137000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0 > > 7fb05f25e000-7fb05f25f000 r--p 00137000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0 > > 7fb05f25f000-7fb05f264000 rw-p 00138000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0Abort > > > > So I would like to compile the source to see if it can be better > > > > When I do so, I have the error message > > In file included from ../../sac-101.3b/src/bbs/setbbv.c:12: > > ../../sac-101.3b/inc/co.h:40: error: conflicting types for 'getline' > > /usr/include/stdio.h:653: error: previous declaration of 'getline' > > was here > > make[1]: *** [bbs/setbbv.o] Error 1 > > make: *** [all-recursive] Error 1 > > > > Is that any solution to go head.... > > > > Thanks > > > > Anne > > -- > > Anne Deschamps > > G?oazur/CNRS > > B?t 3, 250 rue A. Einstein > > 06560 Sophia Antipolis > > tel: +33 4 92 94 26 16 > > secr?tariat : +33 4 92 94 26 02 > > _______________________________________________ > > sac-help mailing list > > sac-help at iris.washington.edu > > http://www.iris.washington.edu/mailman/listinfo/sac-help > > > > _______________________________________________ > sac-help mailing list > sac-help at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/sac-help -------------- next part -------------- An HTML attachment was scrubbed... URL: From carltape at gi.alaska.edu Thu Dec 22 10:59:49 2011 From: carltape at gi.alaska.edu (Carl Tape) Date: Thu, 22 Dec 2011 09:59:49 -0900 Subject: [SAC-HELP] glibc detected (when trying to get polezeros using rdseed) In-Reply-To: References:

Message-ID: Hi Arthur and Rob, Thanks for the replies. No need to address this now. First, I downloaded sac-101.5 and reproduced the problem I mentioned: the gclib exit error and message. My inputs into rdseedv5.1 are "d", "y" for polezeros, "3" to check all, "y" to extract response," and the rest defaults. If you do not request polezeros, there is no error message or exit. If you do request polezeros, there is an error message, but it appears that the files are generated (which is good!). (The exit might be an issue if you are running a script with multiple files.) I tried recompiling rdseed and did notice this warning (among others): cc -I../Include -O -m64 -c -o output_sac.o output_sac.c output_sac.c: In function ?output_sac?: output_sac.c:274: warning: assignment makes pointer from integer without a cast output_sac.c: In function ?write_out_PnZs?: output_sac.c:1521: warning: assignment makes pointer from integer without a cast Anyway, there is no urgency to this. I will try things out with rdseedv5.2 and can try out beta versions in the mean time, if you want. Enjoy the holidays. Today is 3 seconds longer than yesterday up here in Fairbanks, so the days are getting longer! Carl On Thu, Dec 22, 2011 at 7:44 AM, Robert Casey wrote: > > Hi Carl- > > If the issue is with rdseed 5.1, then that is a problem that IRIS DMC has > to address. Can you send us a copy/paste of the input text to rdseed that > you used, so that we can reproduce the error? This will probably not get > resolved until the first couple of weeks of January, since most of the DMC > staff is out on holiday. If I get any ideas about what's wrong, though, > I'll contact you. > > Thanks for letting us know about this issue. As Arthur indicated, we have > a v5.2 coming out that has some bug fixes, but I am not certain that this > issue has been examined or resolved, so it will be good for us to address > this while we still have the release candidate on the workbench. > > Happy Holidays, > > -Rob > > > On Dec 21, 2011, at 6:37 PM, Carl Tape wrote: > > Dear SAC-help: > > I just downloaded rdseedv5.1 and tried to extract waveforms, response, and > PZ files for a file from IRIS. I got the error and behavior mentioned below > by Anne Deschamps. I have sac 101.5 installed (though the pre-release > version), with linux opensuse 11.3, 64-bit. I do know that it only happens > if you ask to produce polezero files -- for waveforms or response files, no > error. > > The exit looks like this: > > ... > Writing IU.YSS.00.LHZ, 3600 samples (binary), starting 2004,361 > 00:55:50.7856 UT > *** glibc detected *** rdseed: free(): invalid pointer: 0x000000000043b845 > *** > ======= Backtrace: ========= > /lib64/libc.so.6(+0x73286)[0x7f10ed8d3286] > /lib64/libc.so.6(cfree+0x6c)[0x7f10ed8d802c] > rdseed[0x42a55b] > ... > > It sounded like I should not expect to see this with the latest version of > sac. > > Thanks, > Carl Tape > > ---------- Forwarded message ---------- > From: > Date: Wed, Sep 7, 2011 at 10:46 AM > Subject: sac-help Digest, Vol 72, Issue 2 > To: sac-help at iris.washington.edu > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 Sep 2011 15:24:35 -0400 > From: Brian Savage > Subject: Re: [SAC-HELP] compiling sac_v101.3 on linux suse 64bits > To: SAC HELP > Cc: Anne Deschamps > Message-ID: <65AEA0A5-FEAF-407E-B2A3-1CF0C693E2A2 at uri.edu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > > Anne, > > I would suggest getting version 101.4. The getline issue was fixed in > this version. > > The message you reported comes from the glibc and is indicating a > minor error in the program. These kinds of messages have shown up > before and should be fixed. > > See > http://www.iris.washington.edu/pipermail/sac-help/2009-August/000593.html > on how to make the message go away. > > If you still see this message when using 101.4, I would like to know > the set of commands you issue before exiting the program so this > problem can be fixed. > > Brian Savage > savage at uri.edu > > On Sep 1, 2011, at 1:56 PM, Anne Deschamps wrote: > > > Hi > > > > when we use the compile linux version (64bits) all is OK except that > > at the end, when we leave the programm we have this error message > > > > *** glibc detected *** sac: free(): invalid next size (fast): > > 0x00000000009fc570 *** > > ======= Backtrace: ========= > > /lib64/libc.so.6(+0x75018)[0x7fb05e59c018] > > /lib64/libc.so.6(cfree+0x6c)[0x7fb05e5a0fec] > > sac[0x5b27dd] > > sac[0x5b2cd9] > > sac[0x5a33c0] > > sac[0x40dacf] > > sac[0x43cf72] > > sac[0x4128c3] > > sac[0x40b1b0] > > sac[0x40555c] > > /lib64/libc.so.6(__libc_start_main+0xe6)[0x7fb05e545bc6] > > sac[0x404efa] > > ======= Memory map: ======== > > 00400000-00604000 r-xp 00000000 00:14 1084254 /usr/local/soft_sismo/ > > sac/sac_v101.3/bin/sac > > 00703000-0072a000 rw-p 00203000 00:14 1084254 /usr/local/soft_sismo/ > > sac/sac_v101.3/bin/sac > > 0072a000-00a2b000 rw-p 00000000 00:00 0 [heap] > > 7fb058000000-7fb058021000 rw-p 00000000 00:00 0 > > 7fb058021000-7fb05c000000 ---p 00000000 00:00 0 > > 7fb05d2c1000-7fb05d2d7000 r-xp 00000000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d2d7000-7fb05d4d6000 ---p 00016000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d4d6000-7fb05d4d7000 r--p 00015000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d4d7000-7fb05d4d8000 rw-p 00016000 08:03 3244152 /lib64/ > > libgcc_s.so.1 > > 7fb05d4d8000-7fb05d4dd000 r-xp 00000000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d4dd000-7fb05d6dc000 ---p 00005000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d6dc000-7fb05d6dd000 r--p 00004000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d6dd000-7fb05d6de000 rw-p 00005000 08:03 2859135 /usr/lib64/ > > libXfixes.so.3.1.0 > > 7fb05d6de000-7fb05d6e7000 r-xp 00000000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d6e7000-7fb05d8e6000 ---p 00009000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d8e6000-7fb05d8e7000 r--p 00008000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d8e7000-7fb05d8e8000 rw-p 00009000 08:03 2859133 /usr/lib64/ > > libXrender.so.1.3.0 > > 7fb05d8e8000-7fb05d8f2000 r-xp 00000000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05d8f2000-7fb05daf1000 ---p 0000a000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05daf1000-7fb05daf2000 r--p 00009000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05daf2000-7fb05daf3000 rw-p 0000a000 08:03 2859279 /usr/lib64/ > > libXcursor.so.1.0.2 > > 7fb05daf3000-7fb05dafe000 r-xp 00000000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dafe000-7fb05dcfe000 ---p 0000b000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dcfe000-7fb05dcff000 r--p 0000b000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dcff000-7fb05dd00000 rw-p 0000c000 08:03 3244057 /lib64/ > > libnss_files-2.11.1.so > > 7fb05dd00000-7fb05dd02000 r-xp 00000000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05dd02000-7fb05df02000 ---p 00002000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05df02000-7fb05df03000 r--p 00002000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05df03000-7fb05df04000 rw-p 00003000 08:03 3575339 /usr/lib64/ > > libXau.so.6.0.0 > > 7fb05df04000-7fb05df1f000 r-xp 00000000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05df1f000-7fb05e11e000 ---p 0001b000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05e11e000-7fb05e11f000 r--p 0001a000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05e11f000-7fb05e120000 rw-p 0001b000 08:03 3575639 /usr/lib64/ > > libxcb.so.1.0.0 > > 7fb05e120000-7fb05e121000 r-xp 00000000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e121000-7fb05e320000 ---p 00001000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e320000-7fb05e321000 r--p 00000000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e321000-7fb05e322000 rw-p 00001000 08:03 3575629 /usr/lib64/ > > libxcb-xlib.so.0.0.0 > > 7fb05e322000-7fb05e326000 r-xp 00000000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e326000-7fb05e525000 ---p 00004000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e525000-7fb05e526000 r--p 00003000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e526000-7fb05e527000 rw-p 00004000 08:03 3244146 /lib64/ > > libuuid.so.1.3.0 > > 7fb05e527000-7fb05e67c000 r-xp 00000000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e67c000-7fb05e87b000 ---p 00155000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e87b000-7fb05e87f000 r--p 00154000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e87f000-7fb05e880000 rw-p 00158000 08:03 3244040 /lib64/ > > libc-2.11.1.so > > 7fb05e880000-7fb05e885000 rw-p 00000000 00:00 0 > > 7fb05e885000-7fb05e8c3000 r-xp 00000000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05e8c3000-7fb05eac3000 ---p 0003e000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05eac3000-7fb05eac7000 r--p 0003e000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05eac7000-7fb05eacd000 rw-p 00042000 08:03 3244109 /lib64/ > > libncurses.so.5.6 > > 7fb05eacd000-7fb05eb22000 r-xp 00000000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05eb22000-7fb05ed21000 ---p 00055000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05ed21000-7fb05ed22000 r--p 00054000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05ed22000-7fb05ed23000 rw-p 00055000 08:03 3244048 /lib64/ > > libm-2.11.1.so > > 7fb05ed23000-7fb05ed25000 r-xp 00000000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ed25000-7fb05ef25000 ---p 00002000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ef25000-7fb05ef26000 r--p 00002000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ef26000-7fb05ef27000 rw-p 00003000 08:03 3244046 /lib64/ > > libdl-2.11.1.so > > 7fb05ef27000-7fb05f05e000 r-xp 00000000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0 > > 7fb05f05e000-7fb05f25e000 ---p 00137000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0 > > 7fb05f25e000-7fb05f25f000 r--p 00137000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0 > > 7fb05f25f000-7fb05f264000 rw-p 00138000 08:03 2859042 /usr/lib64/ > > libX11.so.6.2.0Abort > > > > So I would like to compile the source to see if it can be better > > > > When I do so, I have the error message > > In file included from ../../sac-101.3b/src/bbs/setbbv.c:12: > > ../../sac-101.3b/inc/co.h:40: error: conflicting types for 'getline' > > /usr/include/stdio.h:653: error: previous declaration of 'getline' > > was here > > make[1]: *** [bbs/setbbv.o] Error 1 > > make: *** [all-recursive] Error 1 > > > > Is that any solution to go head.... > > > > Thanks > > > > Anne > > -- > > Anne Deschamps > > G?oazur/CNRS > > B?t 3, 250 rue A. Einstein > > 06560 Sophia Antipolis > > tel: +33 4 92 94 26 16 > > secr?tariat : +33 4 92 94 26 02 > > _______________________________________________ > > sac-help mailing list > > sac-help at iris.washington.edu > > http://www.iris.washington.edu/mailman/listinfo/sac-help > > > > _______________________________________________ > sac-help mailing list > sac-help at iris.washington.edu > http://www.iris.washington.edu/mailman/listinfo/sac-help > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From snoke at vt.edu Thu Dec 22 12:26:42 2011 From: snoke at vt.edu (Arthur Snoke) Date: Thu, 22 Dec 2011 15:26:42 -0500 (EST) Subject: [SAC-HELP] glibc detected (when trying to get polezeros using rdseed) In-Reply-To: References:

Message-ID: Carl, a couple of comments/questions. First, after sending my message last night I realized it was incomplete: In my experience, on all platforms one often finds that a build on a release may not work on earlier releases if dynamical libraries are involved. What may be different about Linux is that it may work only on the same release it was built on. The earlier reported problem on SAC on Linux 64 may have been because the build was on a later version. Next, did you do your test with the built-from-sources RDSEED v5.1 build? I got similar warnings to the ones you got when I built v5.2 beta on my Mac OS 10.6. Interestingly, no warnings when I built it on OS 10.4 Intel. Those warnings do not seem to matter. RDSEED v5.1 has several new features -- especially dealing with polezero files. As is often the case, new features may lead to new bugs. Working with them on getting compatibility between RDSEED and SAC led to a few of the changes between the pre-release and final versions of SAC v101.5. Aside from the polezero stuff, the main changes I can recall off hand fro a SAC point of view is that now the default EVDP is kilometers and CONSTANT is no longer defined. I suggest you make your SEED volume available to Rob/IRIS as Rob wants to check to see if this might be a new bug. As they can be large, I suggest you put it on a Web site and tell Rob/Chris where it is. Otherwise, Rob can probably write you (off list) instructions about how you can upload it to an IRIS server. (Chris is the one who had been working on RDSEED, but I think he is on vacation right now, so write both.) Arthur p.s. What is the day for you with the earliest sunset? For us it is around December 6. We have already gained four minutes. The latest sunrise will be around January 6. However, by local time it was the last day of Daylight Savings time. On Thu, 22 Dec 2011, Carl Tape wrote: > First, I downloaded sac-101.5 and reproduced the problem I mentioned: > the gclib exit error and message. My inputs into rdseedv5.1 are "d", "y" > for polezeros, "3" to check all, "y" to extract response," and the rest > defaults. If you do not request polezeros, there is no error message or > exit. If you do request polezeros, there is an error message, but it > appears that the files are generated (which is good!). (The exit might > be an issue if you are running a script with multiple files.) > > I tried recompiling rdseed and did notice this warning (among others): > > cc -I../Include -O -m64??? -c -o output_sac.o output_sac.c > output_sac.c: In function ?output_sac?: > output_sac.c:274: warning: assignment makes pointer from integer without a > cast > output_sac.c: In function ?write_out_PnZs?: > output_sac.c:1521: warning: assignment makes pointer from integer without a > cast > > Anyway, there is no urgency to this. I will try things out with rdseedv5.2 > and can try out beta versions in the mean time, if you want. From seismo_003 at rediffmail.com Fri Dec 23 02:30:12 2011 From: seismo_003 at rediffmail.com (Sunil Roy) Date: 23 Dec 2011 10:30:12 -0000 Subject: [SAC-HELP] =?utf-8?q?how_to_read_and_write_sac_file_in_C_program?= Message-ID: <20111223103012.31799.qmail@f4mail-235-247.rediffmail.com> Hi, I want to read and write the sac file in C program. As I want to do some basic operation like 3D rotation [LQT] and time shift. SAC file can be read in C by #include "sac.h", but I want to know how. I want to write the changes to header. Thanks for the help Sunil -------------- next part -------------- An HTML attachment was scrubbed... URL: From seismo_003 at rediffmail.com Sun Dec 25 05:12:55 2011 From: seismo_003 at rediffmail.com (Sunil Roy) Date: 25 Dec 2011 13:12:55 -0000 Subject: [SAC-HELP] =?utf-8?q?Not_able_to_get_complete_header_information_?= =?utf-8?q?by_using_C_code?= Message-ID: <20111225131255.1210.qmail@f4mail-235-223.rediffmail.com> I am writing C code to read sac file. But what I have found that my out put sac file does not contain all the header information as to my input sac file. I am using wsac1 (kname, yarray, & npts, &beg, &del, &nerr, strlen( out )); to write it to the sac header. Did i am doing some wrong or probably my code is not complete. how to write the complete header information. my read (in) header info NPTS = 35999 B = 0.000000e+00 E = 1.799900e+03 IFTYPE = TIME SERIES FILE LEVEN = TRUE DELTA = 5.000000e-02 DEPMIN = -1.670385e+04 DEPMAX = 1.073576e+04 DEPMEN = -3.021250e-01 OMARKER = -675.06 T1MARKER = 115.61 (Pdiff) T7MARKER = 704.17 (SKS) T8MARKER = 751.13 (SKKS) T9MARKER = 1277.3 (PKKS) KZDATE = JUL 29 (210), 2011 KZTIME = 07:53:37.694 KSTNM = ADKI CMPAZ = 0.000000e+00 CMPINC = 9.000000e+01 STLA = 1.584456e+01 STLO = 7.996883e+01 STEL = 4.900000e+01 EVLA = -2.378000e+01 EVLO = 1.797600e+02 EVDP = 5.230000e+05 DIST = 1.168606e+04 AZ = 2.809172e+02 BAZ = 1.108402e+02 GCARC = 1.049953e+02 LOVROK = TRUE USER1 = 2.543314e+02 USER7 = 2.541673e+02 USER8 = 4.006796e+02 USER9 = 1.573983e+02 NVHDR = 6 NWFID = 1 LPSPOL = FALSE LCALDA = TRUE KCMPNM = BHN MAG = 6.700000e+00 my write (out) sac header info NPTS = 35999 B = 0.000000e+00 E = 1.799900e+03 IFTYPE = TIME SERIES FILE LEVEN = TRUE DELTA = 5.000000e-02 DEPMIN = -1.670385e+04 DEPMAX = 1.073576e+04 DEPMEN = -3.021250e-01 KSTNM = sta LOVROK = TRUE NVHDR = 6 LPSPOL = FALSE LCALDA = TRUE KCMPNM = Q Thanks for help Sunil Roy Seismological Observatory National Geophysical Research Institute Hyderabad, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From kenneth_a_macpherson at yahoo.com Mon Dec 26 18:20:47 2011 From: kenneth_a_macpherson at yahoo.com (Kenneth Macpherson) Date: Mon, 26 Dec 2011 18:20:47 -0800 (PST) Subject: [SAC-HELP] Not able to get complete header information by using C code In-Reply-To: <20111225131255.1210.qmail@f4mail-235-223.rediffmail.com> Message-ID: <1324952447.78610.YahooMailClassic@web161906.mail.bf1.yahoo.com> Hello Sunil, The WSAC0() function will write more complete header information than WSAC1().? You will need to use it in conjunction with the functions NEWHDR() and SET?HV().? Here is an example of how I populate a header.? I doubt this is the most elegant way to do it, but it seems to work: . . . /* Add header values */ ??? newhdr(); ??? setnhv("NPTS", & np, & NERR, 4); ??? setfhv("DELTA" , & DEL, & NERR, 5); ??? setfhv("B" , & BEG, & NERR, 1); ??? setfhv("STLA", & STLA, & NERR, 4); ??? setfhv("STLO", & STLO, & NERR, 4); ??? setfhv("EVLA", & EVLA, & NERR, 4); ??? setfhv("EVLO", & EVLO, & NERR, 4); ??? setfhv("EVDP", & EVDP, & NERR, 4); ??? setfhv("MAG", & MAG, & NERR, 3); ??? setfhv("O", & O, & NERR, 1); ??? setkhv("KSTNM" , kstnm , & NERR , 5 , strlen(kstnm)); ??? setnhv("NZYEAR", & NZYEAR, & NERR, 6); ??? setnhv("NZJDAY", & NZJDAY, & NERR, 6); ??? setnhv("NZHOUR", & NZHOUR, & NERR, 6);? ??? setnhv("NZMIN", & NZMIN, & NERR, 5); ??? setnhv("NZSEC", & NZSEC, & NERR, 5); ??? setnhv("NZMSEC", & NZMSEC, & NERR, 6); ??? /* Use SAC libraries to write the binaries: */ ??? strcpy(KCMPNM, "N"); // N-S component ??? setkhv("KCMPNM" , KCMPNM, & NERR , 6 , strlen(KCMPNM)); ??? wsac0(sacN, T, N, & NERR, strlen(sacN)); . . . Good Luck! Ken Kenneth A. Macpherson Research Fellow Earth Observatory of Singapore (EOS) Nanyang Technological University 50 Nanyang Avenue, Block N2-01a-15, Singapore 639798 Telephone: (65) 6592 1772 --- On Sun, 12/25/11, Sunil Roy wrote: From: Sunil Roy Subject: [SAC-HELP] Not able to get complete header information by using C code To: "sac-help at iris.washington.edu" Date: Sunday, December 25, 2011, 8:12 AM I am writing C code to read sac file. But what I have found that my out put sac file does not contain all the header information as to my input sac file. I am using wsac1 (kname, yarray, & npts, &beg, &del, &nerr, strlen( out )); to write it to the sac header. Did i am doing some wrong or probably my code is not complete. how to write the complete header information. my read (in) header info ???????? NPTS = 35999 ??????????? B = 0.000000e+00 ??????????? E = 1.799900e+03 ?????? IFTYPE = TIME SERIES FILE ??????? LEVEN = TRUE ??????? DELTA = 5.000000e-02 ?????? DEPMIN = -1.670385e+04 ?????? DEPMAX = 1.073576e+04 ?????? DEPMEN = -3.021250e-01 ????? OMARKER = -675.06 ???? T1MARKER = 115.61?????????? (Pdiff) ???? T7MARKER = 704.17?????????? (SKS) ???? T8MARKER = 751.13?????????? (SKKS) ???? T9MARKER = 1277.3?????????? (PKKS) ?????? KZDATE = JUL 29 (210), 2011 ?????? KZTIME = 07:53:37.694 ??????? KSTNM = ADKI ??????? CMPAZ = 0.000000e+00 ?????? CMPINC = 9.000000e+01 ???????? STLA = 1.584456e+01 ???????? STLO = 7.996883e+01 ???????? STEL = 4.900000e+01 ???????? EVLA = -2.378000e+01 ???????? EVLO = 1.797600e+02 ???????? EVDP = 5.230000e+05 ???????? DIST = 1.168606e+04 ?????????? AZ = 2.809172e+02 ????????? BAZ = 1.108402e+02 ??????? GCARC = 1.049953e+02 ?????? LOVROK = TRUE ??????? USER1 = 2.543314e+02 ??????? USER7 = 2.541673e+02 ??????? USER8 = 4.006796e+02 ??????? USER9 = 1.573983e+02 ??????? NVHDR = 6 ??????? NWFID = 1 ?????? LPSPOL = FALSE ?????? LCALDA = TRUE ?????? KCMPNM = BHN ????????? MAG = 6.700000e+00 my write (out) sac header info ?????? NPTS = 35999 ????????? B = 0.000000e+00 ????????? E = 1.799900e+03 ???? IFTYPE = TIME SERIES FILE ????? LEVEN = TRUE ????? DELTA = 5.000000e-02 ???? DEPMIN = -1.670385e+04 ???? DEPMAX = 1.073576e+04 ???? DEPMEN = -3.021250e-01 ????? KSTNM = sta ???? LOVROK = TRUE ????? NVHDR = 6 ???? LPSPOL = FALSE ???? LCALDA = TRUE ???? KCMPNM = Q Thanks for help Sunil Roy Seismological Observatory National Geophysical Research Institute Hyderabad, India Follow?Rediff Deal ho jaye!?to get exciting offers in your city everyday. -----Inline Attachment Follows----- _______________________________________________ sac-help mailing list sac-help at iris.washington.edu http://www.iris.washington.edu/mailman/listinfo/sac-help -------------- next part -------------- An HTML attachment was scrubbed... URL: