Skip to content
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

Feature: allow acoustic domain and pressure seismograms (specfem2d) #164

Merged
merged 4 commits into from
Mar 8, 2023

Conversation

bch0w
Copy link
Member

@bch0w bch0w commented Mar 8, 2023

Related to #151

SeisFlows was not completely tooled to deal with pressure seismograms and acoustic domains. Especially in SPECFEM2D when seismogram file naming can change enough to fail wildcard matching under certain conditions. This PR improves SeisFlows support for dealing with acoustic domains and pressure seismograms.

Changelog:

  • Parameter components (used by: solver.specfem and preprocess.pyaflowa) now defaults to NoneType. Previously it was set as 'ZNE'. This makes the default behavior of SeisFlows wildcard searing more general/forgiving
  • Made the solver.specfem.data_wildcard() function wildcard search for seismograms much more general to be able to catch all the different types of ASCII and SU filenames that SPECFEM2D might generate
  • Default preprocessing module now allows pressure seismograms, requiring that unit_output='PRE'. Before, pressure seismograms were not an acceptable unit output.

To use acoustic domain and pressure seismogram a User will first need to set up their SPECFEM2D Par_file:

seismotype = 4

and their SeisFlows YAML file:

materials: acoustic
unit_output: pre
components: null

bch0w added 4 commits March 8, 2023 12:53
…t to wildcard searching, which is probably a better default behavior.

this affects specfem solver and pyaflowa preprocessing classes
…eral so that it can catch the different naming schema that come out of specfem2d
@bch0w bch0w merged commit c16f7e4 into devel Mar 8, 2023
@bch0w bch0w deleted the feature-acoustic_domain branch March 8, 2023 22:35
@bch0w bch0w mentioned this pull request Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant