-
Notifications
You must be signed in to change notification settings - Fork 54
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
Make S and P wave speed user provided parameter in BCs #183
Comments
sveerara
added a commit
to sveerara/mastodon
that referenced
this issue
Dec 7, 2018
…ce and non reflecting BC idaholab#183
sveerara
added a commit
to sveerara/mastodon
that referenced
this issue
Dec 7, 2018
…ce and non reflecting BC idaholab#183
sveerara
added a commit
to sveerara/mastodon
that referenced
this issue
Dec 9, 2018
…ce and non reflecting BC idaholab#183
aeslaughter
added a commit
to aeslaughter/mastodon
that referenced
this issue
Dec 23, 2019
aeslaughter
added a commit
to aeslaughter/mastodon
that referenced
this issue
Dec 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently either ComputeIsotropicElasticityTensorSoil or ComputeISoilStress computes the wave speed within the soil domain and the same value is used at the boundary. In this method, the user has to create a separate elastic layer with bedrock material properties in order to set the wave speeds at the base of a nonlinear soil column to bedrock wave speeds.
To avoid this extra meshing effort, it is better for the user to provide the wave speeds for the SeismicForce and NonReflectingBC than using the values computed in either the linear or nonlinear soil.
The text was updated successfully, but these errors were encountered: