Receiver Function not running effectively

[Munatmum]

The local data use is an earthquake event in Saudi Arabia Kingdom. (The data wasn't downloaded online, it was obtained from a professor)
I also need clarification on maybe the 3 components (HHZ, HHE, HHN) for each station would be saved separately as different 3 mseed files or as a single mseed file

[aolivarc]

Hi Munatmum. So I gather that the output contains no earthquakes, as all are discarded for being out of your selected depth range. First, please try to cut the events while setting both min. and max. depths to 0, and check the output again. I have added the depth of the preferred origins to the terminal output, so if you update the codes you should now be able to see them, to check if they truly are out of range.

Regarding your question, the three components should be saved separately and there should not be more than one file per day. Ensure that your data covers the entire timespan of the catalog.

[Munatmum]

Thanks for the prompt response @aolivarc , Setting min. and max. depths to 0 still return same output all the waveforms were discarded.
I downloaded some event from IRIS database to try ISP on new dataset, although .h5 output was created and station ANMO display when I read waveform for rf analysis but it return indexError upon clicking compute rf button.
[ Traceback (most recent call last):
File "/home/munat/ISP/isp/Gui/Frames/receiver_functions_frame.py", line 296, in compute_rfs
self.rfs = mwu.compute_rfs(stnm, self.hdf5_waveforms,
File "/home/munat/ISP/isp/receiverfunctions/rfun_main_window_utils.py", line 355, in compute_rfs
e = arr[np.where(hdf5_file[stnm][event_id].attrs["data_structure"] == "E")[0][0]]
IndexError: index 0 is out of bounds for axis 0 with size 0]

My deduction; could it be that the earthquake data I have weren't present in IRIS catalog.

Thanks, I'll await you response

[aolivarc]

Thanks for the info @Munatmum, it seems that the problem with the depths is just one of units, as they seem to be reported in meters. I will add some lines to handle this.

The error that you get afterwards means that there is no E component for one of the events, I will also look into modifying the function so it does not break when this kind of problem happens (but it should not happen, it's a data problem). It's difficult to tell what could be wrong without having a look at the actual data that you have, and the settings you have used for ANMO (I think your screenshot of the menu belongs to the first log). I would not set such a low minimum magnitude, as you will download a very large catalog with a high number of events that will not even be registered at the stations.

Then yes, ensure that your data covers the timespan of the catalog, as there are a few warnings saying that there is no data or that there are gaps for a few events that do pass all of the other filters (see your first log). May I ask why are you focusing on this very short timespan of 10 minutes? It seems unlikely that you will have enough results there to work with these codes.