From ktenidou at civil.auth.gr  Wed Oct  1 11:09:22 2008
From: ktenidou at civil.auth.gr (Olga-Joan Ktenidou)
Date: Wed, 1 Oct 2008 13:09:22 -0500
Subject: [SAC-HELP] response spectra
Message-ID: <00ab01c923f0$d7db81a0$49e7f884@isismologica.iingen.unam.mx>

dear all,

just wondering if anyone had come across a way to calculate response spectra through sac..
any help/suggestion much appreciated!
thanks,

olga

----
Olga-Joan Ktenidou
Aristotle University of Thessaloniki
Department of Civil Engineering
Lab. of Soil Mechanics, Foundation Eng. & Geotechnical Earthquake Eng.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20081001/c3733df2/attachment.htm>

From valzimmer at berkeley.edu  Tue Oct  7 13:35:54 2008
From: valzimmer at berkeley.edu (Val Zimmer)
Date: Tue, 07 Oct 2008 13:35:54 -0700
Subject: [SAC-HELP] how does SAC define the header variable CMPINC, exactly?
Message-ID: <48EBC82A.2090300@berkeley.edu>

Hello SAC users,

I have a dataset from a station that was NOT placed perfectly level - 
e.g. the sensor was placed on a ledge that had a little bit of tilt, 
such that Z is not perfectly up/down, and N + E have some down or upward 
component in the data.  I'm now trying to analyze that data, but have 
yet to find a good definition of cmpinc in the manual (all it says is  
"Component incident angle (degrees from vertical)").  CMPINC has no 
inherent orientation (like CMPAZ, from north, and looking down with 90 
to the right e.g. east), but I can think of only one good, logical way 
to define cmpinc.  Although, I'm probably missing something, and would 
like to verify that this is correct, hence the email to you all.

I can infer the following things from pulling the data from an 
earthquake seismology station (cmb.bk):

    * +Z is probably up, (not down like in the oilfield):  Up = 0, hence
      Down = 180. 
    * the other components have cmpinc = 90 (N + E)
    * Therefore, the direction of the cmpinc vector *must* be relative
      to the cmpaz vector AND that cmpinc vector corresponds to apparent
      tilt along that vector (not absolute/maximum tilt for the whole
      instrument in whatever direction that happens to be).
    * It follows other axes would have to be defined as follows:
          o DIR               CMPAZ       CMPINC
          o south                 180               90
          o west                  270               90
          o n + a little up       0                 75
          o e + a little down  90              110

Can anyone tell me if this reasoning is correct, and if not, point me to 
some documentation with a clear definition?

Oh, and if any of you know how Antelope defines the <vang> vector, I'm 
also trying to figure that out (I think that Antelope's definition of 
"vertical" is different, e.g. Up = 180 and Down = 0, although, I cannot 
confirm it).

Thanks for your time!
Valerie Zimmer

From fjt21 at cam.ac.uk  Tue Oct  7 16:19:21 2008
From: fjt21 at cam.ac.uk (Frederik Tilmann)
Date: 08 Oct 2008 00:19:21 +0100
Subject: [SAC-HELP] how does SAC define the header variable CMPINC,
	exactly?
In-Reply-To: <48EBC82A.2090300@berkeley.edu>
References: <48EBC82A.2090300@berkeley.edu>
Message-ID: <Prayer.1.3.0.0810080019210.6235@hermes-1.csi.cam.ac.uk>

Dear Valerie

as far as I know your interpretation is essentially correct except that I 
am not entirely clear with what you mean by
>    * Therefore, the direction of the cmpinc vector *must* be relative
>      to the cmpaz vector AND that cmpinc vector corresponds to apparent
>      tilt along that vector (not absolute/maximum tilt for the whole
>      instrument in whatever direction that happens to be).

If you think of each component as a vector then cmpinc is the angle the 
vector makes with vertical up, and cmpaz is the azimuth clockwise from 
north of the horizontal projection of the component vector. It does not 
make sense to talk about the cmpinc or cmpaz vector. For cmpinc=0 or 
cmpinc=180 the value of cmpaz is irrelevant, of course. As far as I know 
nowhere in SAC is cmpinc actually used except to check whether components 
are horizontal for application of the "rot to gcp" command.

A few years back I wrote a SAC command to rotate an arbitrarily oriented 
sensor (3 components needed to be perpendicular) into either VRT, ZNE, or 
LQT system, and this command used cmpinc. This used the extern mechanism of 
sac2000 but I am not sure whether this way of loading up user-defined 
commands works with the more recent versions of sac. If you are interested 
I can send you the source.

Regards
Frederik








On Oct 7 2008, Val Zimmer wrote:

>Hello SAC users,
>
>I have a dataset from a station that was NOT placed perfectly level - 
>e.g. the sensor was placed on a ledge that had a little bit of tilt, 
>such that Z is not perfectly up/down, and N + E have some down or upward 
>component in the data.  I'm now trying to analyze that data, but have 
>yet to find a good definition of cmpinc in the manual (all it says is  
>"Component incident angle (degrees from vertical)").  CMPINC has no 
>inherent orientation (like CMPAZ, from north, and looking down with 90 
>to the right e.g. east), but I can think of only one good, logical way 
>to define cmpinc.  Although, I'm probably missing something, and would 
>like to verify that this is correct, hence the email to you all.
>
>I can infer the following things from pulling the data from an 
>earthquake seismology station (cmb.bk):
>
>    * +Z is probably up, (not down like in the oilfield):  Up = 0, hence
>      Down = 180. 
>    * the other components have cmpinc = 90 (N + E)
>    * Therefore, the direction of the cmpinc vector *must* be relative
>      to the cmpaz vector AND that cmpinc vector corresponds to apparent
>      tilt along that vector (not absolute/maximum tilt for the whole
>      instrument in whatever direction that happens to be).
>    * It follows other axes would have to be defined as follows:
>          o DIR               CMPAZ       CMPINC
>          o south                 180               90
>          o west                  270               90
>          o n + a little up       0                 75
>          o e + a little down  90              110
>
>Can anyone tell me if this reasoning is correct, and if not, point me to 
>some documentation with a clear definition?
>
>Oh, and if any of you know how Antelope defines the <vang> vector, I'm 
>also trying to figure that out (I think that Antelope's definition of 
>"vertical" is different, e.g. Up = 180 and Down = 0, although, I cannot 
>confirm it).
>
>Thanks for your time!
>Valerie Zimmer
>_______________________________________________
>sac-help mailing list
>sac-help at iris.washington.edu
>http://www.iris.washington.edu/mailman/listinfo/sac-help
>

-- 
===============
Frederik Tilmann
Bullard Laboratories           Tel. +44 1223 765545
Department of Earth Sciences   Fax. +44 1223 360779
University of Cambridge        email: tilmann at esc.cam.ac.uk
Madingley Road
Cambridge CB3 0EZ
UK





From savage at uri.edu  Wed Oct  8 06:46:48 2008
From: savage at uri.edu (Brian Savage)
Date: Wed, 8 Oct 2008 09:46:48 -0400
Subject: [SAC-HELP] [sac-dev] [Fwd: GSE writing]
In-Reply-To: <48EC5675.70702@blacknest.gov.uk>
References: <48EC5675.70702@blacknest.gov.uk>
Message-ID: <D9ECF837-B7CA-4977-9255-7529CDF58EBB@uri.edu>

Sheila,

I just checked versions 101.2 and 101.1 on my machine.
It looks like 101.2 works, 101.1 does not.
I will look further into this for a better answer.

This bug was not known about.  Thank you for being persistent.  :)

Cheers
Brian
savage at uri.edu


On Oct 8, 2008, at 2:43 AM, Sheila Peacock wrote:

> Dear All,
>
> I sent this to SAC-help and got only one reply from someone else
> who had had the same problem, but no solution.  Since you are
> working on the latest edition, I'm wondering if you have come
> across, and addressed, this problem.
>
> Regards,
> Sheila.
>
>
> -------- Original Message --------
> Subject: GSE writing
> Date: Tue, 30 Sep 2008 08:05:05 +0100
> From: Sheila Peacock <sheila at blacknest.gov.uk>
> Organization: AWE Blacknest
> To: sac-help at iris.washington.edu
>
> Dear All,
>
> SAC v. 101.1 either fails or crashes when I try to use "writegse".   
> SAC v. 100 is OK
> with writegse.  Is this a known bug?
>
> Regards,
> Sheila Peacock.
>
> SAC v. 100 (is OK)
> $ sacb
>  SEISMIC ANALYSIS CODE [03/01/2005 (Version 100.00)]
>  Copyright 1995 Regents of the University of California
>
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse 198608011403COL.gse.int
> Converting waveforms .
> Writing station data .
> Writing channel data .
> Writing arrival data .
> 1 waveforms written in 198608011403COL.gse.int
> SAC> end
>
>
> SAC v. 101.1 fails:
>
> $ sac1011
>  SEISMIC ANALYSIS CODE [01/19/2008 (Version 101.1)]
>  Copyright 1995 Regents of the University of California
>
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse 198608011403COL.gse.int
> Segmentation fault
>
>
> or.... (trying various parameters in the parameter list)
>
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse int 198608011403COL.gse.int
>  ERROR 1312: Bad number of files in write file list:
> SAC> writegse int source off 198608011403COL.gse.int
>  ERROR 1312: Bad number of files in write file list:
> SAC> writegse int source off commit 198608011403COL.gse.int
>  ERROR 1312: Bad number of files in write file list:
>
> $ sac1011
>  SEISMIC ANALYSIS CODE [01/19/2008 (Version 101.1)]
>  Copyright 1995 Regents of the University of California
>
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse CM6 198608011403COL.gse.cm6
> Segmentation fault
>
> _______________________________________________
> sac-dev mailing list
> sac-dev at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/sac-dev


From savage at uri.edu  Wed Oct  8 07:17:08 2008
From: savage at uri.edu (Brian Savage)
Date: Wed, 8 Oct 2008 10:17:08 -0400
Subject: [SAC-HELP] [sac-dev] [Fwd: GSE writing]
In-Reply-To: <D9ECF837-B7CA-4977-9255-7529CDF58EBB@uri.edu>
References: <48EC5675.70702@blacknest.gov.uk>
	<D9ECF837-B7CA-4977-9255-7529CDF58EBB@uri.edu>
Message-ID: <B36DC6F4-43BF-4842-99C2-69FAE1DE5091@uri.edu>

Shelia,

After a bit of looking ...

The SeisMgr database in SAC is responsible for writing GSE files.
If the SeisMgr database is off the writing of GSE files fails.

Version:  If SeisMgr database on by default
v100.0:   On
v101.1:   Off  (writegse fails)
v101.2:   On

The SeisMgr database should is now be on by default in v101.2 as well  
as in future versions.

To turn on the database set the environment variable in sh or csh (in  
v101.1 and later)
sh% export SAC_USE_DATABASE=1
csh% setenv SAC_USE_DATABASE 1

Sorry for the headaches.

Cheers
Brian


On Oct 8, 2008, at 9:46 AM, Brian Savage wrote:

> Sheila,
>
> I just checked versions 101.2 and 101.1 on my machine.
> It looks like 101.2 works, 101.1 does not.
> I will look further into this for a better answer.
>
> This bug was not known about.  Thank you for being persistent.  :)
>
> Cheers
> Brian
> savage at uri.edu
>
>
> On Oct 8, 2008, at 2:43 AM, Sheila Peacock wrote:
>
>> Dear All,
>>
>> I sent this to SAC-help and got only one reply from someone else
>> who had had the same problem, but no solution.  Since you are
>> working on the latest edition, I'm wondering if you have come
>> across, and addressed, this problem.
>>
>> Regards,
>> Sheila.
>>
>>
>> -------- Original Message --------
>> Subject: GSE writing
>> Date: Tue, 30 Sep 2008 08:05:05 +0100
>> From: Sheila Peacock <sheila at blacknest.gov.uk>
>> Organization: AWE Blacknest
>> To: sac-help at iris.washington.edu
>>
>> Dear All,
>>
>> SAC v. 101.1 either fails or crashes when I try to use  
>> "writegse".  SAC v. 100 is OK
>> with writegse.  Is this a known bug?
>>
>> Regards,
>> Sheila Peacock.
>>
>> SAC v. 100 (is OK)
>> $ sacb
>>  SEISMIC ANALYSIS CODE [03/01/2005 (Version 100.00)]
>>  Copyright 1995 Regents of the University of California
>>
>> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
>> SAC> writegse 198608011403COL.gse.int
>> Converting waveforms .
>> Writing station data .
>> Writing channel data .
>> Writing arrival data .
>> 1 waveforms written in 198608011403COL.gse.int
>> SAC> end
>>
>>
>> SAC v. 101.1 fails:
>>
>> $ sac1011
>>  SEISMIC ANALYSIS CODE [01/19/2008 (Version 101.1)]
>>  Copyright 1995 Regents of the University of California
>>
>> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
>> SAC> writegse 198608011403COL.gse.int
>> Segmentation fault
>>
>>
>> or.... (trying various parameters in the parameter list)
>>
>> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
>> SAC> writegse int 198608011403COL.gse.int
>>  ERROR 1312: Bad number of files in write file list:
>> SAC> writegse int source off 198608011403COL.gse.int
>>  ERROR 1312: Bad number of files in write file list:
>> SAC> writegse int source off commit 198608011403COL.gse.int
>>  ERROR 1312: Bad number of files in write file list:
>>
>> $ sac1011
>>  SEISMIC ANALYSIS CODE [01/19/2008 (Version 101.1)]
>>  Copyright 1995 Regents of the University of California
>>
>> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
>> SAC> writegse CM6 198608011403COL.gse.cm6
>> Segmentation fault
>>
>> _______________________________________________
>> sac-dev mailing list
>> sac-dev at iris.washington.edu
>> http://www.iris.washington.edu/mailman/listinfo/sac-dev
>
> _______________________________________________
> sac-help mailing list
> sac-help at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/sac-help


From daedalus at qwest.net  Wed Oct  8 22:51:12 2008
From: daedalus at qwest.net (Bob Hancock)
Date: Wed, 08 Oct 2008 22:51:12 -0700
Subject: [SAC-HELP] Do Loop Bug
Message-ID: <C512E9E0.6FE9%daedalus@qwest.net>

I copied the Do Loop macro for particle motion plots from the Do Loop
Examples contained in the MACRO Section of the SAC Manual, and have found a
problem ? See Macro followed by explanation below:

READ ABC 
SETBB TIME1 0 
DO TIME2 FROM 2 TO 10 BY 2
XLIM %TIME1 $TIME2 
TITLE 'Particle Motion from %TIME1 to $TIME2$'
PLOTPM 
SETBB TIME1 $TIME2 
ENDDO

There are four variables in the macro

Time1 ? The starting value for XLIM
Time2 ? The ending value for XLIM
Upper limit of macro processing
Incremental value to increase or decrease the values of both Time1 and Time2
for the next increment.

As long as the incremental value is equal to or greater than the time
difference between Time1 and Time2, the macro works as advertised.  NOTE ?
This is how the Macro above is setup.

However, when the incremental time is decreased to less than the value
between Time1 and Time2, the time difference between Time1 and Time two is
AUTOMATICALLY decreased to equal the incremental value.  See values in Macro
below:

READ ABC 
SETBB TIME1 2300 
DO TIME2 FROM 2400 TO 2800 BY 5
XLIM %TIME1 $TIME2 
TITLE 'Particle Motion from %TIME1 to $TIME2$'
PLOTPM 
SETBB TIME1 $TIME2 
ENDDO

I have not found a solution to this problem.

If anyone has encountered this problem, or has a suggestion on how to
alleviate the problem, I would appreciate hearing from them.

Thank You

Bob Hancock
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20081008/8ae3f9f4/attachment-0001.htm>

From george at gly.bris.ac.uk  Thu Oct  9 06:55:13 2008
From: george at gly.bris.ac.uk (George Helffrich)
Date: Thu, 9 Oct 2008 14:55:13 +0100
Subject: [SAC-HELP] Do Loop Bug
In-Reply-To: <C512E9E0.6FE9%daedalus@qwest.net>
References: <C512E9E0.6FE9%daedalus@qwest.net>
Message-ID: <cd8fecd49277ef3f22344443d296c076@gly.bris.ac.uk>

Dear All -

	It is a feature-cum-bug in SAC's implementation of DO that all the 
numeric values are generated as a single string upon entry to the loop. 
  If there are many values (80 in your case) that's a long string and it 
can get truncated or overflow.  Here's a workaround that uses 
SYSTEMCOMMAND to build a file of macro invocations for each time 
window.  Beware of all the "@"-escapes:

funcgen seismogram; w /tmp/hold0; w /tmp/hold1; r /tmp/hold0 /tmp/hold1
sc echo xlim @$1 @$2                               > /tmp/macro
sc echo title 'Particle Motion from @$1 to @$2@$' >> /tmp/macro
sc echo plotpm                                    >> /tmp/macro
sc echo 2400 2800 5 | awk '{for@(t=@$1;t<=@$2;t+=@$3@) printf "m 
/tmp/macro @%f @%f\n",t,t+100}' > /tmp/sac.in
sc rm -f /tmp/macro /tmp/sac.in

On 9 Oct 2008, at 06:51, Bob Hancock wrote:

> I copied the Do Loop macro for particle motion plots from the Do Loop 
> Examples contained in the MACRO Section of the SAC Manual, and have 
> found a problem ? See Macro followed by explanation below:
>
> READ ABC
>  SETBB TIME1 0
>  DO TIME2 FROM 2 TO 10 BY 2
>  XLIM %TIME1 $TIME2
>  TITLE 'Particle Motion from %TIME1 to $TIME2$'
>  PLOTPM
>  SETBB TIME1 $TIME2
>  ENDDO
>
> There are four variables in the macro
>
>  Time1 ? The starting value for XLIM
>  Time2 ? The ending value for XLIM
>  Upper limit of macro processing
>  Incremental value to increase or decrease the values of both Time1 
> and Time2 for the next increment.
>
>  As long as the incremental value is equal to or greater than the time 
> difference between Time1 and Time2, the macro works as advertised. 
> ?NOTE ? This is how the Macro above is setup.
>
>  However, when the incremental time is decreased to less than the 
> value between Time1 and Time2, the time difference between Time1 and 
> Time two is AUTOMATICALLY decreased to equal the incremental value. 
> ?See values in Macro below:
>
> READ ABC
>  SETBB TIME1 2300
>  DO TIME2 FROM 2400 TO 2800 BY 5
>  XLIM %TIME1 $TIME2
>  TITLE 'Particle Motion from %TIME1 to $TIME2$'
>  PLOTPM
>  SETBB TIME1 $TIME2
>  ENDDO
>
>  I have not found a solution to this problem.
>
>  If anyone has encountered this problem, or has a suggestion on how to 
> alleviate the problem, I would appreciate hearing from them.
>
>  Thank You
>
>  Bob Hancock  _______________________________________________
> sac-help mailing list
> sac-help at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/sac-help
>
                                     George Helffrich
                                     george at geology.bristol.ac.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 5117 bytes
Desc: not available
URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20081009/7a74aa49/attachment.bin>

From dtdngkua at memphis.edu  Fri Oct 10 15:48:57 2008
From: dtdngkua at memphis.edu (Donny T Dangkua (dtdngkua))
Date: Fri, 10 Oct 2008 17:48:57 -0500
Subject: [SAC-HELP] Install SAC
Message-ID: <C5154609.368%dtdngkua@memphis.edu>

Hello,
I'm trying to install SAC in my MacBook (OSX 10.5),
I have problem after I run the configure (./configure) when I type 'make', the result like shown below:

Making all in libedit
make[1]: Nothing to be done for `all'.
Making all in utils
make[1]: Nothing to be done for `all'.
Making all in src
gcc     -I../inc -I../libedit/include   -o sac  main/sac.o -L. libsac_all.a libevalresp.a libSMnonOracleFuncs.a  libSacOracleStubFuncs.a    -lX11 ../libedit/lib/libedit.a -ldl -lm -lncurses
ld: library not found for -lX11
collect2: ld returned 1 exit status
make[1]: *** [sac] Error 1
make: *** [all-recursive] Error 1

Can you tell me what's the problem and how to solve it?
I'm sorry if it's just a basic question.
Thank you.

Donny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20081010/0bc19163/attachment.htm>

From j.wookey at bristol.ac.uk  Fri Oct 10 22:09:50 2008
From: j.wookey at bristol.ac.uk (James Wookey)
Date: Sat, 11 Oct 2008 06:09:50 +0100
Subject: [SAC-HELP] Install SAC
In-Reply-To: <C5154609.368%dtdngkua@memphis.edu>
References: <C5154609.368%dtdngkua@memphis.edu>
Message-ID: <D5D24695-8A55-48A8-8550-1ABC21158634@bristol.ac.uk>

Dear Donny,

It looks like you don't have the X11 libraries installed. This is an  
optional install in Leopard, and should be on your Leopard DVD. See:

http://www1.gly.bris.ac.uk/~wookey/MEFTLG/index.htm

for some extra detail if you need it. However, there is an easier  
option for the Mac user! You can also use MacSAC, which is an easy to  
install, extra featured binary version for intel and powerpc Macs  
which is developed and maintained by George Helffrich. It also has a  
native Mac graphics device. See:

http://www1.gly.bris.ac.uk/~george/sac-bugs.html

to download it. I still recommend you install X11 as well, however.

Hope this helps!

Best wishes,

James

On 10 Oct 2008, at 23:48, Donny T Dangkua (dtdngkua) wrote:

> Hello,
> I?m trying to install SAC in my MacBook (OSX 10.5),
> I have problem after I run the configure (./configure) when I type  
> ?make?, the result like shown below:
>
> Making all in libedit
> make[1]: Nothing to be done for `all'.
> Making all in utils
> make[1]: Nothing to be done for `all'.
> Making all in src
> gcc     -I../inc -I../libedit/include   -o sac  main/sac.o -L.  
> libsac_all.a libevalresp.a libSMnonOracleFuncs.a   
> libSacOracleStubFuncs.a    -lX11 ../libedit/lib/libedit.a -ldl -lm - 
> lncurses
> ld: library not found for -lX11
> collect2: ld returned 1 exit status
> make[1]: *** [sac] Error 1
> make: *** [all-recursive] Error 1
>
> Can you tell me what?s the problem and how to solve it?
> I?m sorry if it?s just a basic question.
> Thank you.
>
> Donny
> _______________________________________________
> sac-help mailing list
> sac-help at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/sac-help




: James Wookey
: Department of Earth Sciences
: University of Bristol
: Wills Building, Queens Road
: Bristol BS8 1RJ, U.K.
: Tel +44 (0)117 954 5496
: Fax +44 (0)117 925 3385
: j.wookey at bristol.ac.uk
: http://www1.gly.bris.ac.uk/~wookey





From yamac at sevo.kyushu-u.ac.jp  Tue Oct 14 21:22:25 2008
From: yamac at sevo.kyushu-u.ac.jp (Yusuke YAMASHITA)
Date: Wed, 15 Oct 2008 13:22:25 +0900
Subject: [SAC-HELP] Install SAC in my Linux Machine (Fedora9)
Message-ID: <48F57001.80206@sevo.kyushu-u.ac.jp>

Hello,
I'm trying to install SAC in my Linux machine (Fedora9).
I have problem when I run the SAC command.
If anyone has had any similar problems installing,
I would be grateful for advice.
My Linux machine's performance and the result like shown below:

CPU: Intel(R) Pentium(R)4 3.06GHz
OS: Fedora9 (kernel 2.6.26.5-45.fc9.i686)
Memory: 1GB
HDD: 80GB

Error message:
*** glibc detected *** sac: malloc(): memory corruption: 0x08fb4640 ***
======= Backtrace: =========
/lib/libc.so.6[0x578596]
/lib/libc.so.6(__libc_malloc+0x95)[0x579ce5]
sac[0x804c79d]
sac[0x805369d]
sac[0x804f091]
sac[0x804b15b]
/lib/libc.so.6(__libc_start_main+0xe6)[0x51e5d6]
sac[0x804b041]
======= Memory map: ========
00110000-00111000 r-xp 00110000 00:00 0          [vdso]
00111000-00114000 r-xp 00000000 08:01 1089923    /lib/libuuid.so.1.2
00114000-00115000 rw-p 00003000 08:01 1089923    /lib/libuuid.so.1.2
004e8000-00504000 r-xp 00000000 08:01 1089641    /lib/ld-2.8.so
00504000-00505000 r--p 0001c000 08:01 1089641    /lib/ld-2.8.so
00505000-00506000 rw-p 0001d000 08:01 1089641    /lib/ld-2.8.so
00508000-0066b000 r-xp 00000000 08:01 1089649    /lib/libc-2.8.so
0066b000-0066d000 r--p 00163000 08:01 1089649    /lib/libc-2.8.so
0066d000-0066e000 rw-p 00165000 08:01 1089649    /lib/libc-2.8.so
0066e000-00671000 rw-p 0066e000 00:00 0
00673000-0069a000 r-xp 00000000 08:01 1089791    /lib/libm-2.8.so
0069a000-0069b000 r--p 00026000 08:01 1089791    /lib/libm-2.8.so
0069b000-0069c000 rw-p 00027000 08:01 1089791    /lib/libm-2.8.so
0069e000-006a1000 r-xp 00000000 08:01 1089651    /lib/libdl-2.8.so
006a1000-006a2000 r--p 00002000 08:01 1089651    /lib/libdl-2.8.so
006a2000-006a3000 rw-p 00003000 08:01 1089651    /lib/libdl-2.8.so
00826000-00841000 r-xp 00000000 08:01 1171669    /usr/lib/libxcb.so.1.0.0
00841000-00842000 rw-p 0001a000 08:01 1171669    /usr/lib/libxcb.so.1.0.0
00844000-00941000 r-xp 00000000 08:01 1171671    /usr/lib/libX11.so.6.2.0
00941000-00945000 rw-p 000fc000 08:01 1171671    /usr/lib/libX11.so.6.2.0
00947000-00949000 r-xp 00000000 08:01 1171573    /usr/lib/libXau.so.6.0.0
00949000-0094a000 rw-p 00001000 08:01 1171573    /usr/lib/libXau.so.6.0.0
0094c000-00951000 r-xp 00000000 08:01 1171584    /usr/lib/libXdmcp.so.6.0.0
00951000-00952000 rw-p 00004000 08:01 1171584    /usr/lib/libXdmcp.so.6.0.0
00954000-00955000 r-xp 00000000 08:01 1171670    /usr/lib/libxcb-xlib.so.0.0.0
00955000-00956000 rw-p 00000000 08:01 1171670    /usr/lib/libxcb-xlib.so.0.0.0
00cdd000-00cea000 r-xp 00000000 08:01 1089796    /lib/libgcc_s-4.3.0-20080428.so.1
00cea000-00ceb000 rw-p 0000c000 08:01 1089796    /lib/libgcc_s-4.3.0-20080428.so.1
00d4d000-00d64000 r-xp 00000000 08:01 367882     /usr/lib/libICE.so.6.3.0
00d64000-00d65000 rw-p 00016000 08:01 367882     /usr/lib/libICE.so.6.3.0
00d65000-00d67000 rw-p 00d65000 00:00 0
00d69000-00d70000 r-xp 00000000 08:01 1171806    /usr/lib/libSM.so.6.0.0
00d70000-00d71000 rw-p 00006000 08:01 1171806    /usr/lib/libSM.so.6.0.0
02baa000-02bc0000 r-xp 00000000 08:01 1089765    /lib/libtinfo.so.5.6
02bc0000-02bc3000 rw-p 00015000 08:01 1089765    /lib/libtinfo.so.5.6
02bc5000-02be6000 r-xp 00000000 08:01 1089834    /lib/libncurses.so.5.6
02be6000-02be7000 rw-p 00020000 08:01 1089834    /lib/libncurses.so.5.6
08048000-0820b000 r-xp 00000000 08:01 1173356    /usr/local/sac/bin/sac
0820b000-082d1000 rw-p 001c3000 08:01 1173356    /usr/local/sac/bin/sac
082d1000-08555000 rw-p 082d1000 00:00 0
08fb4000-08fd5000 rw-p 08fb4000 00:00 0          [heap]
b7f00000-b7f21000 rw-p b7f00000 00:00 0
b7f21000-b8000000 ---p b7f21000 00:00 0
b8041000-b8045000 rw-p b8041000 00:00 0
b8059000-b805a000 rw-p b8059000 00:00 0
bfc45000-bfc5a000 rw-p bffeb000 00:00 0          [stack]
abort


-- 
  Yusuke YAMASHITA  ( yamac at sevo.kyushu-u.ac.jp )
  Institute of Seismology and Volcanology,
  Faculty of Sciences, Kyushu University, Japan
  2-5643-29 Shin'yama, Shimabara, Nagasaki 855-0843, Japan
  TEL:+81-957-62-6621  FAX:+81-957-63-0225




From civyfei at gmail.com  Tue Oct 21 13:14:23 2008
From: civyfei at gmail.com (Ching-Wen Chen)
Date: Tue, 21 Oct 2008 15:14:23 -0500
Subject: [SAC-HELP] SAC interact with csh
Message-ID: <bfcaf5f20810211314p7b25d590g63f3a47e8b12a866@mail.gmail.com>

Dear All,

I am writing an instrument response correction script. I set stations' name
and event seperately. It works for "read" in SAC, but not for trans
polezero.  Any suggestion on this one?  Thank your for your time and effort.

--

set STA = "GAC"
set EVENT = "200411150906"
set YYYY =  "2004"
set DISN = `cat stadis | grep $STA | awk '{ print $4 }'`
set STANUM = `cat stadis | grep $STA | awk '{ print $2}'`
/bin/cp 20*.$STA..BHZ.D.SAC D$DISN.$STANUM.$STA.Z
if (-e D$DISN.$STANUM.$STA.Z ) then
sac2000 << !

### read  works####
r  D$DISN.$STANUM.$STA.Z
rmean
taper
p1
########## This doesn't work due to $YYYY and $EVENT
trans from polezero s
/data/cchen/Ontario_CN/CNSN_sac/$YYYY\_sac/$EVENT/Resp_files/$STA\_BHZ to
polezero s
/data/cchen/Ontario_CN/CNSN_sac/generic_resp_files/SAC_PZs_resp03.HHZ
##########

w over
!
endif

-----


Chingwen Chen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20081021/094c49f2/attachment.htm>

From deschamps at geoazur.unice.fr  Sat Oct 25 13:18:20 2008
From: deschamps at geoazur.unice.fr (Anne Deschamps)
Date: Sat, 25 Oct 2008 22:18:20 +0200
Subject: [SAC-HELP] sac-help Digest, Vol 39, Issue 1
In-Reply-To: <mailman.307.1223531485.776.sac-help@iris.washington.edu>
References: <mailman.307.1223531485.776.sac-help@iris.washington.edu>
Message-ID: <49037F0C.6040303@geoazur.unice.fr>

Hi

I would like to use the type evalresp to compute the signal corrected 
from the instrumental response (files provided by rdseed).

What is the IDEP value which should be insered in the header to say that 
I have raw data? Presently in my data IDEP is not defined

I have accelerometric data.

What is the result on accelerometric data of the command
transfer from evalresp to none

What is the result of
transfer from evalresp to acc
the amplitudes are different (even after removing the high frequencies...)
the IDEP in one is  ACCELERATION (CM/SEC/SEC)
          in the other  DISPLACEMENT (NM)

the RESP file indicates
B053F05     Response in units lookup:              M/S**2 - Acceleration

So if you could give me the rules, it will be great as presently the 
result is not what we expect. May be there is a compatibility problem of 
our RESP file.

from yours indications I will try to find the rule for the velocimetric 
data.
Thanks

Anne Deschamps

sac-help-request at iris.washington.edu a ?crit :
> Send sac-help mailing list submissions to
> 	sac-help at iris.washington.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.iris.washington.edu/mailman/listinfo/sac-help
> or, via email, send a message with subject or body 'help' to
> 	sac-help-request at iris.washington.edu
> 
> You can reach the person managing the list at
> 	sac-help-owner at iris.washington.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sac-help digest..."
> 
> 
> Today's Topics:
> 
>    1.  GSE writing (Sheila Peacock)
>    2.  response spectra (Olga-Joan Ktenidou)
>    3.  how does SAC define the header variable CMPINC, exactly?
>       (Val Zimmer)
>    4. Re:  how does SAC define the header variable CMPINC,	exactly?
>       (Frederik Tilmann)
>    5. Re:  [sac-dev] [Fwd: GSE writing] (Brian Savage)
>    6. Re:  [sac-dev] [Fwd: GSE writing] (Brian Savage)
>    7.  Do Loop Bug (Bob Hancock)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 30 Sep 2008 09:57:34 +0100
> From: Sheila Peacock <s.peacock at blacknest.gov.uk>
> Subject: [SAC-HELP] GSE writing
> To: sac-help at iris.washington.edu
> Message-ID: <48E1E9FE.5020002 at blacknest.gov.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> (re-sent)
> 
> 
> Dear All,
> 
> SAC v. 101.1 either fails or crashes when I try to use "writegse".  SAC v. 100 is OK
> with writegse.  Is this a known bug?
> 
> Regards,
> Sheila Peacock.
> 
> SAC v. 100 (is OK)
> $ sacb
>   SEISMIC ANALYSIS CODE [03/01/2005 (Version 100.00)]
>   Copyright 1995 Regents of the University of California
> 
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse 198608011403COL.gse.int
> Converting waveforms .
> Writing station data .
> Writing channel data .
> Writing arrival data .
> 1 waveforms written in 198608011403COL.gse.int
> SAC> end
> 
> 
> SAC v. 101.1 fails:
> 
> $ sac1011
>   SEISMIC ANALYSIS CODE [01/19/2008 (Version 101.1)]
>   Copyright 1995 Regents of the University of California
> 
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse 198608011403COL.gse.int
> Segmentation fault
> 
> 
> or.... (trying various parameters in the parameter list)
> 
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse int 198608011403COL.gse.int
>   ERROR 1312: Bad number of files in write file list:
> SAC> writegse int source off 198608011403COL.gse.int
>   ERROR 1312: Bad number of files in write file list:
> SAC> writegse int source off commit 198608011403COL.gse.int
>   ERROR 1312: Bad number of files in write file list:
> 
> $ sac1011
>   SEISMIC ANALYSIS CODE [01/19/2008 (Version 101.1)]
>   Copyright 1995 Regents of the University of California
> 
> SAC> r 1986.213.14.03.12.3600.DW.COL..SHZ.D.SAC
> SAC> writegse CM6 198608011403COL.gse.cm6
> Segmentation fault
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 1 Oct 2008 13:09:22 -0500
> From: "Olga-Joan Ktenidou" <ktenidou at civil.auth.gr>
> Subject: [SAC-HELP] response spectra
> To: <sac-help at iris.washington.edu>
> Message-ID:
> 	<00ab01c923f0$d7db81a0$49e7f884 at isismologica.iingen.unam.mx>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> dear all,
> 
> just wondering if anyone had come across a way to calculate response spectra through sac..
> any help/suggestion much appreciated!
> thanks,
> 
> olga
> 
> ----
> Olga-Joan Ktenidou
> Aristotle University of Thessaloniki
> Department of Civil Engineering
> Lab. of Soil Mechanics, Foundation Eng. & Geotechnical Earthquake Eng.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20081001/c3733df2/attachment-0001.htm>
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 07 Oct 2008 13:35:54 -0700
> From: Val Zimmer <valzimmer at berkeley.edu>
> Subject: [SAC-HELP] how does SAC define the header variable CMPINC,
> 	exactly?
> To: sac-help at iris.washington.edu
> Message-ID: <48EBC82A.2090300 at berkeley.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hello SAC users,
> 
> I have a dataset from a station that was NOT placed perfectly level - 
> e.g. the sensor was placed on a ledge that had a little bit of tilt, 
> such that Z is not perfectly up/down, and N + E have some down or upward 
> component in the data.  I'm now trying to analyze that data, but have 
> yet to find a good definition of cmpinc in the manual (all it says is  
> "Component incident angle (degrees from vertical)").  CMPINC has no 
> inherent orientation (like CMPAZ, from north, and looking down with 90 
> to the right e.g. east), but I can think of only one good, logical way 
> to define cmpinc.  Although, I'm probably missing something, and would 
> like to verify that this is correct, hence the email to you all.
> 
> I can infer the following things from pulling the data from an 
> earthquake seismology station (cmb.bk):
> 
>     * +Z is probably up, (not down like in the oilfield):  Up = 0, hence
>       Down = 180. 
>     * the other components have cmpinc = 90 (N + E)
>     * Therefore, the direction of the cmpinc vector *must* be relative
>       to the cmpaz vector AND that cmpinc vector corresponds to apparent
>       tilt along that vector (not absolute/maximum tilt for the whole
>       instrument in whatever direction that happens to be).
>     * It follows other axes would have to be defined as follows:
>           o DIR               CMPAZ       CMPINC
>           o south                 180               90
>           o west                  270               90
>           o n + a little up       0                 75
>           o e + a little down  90              110
> 
> Can anyone tell me if this reasoning is correct, and if not, point me to 
> some documentation with a clear definition?
> 
> Oh, and if any of you know how Antelope defines the <vang> vector, I'm 
> also trying to figure that out (I think that Antelope's definition of 
> "vertical" is different, e.g. Up = 180 and Down = 0, although, I cannot 
> confirm it).
> 
> Thanks for your time!
> Valerie Zimmer
> 
> 
> ------------------------------
> 
> Message: 4
> Date: 08 Oct 2008 00:19:21 +0100
> From: Frederik Tilmann <fjt21 at cam.ac.uk>
> Subject: Re: [SAC-HELP] how does SAC define the header variable
> 	CMPINC,	exactly?
> To: Val Zimmer <valzimmer at berkeley.edu>
> Cc: sac-help at iris.washington.edu
> Message-ID: <Prayer.1.3.0.0810080019210.6235 at hermes-1.csi.cam.ac.uk>
> Content-Type: text/plain; format=flowed; charset=ISO-8859-1
> 
> Dear Valerie
> 
> as far as I know your interpretation is essentially correct except that I 
> am not entirely clear with what you mean by
>>    * Therefore, the direction of the cmpinc vector *must* be relative
>>      to the cmpaz vector AND that cmpinc vector corresponds to apparent
>>      tilt along that vector (not absolute/maximum tilt for the whole
>>      instrument in whatever direction that happens to be).
> 
> If you think of each component as a vector then cmpinc is the angle the 
> vector makes with vertical up, and cmpaz is the azimuth clockwise from 
> north of the horizontal projection of the component vector. It does not 
> make sense to talk about the cmpinc or cmpaz vector. For cmpinc=0 or 
> cmpinc=180 the value of cmpaz is irrelevant, of course. As far as I know 
> nowhere in SAC is cmpinc actually used except to check whether components 
> are horizontal for application of the "rot to gcp" command.
> 
> A few years back I wrote a SAC command to rotate an arbitrarily oriented 
> sensor (3 components needed to be perpendicular) into either VRT, ZNE, or 
> LQT system, and this command used cmpinc. This used the extern mechanism of 
> sac2000 but I am not sure whether this way of loading up user-defined 
> commands works with the more recent versions of sac. If you are interested 
> I can send you the source.
> 
> Regards
> Frederik
> 
> 
> 
> 
> 
> 
> 
> 
> On Oct 7 2008, Val Zimmer wrote:
> 
>> Hello SAC users,
>>
>> I have a dataset from a station that was NOT placed perfectly level - 
>> e.g. the sensor was placed on a ledge that had a little bit of tilt, 
>> such that Z is not perfectly up/down, and N + E have some down or upward 
>> component in the data.  I'm now trying to analyze that data, but have 
>> yet to find a good definition of cmpinc in the manual (all it says is  
>> "Component incident angle (degrees from vertical)").  CMPINC has no 
>> inherent orientation (like CMPAZ, from north, and looking down with 90 
>> to the right e.g. east), but I can think of only one good, logical way 
>> to define cmpinc.  Although, I'm probably missing something, and would 
>> like to verify that this is correct, hence the email to you all.
>>
>> I can infer the following things from pulling the data from an 
>> earthquake seismology station (cmb.bk):
>>
>>    * +Z is probably up, (not down like in the oilfield):  Up = 0, hence
>>      Down = 180. 
>>    * the other components have cmpinc = 90 (N + E)
>>    * Therefore, the direction of the cmpinc vector *must* be relative
>>      to the cmpaz vector AND that cmpinc vector corresponds to apparent
>>      tilt along that vector (not absolute/maximum tilt for the whole
>>      instrument in whatever direction that happens to be).
>>    * It follows other axes would have to be defined as follows:
>>          o DIR               CMPAZ       CMPINC
>>          o south                 180               90
>>          o west                  270               90
>>          o n + a little up       0                 75
>>          o e + a little down  90              110
>>
>> Can anyone tell me if this reasoning is correct, and if not, point me to 
>> some documentation with a clear definition?
>>
>> Oh, and if any of you know how Antelope defines the <vang> vector, I'm 
>> also trying to figure that out (I think that Antelope's definition of 
>> "vertical" is different, e.g. Up = 180 and Down = 0, although, I cannot 
>> confirm it).
>>
>> Thanks for your time!
>> Valerie Zimmer
>> _______________________________________________
>> sac-help mailing list
>> sac-help at iris.washington.edu
>> http://www.iris.washington.edu/mailman/listinfo/sac-help
>>
> 



From domenico at gfz-potsdam.de  Thu Oct 30 02:04:05 2008
From: domenico at gfz-potsdam.de (Domenico Di Giacomo)
Date: Thu, 30 Oct 2008 10:04:05 +0100
Subject: [SAC-HELP] TRANSFER
Message-ID: <op.ujtx43qbzs90bw@des58.gfz-potsdam.de>

Hi SAC users,

I am writing a simple script to remove the instrument response by using  
SAC (Version 101.2).

When I was testing the SAC's transfer command, I got this message:

SAC> r 2006.319.11.18.29.3500.KN.ULHL..BHZ.R.SAC
SAC> transfer from evalresp
Extracting evresp response for ULHL, BHZ...

Station (ULHL    ), Channel (BHZ     )
         Waveform multiplied by 1.000000 after deconvolution.

The SCALE field is properly set in the SAC header, but for some reason the  
waveform is multiplied by 1.0.

Does somebody knows where does this problem come from and how to solve it?

Thanks

Domenico

-- 

-----------------------------------------------
Domenico Di Giacomo

Department 2 Physics of the Earth
Section 2.1 Earthquake Risk and Early Warning
Phone: +49 (0)331/288-1285
FAX: +49 (0)331/288-1204
Email: domenico at gfz-potsdam.de
_______________________________________

Helmholtz Centre Potsdam
GFZ German Research Centre For Geosciences
Public Law Foundation State of Brandenburg
Telegrafenberg, D-14473 Potsdam
_______________________________________