Skip to content

[GeoMechanicsApplication] Remove two unused piping interface elements#13628

Merged
avdg81 merged 2 commits intomasterfrom
geo/remove-unused-piping-elements
Jul 15, 2025
Merged

[GeoMechanicsApplication] Remove two unused piping interface elements#13628
avdg81 merged 2 commits intomasterfrom
geo/remove-unused-piping-elements

Conversation

@avdg81
Copy link
Contributor

@avdg81 avdg81 commented Jul 14, 2025

📝 Description
Removed elements "SteadyStatePwPipingElement3D6N" and "SteadyStatePwPipingElement3D8N", since they were unused. In fact, they couldn't be used, since two parts of their implementation (CalculateLength and CalculateHeadGradient) would unconditionally raise an error.

@avdg81 avdg81 self-assigned this Jul 14, 2025
@avdg81 avdg81 requested a review from a team as a code owner July 14, 2025 12:44
@avdg81 avdg81 added the GeoMechanics Issues related to the GeoMechanicsApplication label Jul 14, 2025
@avdg81 avdg81 requested a review from rfaasse July 14, 2025 12:44
Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this clean-up! I don't see any issues here, I just want to check if these old interface-based piping elements (3D6N and 3D8N) are also not used by anyone else (I can't imagine, because it seems they were indeed unusable due to certain functionality not being implemented, but just double-checking).

Comment on lines -126 to -140
template <>
void SteadyStatePwPipingElement<3, 6>::CalculateLength(const GeometryType& Geom)
{
KRATOS_ERROR << " Length of SteadyStatePwPipingElement3D6N element is not "
"implemented"
<< std::endl;
}

template <>
void SteadyStatePwPipingElement<3, 8>::CalculateLength(const GeometryType& Geom)
{
KRATOS_ERROR << " Length of SteadyStatePwPipingElement3D8N element is not "
"implemented"
<< std::endl;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these always called in a piping calculation? Or is it similar to e.g our interface geometry, where we might say: length is not implemented for a surface interface?

Comment on lines -265 to -283
template <>
double SteadyStatePwPipingElement<3, 6>::CalculateHeadGradient(const PropertiesType& Prop,
const GeometryType& Geom,
double dx)
{
KRATOS_ERROR << " head gradient calculation of "
"SteadyStatePwPipingElement3D6N element is not implemented"
<< std::endl;
}

template <>
double SteadyStatePwPipingElement<3, 8>::CalculateHeadGradient(const PropertiesType& Prop,
const GeometryType& Geom,
double dx)
{
KRATOS_ERROR << " head gradient calculation of "
"SteadyStatePwPipingElement3D8N element is not implemented"
<< std::endl;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, is this function always called in a piping calculation?

@github-project-automation github-project-automation bot moved this from In progress to Reviewer approved in GeoMechanicsApplication (Deltares) Jul 14, 2025
@avdg81 avdg81 requested a review from mcgicjn2 July 14, 2025 13:36
@avdg81 avdg81 merged commit f05d0a1 into master Jul 15, 2025
10 checks passed
@avdg81 avdg81 deleted the geo/remove-unused-piping-elements branch July 15, 2025 09:06
@github-project-automation github-project-automation bot moved this from Reviewer approved to Done in GeoMechanicsApplication (Deltares) Jul 15, 2025
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

Development

Successfully merging this pull request may close these issues.

2 participants