Skip to content
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

wrong label data of back_azimuth_deg #8

Closed
Seismic-wave-Han opened this issue Nov 27, 2021 · 4 comments
Closed

wrong label data of back_azimuth_deg #8

Seismic-wave-Han opened this issue Nov 27, 2021 · 4 comments

Comments

@Seismic-wave-Han
Copy link

Seismic-wave-Han commented Nov 27, 2021

Hello.
I'm Sangwoo Han in Seismology, Geophysics and Tectonophysics Lab in Seoul National Univ. in South Korea.
First of all, thank you for your effort to make a very cool global benchmark dataset.

I found some problems in the label data of 'back_azimuth_deg'.
There are some 180-degree differences between 'back_azimuth_deg' in STEAD and back-azimuth obtained using locations of source and receiver.
I download STEAD data from mega cloud link.
I attached an image of back-azimuth differences.
figure

Also, I gave you one example of this problem.

  • Trace name: 'AKGG.AV_20060814223729_EV'

I used function gps2dist_azimuth() from obspy.geodetics.base to get back-azimuth.
I also want to know the formula that you used to calculate 'back_azimuth_deg'
Please check this problem and could you reply to this?

@smousavi05
Copy link
Owner

Hi @Seismic-wave-Han , you are right. The reported value for 'AKGG.AV_20060814223729_EV' is azimuth not the back azimuth.I used the same function from Obspy. And this is how it was calculated during the compiling of the dataset:

            distanceKm, azimuth, back_azimuth = obspy.geodetics.base.gps2dist_azimuth(
                                                                        float(event_lat), 
                                                                        float(event_lon),
                                                                        float(station_lat), 
                                                                        float(station_lon), 
                                                                        a=6378137.0, 
                                                                        f=0.0033528106647474805)
            distanceKm = (distanceKm/1000);
            distance = round((distanceKm / 111), 4);
            back_azimuth = round(back_azimuth, 4)

However, I haven't figured out what went wrong yet. I checked the station lat and long and they are correct. So no flipping of the event-station coordinates. Could you tell me how many of these you found in the dataset?

@Seismic-wave-Han
Copy link
Author

Seismic-wave-Han commented Nov 29, 2021

Hi @smousavi05. I prepared some figures related to the error of back-azimuth (also, distance)
baz_error
baz_error_hist
These figures are the back-azimuth error along with whole samples and their histogram.
Samples with errors in the 170-190 degree range are 8% of the total.

I also found the distance discrepancy with obspy.
dist_error
The error of distance is nearly zero, but it shows quite a large error for some samples.
I hope this information will help you find systematic errors in STEAD.

@smousavi05 smousavi05 pinned this issue Apr 14, 2022
@Rohit-Tomar
Copy link

I have downloaded all the chunks of the dataset and trying to run the code but not getting the image folder in the dataset. Can you please help

@smousavi05
Copy link
Owner

smousavi05 commented May 5, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants