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

[GeoMechanicsApplication] Phreatic error with discontinuous geometry #10290

Closed
EleniSmyrniou opened this issue Sep 20, 2022 · 4 comments · Fixed by #11184
Closed

[GeoMechanicsApplication] Phreatic error with discontinuous geometry #10290

EleniSmyrniou opened this issue Sep 20, 2022 · 4 comments · Fixed by #11184
Assignees
Labels
GeoMechanics Issues related to the GeoMechanicsApplication

Comments

@EleniSmyrniou
Copy link
Contributor

EleniSmyrniou commented Sep 20, 2022

As a user, I would like to be able to apply a multiple-point phreatic line, such that I can model water pressure fields.

Description

When multiple phreatic lines are assigned to a surface it seems that the first point in the left is always extrapolated to the right. As it can be seen in the figures bellow.

image

image

Acceptance Criteria

@EleniSmyrniou EleniSmyrniou added the GeoMechanics Issues related to the GeoMechanicsApplication label Sep 20, 2022
@EleniSmyrniou
Copy link
Contributor Author

EleniSmyrniou commented Sep 21, 2022

The problem can be found in apply_scalar_constrain_table_process.py in function CalculatePressure.
In this case when the node is outside of the phreatic line the pressure gets extrapolated. This makes assigning different phreatic lines in the same surface order dependent

` double CalculatePressure(const Node<3> &rNode, const array_1d<double, 2> &y) const
{
double height = 0.0;
if (rNode.Coordinates()[mHorizontalDirection] >= mMinHorizontalCoordinate && rNode.Coordinates()[mHorizontalDirection] <= mMaxHorizontalCoordinate) {
height = mSlope * (rNode.Coordinates()[mHorizontalDirection] - mFirstReferenceCoordinate[mHorizontalDirection]) + y[0];

    } else if (rNode.Coordinates()[mHorizontalDirection] < mMinHorizontalCoordinate) {
        height = mSlope * (mMinHorizontalCoordinate - mFirstReferenceCoordinate[mHorizontalDirection]) + y[0];

    } else if (rNode.Coordinates()[mHorizontalDirection] > mMaxHorizontalCoordinate) {
        height = mSlope * (mMaxHorizontalCoordinate - mFirstReferenceCoordinate[mHorizontalDirection]) + y[0];
    }

    const double distance = height - rNode.Coordinates()[mGravityDirection];
    const double pressure = - PORE_PRESSURE_SIGN_FACTOR * mSpecificWeight * distance;
    return pressure;
}`

@mcgicjn2 mcgicjn2 self-assigned this Sep 30, 2022
@mcgicjn2
Copy link
Contributor

Fixed for constant pressure

image

@mcgicjn2
Copy link
Contributor

Also added phreatic multi line table process .... i.e. varies in time

@mcgicjn2
Copy link
Contributor

mcgicjn2 commented Jul 7, 2023

The PR was closed so that @WPK4FEM and @avdg81 can complete there changes to the underlying functionalities before reimplementation.

@rfaasse rfaasse self-assigned this Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GeoMechanics Issues related to the GeoMechanicsApplication
3 participants