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

[Core] Consistency between Element/Condition and Node clone #4795

Open
loumalouomega opened this issue May 6, 2019 · 8 comments
Open

[Core] Consistency between Element/Condition and Node clone #4795

loumalouomega opened this issue May 6, 2019 · 8 comments

Comments

@loumalouomega
Copy link
Member

loumalouomega commented May 6, 2019

The clone of the node does not consider new Id:

typename Node<TDimension>::Pointer Clone()

But the condition and element does:

virtual Pointer Clone (IndexType NewId, NodesArrayType const& ThisNodes) const

Maybe we should discuss this inconsistency

@loumalouomega
Copy link
Member Author

I think this discussion is still valid

@loumalouomega
Copy link
Member Author

I think this discussion is still valid

@KratosMultiphysics/technical-committee

@roigcarlo
Copy link
Member

@loumalouomega We are currently considering options to "merge" elements and conditions. As long as the PR is ready we will ping everyone.

In the meantime, I agree with you, its odd that they have different interfaces :S

@loumalouomega
Copy link
Member Author

@loumalouomega We are currently considering options to "merge" elements and conditions. As long as the PR is ready we will ping everyone.

In the meantime, I agree with you, its odd that they have different interfaces :S

It is nice to unify elements and conditions, as implementation is 99.9% identical. In any case, this discussion is still valid.

@pooyan-dadvand
Copy link
Member

@KratosMultiphysics/technical-committee don't see any reason for having the Clone method for the node as we don't derive from it. So we propose to remove the Clone of the node (and implicitly we don't have inconsistency anymore)

@RiccardoRossi
Copy link
Member

@loumalouomega is this still a relevant PR in view of eventually removing the clone of the node?

@loumalouomega
Copy link
Member Author

There is a PR, where this is discussed as well

@loumalouomega
Copy link
Member Author

There is a PR, where this is discussed as well

#11286

(@RiccardoRossi you contributed recently there)

@RiccardoRossi RiccardoRossi moved this from 🏗 In progress to 🔖 Ready in Technical Commiittee Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🔖 Ready
Development

No branches or pull requests

4 participants