-
Notifications
You must be signed in to change notification settings - Fork 96
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
Negative porosities when using poroelastic material with state variables #658
Comments
Is the porosity a function of other variables? If so, which ones and how are they updated? Pointing me to code is fine. |
The update of the porosity (plane strain) is in |
I'm not 100% sure if this is the place but I see it in IsotropicLinearPoroelasticity.hh at line 2488 |
We should put in an assert there for negative porosity, or a clamp |
The porosity should only be between 0 and 1, so I think a clamp makes sense! |
I agree.
…On Fri, Sep 29, 2023, 11:36 Daniel Douglas ***@***.***> wrote:
The porosity should only be between 0 and 1, so I think a clamp makes
sense!
—
Reply to this email directly, view it on GitHub
<#658 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJY33TFKLO64QDATY6XM2DX44IKVANCNFSM6AAAAAA5MXRBGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Fixed in branch |
Describe the bug
When using poroelasticity and state variables, the porosity field can develop
To Reproduce
PETSc branch: knepley/pylith
PyLith fork: https://github.com/baagaard-usgs/pylith.git
PyLith branch: baagaard/example-poroelasticity-statevars
Steps to reproduce the behavior.
pylith step01_elastic_bending.cfg
Expected behavior
The porosity as a physical parameter should not be negative,
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Please provide the following information:
Additional context
Add any other context about the problem here.
step01_elastic_bending.txt
variable_permeability.txt
pylithapp copy.txt
top_boundary.txt
The text was updated successfully, but these errors were encountered: