-
Notifications
You must be signed in to change notification settings - Fork 31
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
Comments
Hi, these parameters are explained in the README file. |
Yes, the definitions are provided, but how to select their optimized values? should we do it by try and error? |
There are always some trade-offs: number of detections and false positive rate; speed and accuracy. This depends on your focus. |
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).
|
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. |
Hi, following your suggestion i increased max_sigma11 to 2.5s. Now a strange situation has occured!:
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. |
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:
Thanks.
The text was updated successfully, but these errors were encountered: