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

Need for some tips on setting parameters #30

Open
saeedsltm opened this issue Mar 27, 2023 · 6 comments
Open

Need for some tips on setting parameters #30

saeedsltm opened this issue Mar 27, 2023 · 6 comments

Comments

@saeedsltm
Copy link

Since there is no any document ready until now, It would be helpful to give us some tips and notes on how to select best parameters controling the final results. It seems the following are the most important ones that should be choosen with care while working in local or regional scales:

  • dbscan_eps
  • dbscan_min_samples
  • max_sigma11
  • any other?
    Thanks.
@zhuwq0
Copy link
Contributor

zhuwq0 commented Mar 27, 2023

Hi, these parameters are explained in the README file.

@saeedsltm
Copy link
Author

Yes, the definitions are provided, but how to select their optimized values? should we do it by try and error?

@zhuwq0
Copy link
Contributor

zhuwq0 commented Mar 27, 2023

There are always some trade-offs: number of detections and false positive rate; speed and accuracy. This depends on your focus.

@saeedsltm
Copy link
Author

I ran the code in one day continus data for the Turkey-Syria earthquakes (2023-02-06 7.8Mw & 7.5Mw) and it almost done. The P and S picks for small quakes are well idetified, detected and associated. The only problem is that the output catalog does not contain large events (like M> 5).
Shoud we consider different range of parameters:
These are what i have used:

  • dbscan_eps = 15
  • dbscan_min_samples=3
  • min_picks_per_eq=6
  • max_sigma11=1.5

@zhuwq0
Copy link
Contributor

zhuwq0 commented Apr 3, 2023

Hi, first I would check how many picks available for these large events in the input data; secondly for debugging, I would make max_sigma11 very large to remove filtering.

@saeedsltm
Copy link
Author

saeedsltm commented Apr 5, 2023

Hi, following your suggestion i increased max_sigma11 to 2.5s. Now a strange situation has occured!:

  • Choosing a narrow time window ( 15 min) for the whole processing (picking + association) results in dtecting more events in which previously missed.
  • Choosing a broader time window ( 60 min) for the whole processing (picking + association) causes once again some events to be missed (not accosiated).

Do you have any idea? I also increased dbscan_eps to 20, but still missing some large events while working with 60 min time window.

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

2 participants