You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The call in main.py to write_closure_info_to_log() is hardwired to pass on the second, third, and fourth angle. That looks like a remnant from the past where the code assumed the user always specified three angles in the configuration file and the code padded those with a 0- and 45-degree response. I suggest changing
Note, that this is not guaranteed to give good results if the user specifies just one angle in the configuration file.
I am now seeing that I sometimes still get 5 angles in rfc_raw when I specify 3 in the configuration file. In that case my fix above does not work because the code is now trying to match 5 RFCs with 3 angles.
I need to figure out why I sometimes get 3 and other times 5 angles in rfc_raw...
The text was updated successfully, but these errors were encountered:
@geokefe this is not the right place to ask that question.
Anyway, there is a 'notebook' folder that show exactly how to use synthoseis in a Jupyter notebook.
The call in main.py to write_closure_info_to_log() is hardwired to pass on the second, third, and fourth angle. That looks like a remnant from the past where the code assumed the user always specified three angles in the configuration file and the code padded those with a 0- and 45-degree response. I suggest changing
closures.write_closure_info_to_log(seismic.rfc_raw[1:4, ...])
to
closures.write_closure_info_to_log(seismic.rfc_raw[:, ...])
Note, that this is not guaranteed to give good results if the user specifies just one angle in the configuration file.
I am now seeing that I sometimes still get 5 angles in rfc_raw when I specify 3 in the configuration file. In that case my fix above does not work because the code is now trying to match 5 RFCs with 3 angles.
I need to figure out why I sometimes get 3 and other times 5 angles in rfc_raw...
The text was updated successfully, but these errors were encountered: