Closed sxyzy1016 closed 5 months ago
Hi! Please see BEAT FAQ here: https://pyrocko.org/beat/docs/current/faq.html Your issues is number 5/6, which are the same but for different data types. From what I can see in your case - it is at least the deoth grid, so please increase source_depth_max to at least 30km, better give a little buffer maybe 35km. Depending on your data and the distance of your furthest data point to the source, you may also need to increase source_distance_radius. Up and better higher than the longest distance. Cheers! Hannes
Hi!
Thanks a lot for your advice. And sorry for my late response.
I tried lots of times these days, increasing source_depth_max
and source_distance_radius
, even an extremly high value like 300
and 1000
, but the issue still occured. The INDEX_OUT_OF_BOUNDS
poped up immediately after the log geodetic - INFO Retrieving geodetic data-covariances with structure "import" for insar6_2
.
I also tried decreasing the upper value of depth
in the prior
, but no help.
And my InSAR deformation data is like:
Please see the last two sentences of my previous response.
Please re-open in case issue still exists.
Hi there,
I was trying to calculate the geometry Rec-source using geodetic InSAR data as a practice. I was just following the Example 3 Laquila in the document but without waveform data and just geodetic data.
What I did was:
beat init some_proj
beat import some_proj
, andgeodetic_data.pkl
was created succefully.beat build_gfs some_proj --datatypes=geodetic
andbeat build_gfs some_proj --force --execute
, and everything seems ok.beat some_proj --parameters="hierarchicals,hypers"
And then in the follow step
beat sample turkey2023 --hypers
I run intopyrocko.gf.store_ext.StoreExtError: INDEX_OUT_OF_BOUNDS
. The full trace is here:I thought it was a problem of my data format, so I compared my
geodetic_data.pkl
with the example 3 in spyder, but I got no idea.I am newbie to this study area. Really need your help... OTL
The final config yaml used in this step was: