You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could "ispaq" convert from acceleration or displacement responses to velocity?
Or could it plot the PSD in acceleration or displacement domain, including the low noise model?
My local data repository stores responses in displacement (IMS standard) and when I get them out in dataless SEED or StationXML file they are in displacement, e.g. three zeros in the Poles-and-Zeros section, and the units are "M". To get plots that look like the output from Mustang, I have to edit the RESP and StationXML files to convert them to velocity (i.e. remove a zero, divide the sensitivity by 2pi/calibration period and change the units to "M/S"). Could "ispaq" do this for itself? I ask because I compared the output with Mustang for station IM.EKB10, which has response in acceleration units:
but the output from Mustang (query line below) is presumably in velocity as it looks more-or-less (!) the same as the output from "ispaq" after I had converted the response file to velocity (pic attached). So I think Mustang converts to velocity for itself.
Could "ispaq" convert from acceleration or displacement responses to velocity?
Or could it plot the PSD in acceleration or displacement domain, including the low noise model?
My local data repository stores responses in displacement (IMS standard) and when I get them out in dataless SEED or StationXML file they are in displacement, e.g. three zeros in the Poles-and-Zeros section, and the units are "M". To get plots that look like the output from Mustang, I have to edit the RESP and StationXML files to convert them to velocity (i.e. remove a zero, divide the sensitivity by 2pi/calibration period and change the units to "M/S"). Could "ispaq" do this for itself? I ask because I compared the output with Mustang for station IM.EKB10, which has response in acceleration units:
http://service.iris.edu/fdsnws/station/1/query?net=IM&sta=EKB10&loc=--&cha=BHZ&startbefore=2019-05-01T00:00:00&endafter=2019-05-02T00:00:00&level=response
but the output from Mustang (query line below) is presumably in velocity as it looks more-or-less (!) the same as the output from "ispaq" after I had converted the response file to velocity (pic attached). So I think Mustang converts to velocity for itself.
https://services.iris.edu/mustang/noise-pdf/1/query?target=IM.EKB10..BHZ.M&starttime=2024-06-05&endtime=2024-06-08&plot.power.max=-100&plot.power.min=-190&plot.period.max=100&plot.period.min=0.1&format=plot
The text was updated successfully, but these errors were encountered: