New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question about channel filtering behavior #79
Comments
Hi @dylanmikesell, your channel_list format looks fine. These are channel_priorities by the way and I do not know why it returns low frequency and broadband channels as well. Under the hood Obspy's mass downloader is being used these are the documentations https://docs.obspy.org/packages/autogen/obspy.clients.fdsn.mass_downloader.html |
I think the mass_downloader call is fine. However, in utils/downloader.py there is the makeStationList() function. It looks to me like someone was trying to code in a channel filter given the |
@dylanmikesell I see now. It seems the formatting conventions for channel list is different here. Could you try something like this: channel_list=["HHZ", "HHN", "HHE", "HH1", "HH2"] |
I have a related question to this. I am creating my station list and finding a mix of stations with multiple channels and some with a single channel, which seems fine. However, when I run the downloader, I am only getting mseed files with single component data for every station on my station list. I don't believe I am using the downloader incorrectly but is there something I am doing that is causing only a single channel to be collected per station? ExampleStation MNHN from JSON list has channels HH2, HHZ, HH1 downloaded mseed file 'TX.MNHN.00.HHZ__20200501T000000Z__20200502T000000Z.mseed' only has the channel HHZ and is the only mseed downloaded for station MNHN. Code
|
@Bryanrt-geophys Hi Bryan, that sometimes happens just due to networking traffic. I have seen that behavior before but couldn't find any explanation/solution for it as it is mainly governed by Obspy API and IRIS fetching mechanism. |
@smousavi05 Thanks Mustafa. It appears to have happened with every instance I have drawn on so far. I will try looking into Obspy and see if there is something I can figure out from there. If I find anything I will be sure to pass it on. Also, as I am not a seismologist, I don't know if this is a horrible idea but can the missing components from a sensor be simulated easily from single component data? |
@Bryanrt-geophys thanks. No simulation is not easy. Jut try downloading the same data using Obspy and see if you get those missing traces. |
I am running a download using a channel filter (I think anyways). I use the following.
channel_list=["HH[ZNE12]"]
However, I returned in the json file in json/ is the complete list of channels at a station. For example,
Can you please explain the behavior of channel_list to me? I am writing some other code to build a station file for hypoinverse from the json file, but the fact that there are these extra channels is screwing things up for me. I did update EQTransformer code today, so I am using EQTransformer==0.1.61.
Thanks!
The text was updated successfully, but these errors were encountered: