-
Notifications
You must be signed in to change notification settings - Fork 91
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
refactor: fields and constitutives #3517
base: develop
Are you sure you want to change the base?
Conversation
@@ -250,22 +249,19 @@ void CompositionalMultiphaseBase::registerDataOnMesh( Group & meshBodies ) | |||
} | |||
|
|||
// If at least one region has a capillary pressure model, consider it enabled for all | |||
string const capPresName = getConstitutiveName< CapillaryPressureBase >( subRegion ); | |||
if( !capPresName.empty() ) | |||
if( !getConstitutiveName< CapillaryPressureBase >( subRegion ).empty() ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if( !getConstitutiveName< CapillaryPressureBase >( subRegion ).empty() ) | |
m_hasCapPressure = !getConstitutiveName< CapillaryPressureBase >( subRegion ).empty(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this would change the logic, i committed first but now will revert
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about m_hasCapPressure |= !getConstitutiveName< CapillaryPressureBase >( subRegion ).empty();
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MelReyCG done, could you please approve?
@@ -228,8 +229,6 @@ void CompositionalMultiphaseBase::postInputInitialization() | |||
|
|||
void CompositionalMultiphaseBase::registerDataOnMesh( Group & meshBodies ) | |||
{ | |||
using namespace fields::flow; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious as to why we are removing this. Is this part of the coding standard?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
using namespace fields
already defined in the very beginning of the file, so no need to duplicate it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i am not sure if there is a coding standard about that, just trying to make things consistent across the solvers
…phaseBase.cpp Co-authored-by: Dickson Kachuma <81433670+dkachuma@users.noreply.github.com>
setRestartFlags( RestartFlags::NO_WRITE ). | ||
setSizedFromParent( 0 ); | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, what is the need for PhysicsSolverBase::setConstitutiveNamesCallSuper...
why was this removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i am not exactly sure about the logic behind, i think it originates from this big PR #1682
fluidNames
registration moved somewhere else (next to its assignement), so this function becomes redundant
clean up fields and constitutive "registration"