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
I've been using SeisFlows to set up a 2D elastic example, but I've run into an issue. The files in scratch/solver/mainsolver/traces/adj are being generated with two different filename patterns. One file follows the *BXX.adj pattern but is empty, while the rest follow the *HX*.adj or *MX*.adj pattern. However, the output generated from SPECFEM2D uses the *BX*.semd naming convention.
This discrepancy is causing my inversion to fail because SeisFlows reads the empty *BXX.adj file. I'm unsure why, even though the SPECFEM outputs are in the BX* name format, the adjoint files are generated with a different naming convention.
Thank you for your assistance.
The text was updated successfully, but these errors were encountered:
Hello,
I've been using SeisFlows to set up a 2D elastic example, but I've run into an issue. The files in
scratch/solver/mainsolver/traces/adj
are being generated with two different filename patterns. One file follows the*BXX.adj
pattern but is empty, while the rest follow the*HX*.adj
or*MX*.adj
pattern. However, the output generated from SPECFEM2D uses the*BX*.semd
naming convention.This discrepancy is causing my inversion to fail because SeisFlows reads the empty
*BXX.adj
file. I'm unsure why, even though the SPECFEM outputs are in theBX*
name format, the adjoint files are generated with a different naming convention.Thank you for your assistance.
The text was updated successfully, but these errors were encountered: