feature support specfem3d globe #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…_globe working directory and adjoint simulation included laplacian smoothing wrapper and allow user choice between gaussian and laplacian smoothing
…ed to figure out the intricacies of dealing with multiple regions and whether or not they are updated, which will affect the available kernels, but model reading for 3D globe as well as flavor guessing has been added
…del class. Now allows for user-definition of region for building model, and can read and write globe models which have a different format from specfem2d and 3d models
…inherited from specfem3d
… as we assume we only need text files
…els, also deals with all anisotropic model parameters
…ore general in the check statement
… which is 3dglobe only. this is used to deal with different regions in 3d globe models
… a wip but not used
…tencies between specfem3d and 3d_globe that make it difficult to have 3d as parent to 3d_globe. need to make some larger scale changes to incorporate
…onto specfem parent class
… 3d_globe and 2d/3d have
…to break vector into model defintion
…s in line with how specfem3d_globe expects them
…tion to more dynamically find appropriate kernels generated by an adjoint simulation. the previous form of attempting a broad wildcard ended up grabbing undesired files
…odels also specfem3d_globe model files was empty due to incorrect wildcard searching
…be. 3d_globe now treats region + parameter as a single parameter, meaning it can use the original model implementation mechanics
…egions as part of parameters rather than a separate variable
…tag for parameter input
…a loop infinitely until OOM killed process. fixed this by statically generating acceptable parameter list at the top of the Model class, not with a loop in the init statement. also threw a warning in there for specfem2d models that can't find coordinate files, rather than crashing out with an assertion error
…er than dynmically grabbing from user input parameter
This was referenced Nov 24, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds SPECFEM3D_GLOBE support to SeisFlows. Addresses some key differences between SPECFEM3D and 3D_GLOBE versions which required some re-tooling of SeisFlows. Major differences include:
This resulted in a re-tooled Model class (to allow for the 'regions' in the globe code), expansion on the previously unfinished specfem3d_globe solver class, and some generalization of workflow code to deal with some 3D and 3D_GLOBE differences.
This was successfully tested on Chinook04 (t1small partition) for a 1 event, 1 iteration inversion. All tests passing.
Relevant Issue: #141