transferResponse

This calculates and applies the polezero response from the sensor (stage 1) in the response along with the overall gain. The response will be retrieved from the source in the network arm, but if the server responds that response does not exist, then this processor will fail.

Great care should be taken with this processor as the transfer is a spectral division, and is hence inherently unstable. This basically means that if you allow the frequency limits to be too large, specified in lowCut, lowPass, highPass and highCut, you will be dividing one very small number by another very small number, which due to rounding errors may generate very large amplitudes at long periods which are not real. Also, you should almost always apply an rmean and taper before applying transferResponse.

The defaults are as in the example below. See the sac manual for more in depth discussion of transfer. SOD does not use SAC directly, but the implementation is modeled on SAC and should have identical results. Meaning that the results, assuming the response is set up correctly, should be displacement, ie it is meant to be the same as running in sac the command:

transfer from polezero subtype xyz to none

Example 

<transferResponse>
    <lowCut>0.005</lowCut>
    <lowPass>0.01</lowPass>
    <highPass>1e5</highPass>
    <highCut>1e6</highCut>
</transferResponse>

This consists of

<transferResponse>

<lowCut>float</lowCut> optional
<lowPass>float</lowPass> optional
<highPass>float</highPass> optional
<highCut>float</highCut> optional
</transferResponse>

Places this can be found

In seismogramProcess there is a choice between all of the following