-
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
Associating Sparse Network with GaMMA #50
Comments
Hi, I am working with a similarly small network (5 stations). Here are my parameters, naturally the x, y, and z in the config are going to be different for you. I would recommend still playing around with the min_picks_per_eq parameter as well. Mine is currently set to 5, but you may need a lower threshold for only three stations. Are you getting phases for all three of your stations? You may also need to increase dbscan_eps if the distance between the stations is fairly large, or turn off dbscan entirely. Good luck! Gammaconfig = {} DBSCANconfig["bfgs_bounds"] = ( Filteringconfig["min_picks_per_eq"] = 5 # 4 has many more events, but 5 seems to have a lot fewer mislocations |
@SquirrelKnight Thank you for explaining the issue! That is correct. GaMMA is basically a clustering method following traveltime/ground-motion relationships. It is not limited by the number of stations, while clustering is a bit sensitive to the hyper parameters. |
Hello,
I was curious if GaMMA is able to associate phase picks obtained from a very sparse network composed of 3 instruments?
I have good phase picks acquired from PhaseNet, however when I try to associate the events GaMMA yields the dreaded -1 event index for phase arrivals and generates no catalogs. I've played around with the parameters extensively with all tests resulting the same.
Is GaMMA limited by the number of stations and/or the spatial footprint of the network?
Thank you!
The text was updated successfully, but these errors were encountered: