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

refactor: trying to improve the constitutive allocation message #3511

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

paveltomin
Copy link
Contributor

updated output looks like this:

meshBodyName/meshLevelName/regionName/subRegionName = mesh/Level0/barrier/cb-0_0_2, 8 quadrature points
  ConstitutiveModels/fluid allocated
  ConstitutiveModels/porousRockBarrier allocated
  ConstitutiveModels/skeletonBarrier allocated
  ConstitutiveModels/rockPorosityBarrier allocated
  ConstitutiveModels/rockPermBarrier allocated
  ConstitutiveModels/relperm allocated
meshBodyName/meshLevelName/regionName/subRegionName = mesh/Level0/wellRegion1/wellRegion1UniqueSubRegion, 1 quadrature point
  ConstitutiveModels/fluid allocated
  ConstitutiveModels/relperm allocated

@paveltomin paveltomin self-assigned this Jan 11, 2025
@paveltomin paveltomin changed the title refact: trying to improve the constitutive allocation message refactor: trying to improve the constitutive allocation message Jan 11, 2025
group = constitutiveGroup->registerGroup< ConstitutiveBase >( subRelationName, std::move( constitutiveModel ) );
group.setSizedFromParent( 1 );
group.resize( constitutiveGroup->size() );
hangConstitutiveRelation( subRelationName, parent, numConstitutivePointsPerParentIndex );
Copy link
Contributor

Choose a reason for hiding this comment

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

This recursive call potentially goes deeper than the original code. Are we sure it will terminate?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good point, i am sure it will terminate but not sure what way is correct
@rrsettgast @CusiniM could you please confirm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants