TauP SetSac

TauP SetSac uses the depth and distance information in textsc{sac}~cite{sacmanual}

file headers to

put theoretical arrival times into the t0t9 header variables. The header variable for a phase can be specified with by a dash followed by a number, for instance S-9 puts the S arrival time in t9. If no header is specified then the time will be inserted in the first header variable not allocated to another phase, starting with 0. If there are no header variables not already allocated to a phase, then the additional phases will not be added to the header. Note that this does not refer to times that are already in the textsc{sac} file before TauP SetSac is run. They will be overwritten. The ray parameter, in seconds per radian, is also inserted into the corresponding user0-user9 header.

Note that triplicated phases are a problem as there is only one spot to put a time. For example, in iasp91 S has three arrivals at 20~degrees but only one can be put into the choosen header. TauP SetSac assumes that the first arrival is the most important, and uses it. Additional header variables may be appended for the times of the multiples. For example, S-458 would put the first S arrival into header t4 and the second into t5 and the thrid into t8. If there are more arrivals than headers, the later arrivals are not added. If there are more headers than arrivals, then the header is not set.

Warning: TauP SetSac assumes the textsc{evdp} header has depth in meters unless the -evdpkm flag is used, in which case kilometers are assumed. This may be a problem for users that improperly use kilometers for the depth units. Due to much abuse of the textsc{sac} depth header units, a warning message is printed if the depth appears to be in kilometers, i.e. it is $< 1000$, and -evdpkm is not used. This can be safely ignored if the event really is less than 1000 meters deep. See the textsc{sac} manual~cite{sacmanual} for confirmation.

The textsc{sac} files must have textsc{evdp} and the textsc{o} marker set. Also, if textsc{gcarc} or textsc{dist} is not set then TauP SetSac can calculate a distance only if textsc{stla}, textsc{stlo}, textsc{evla} and textsc{evlo} are set.

The user should be very careful about previously set header variables. TauP SetSac will overwrite any previously set t user headers. A future feature may do more careful checking, but the current version makes no effort to verify that the header is undefined before writing.

If the given filename is a directory, TauP SetSac will recursively look for files within that directory to process. Thus, a large directory structure of Sac files can be processed easily.

The usage is:

Usage: taup_setsac [arguments]  or, for purists, java edu.sc.seis.TauP.TauP_SetSac [arguments]
Arguments are:-ph phase list     -- comma separated phase list,
                      use phase-# to specify the sac header,
                      for example, ScS-8 puts ScS in t8
-pf phasefile      -- file containing phases

-mod[el] modelname -- use velocity model "modelname" for calculations
                      Default is iasp91.

--evdpkm            -- sac depth header is in km, default is meters

--prop [propfile]   -- set configuration properties
--debug             -- enable debugging output
--verbose           -- enable verbose output
--version           -- print the version
--help              -- print this out, but you already know that!
sacfilename [sacfilename ...]
Ex: taup_setsac --mod S_prem -ph S-8,ScS-9 wmq.r wmq.t wmq.zputs the first S arrival in T8 and ScS in T9