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.

Sign up for GitHub

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

Jump to bottom

FancyExtruderGenerator removes the partitioner #18696

Closed
GiudGiud opened this issue Aug 25, 2021 · 2 comments
Closed

FancyExtruderGenerator removes the partitioner #18696

GiudGiud opened this issue Aug 25, 2021 · 2 comments
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.

Comments

@GiudGiud
Copy link
Contributor

GiudGiud commented Aug 25, 2021 •
edited

Bug Description

The fancy extruder generator starts from a new mesh base and never copies over the input partitioner, nor changes the mesh base for the partitioner.
So the partitioner is gone. And MOOSE is unhappy

Since neither operation (changing partitioner of a mesh, changing mesh base of a partitioner) are currently possible in libmesh, I think the partitioner needs to be created later with the final mesh generator mesh?
Rn the order of execution:

[DBG][ACT] TASK (         add_partitioner) TYPE (               PartitionerAction) NAME (     Partitioner) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (            core) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (         extrude) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (boundary_removal) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (     boundaries1) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (     boundaries2) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (     boundaries3) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (     boundaries4) Memory usage 42MB
[DBG][ACT] TASK (      add_mesh_generator) TYPE (          AddMeshGeneratorAction) NAME (     boundaries5) Memory usage 42MB

thoughts @friedmud ?

Steps to Reproduce

Try to use both a Partitioner and a FancyExtruderGenerator

Impact

Stopping me from running BEAVRS
@GiudGiud GiudGiud added T: defect An anomaly, which is anything that deviates from expectations. P: normal A defect affecting operation with a low possibility of significantly affects. labels Aug 25, 2021
friedmud added a commit to friedmud/moose that referenced this issue Aug 30, 2021
@friedmud
Fix custom partitioning with generators refs idaholab#18696
d65d0f8
friedmud added a commit to friedmud/moose that referenced this issue Aug 30, 2021
@friedmud
Fix custom partitioning with generators refs idaholab#18696
507d845
@friedmud friedmud mentioned this issue Aug 30, 2021
Merged
friedmud added a commit to friedmud/moose that referenced this issue Aug 31, 2021
@friedmud
Fix custom partitioning with generators refs idaholab#18696
0aa2e56
@GiudGiud
Copy link
Contributor Author

Fixed by #18696

@friedmud
Copy link
Contributor

friedmud commented May 3, 2022

I think you mean #18735 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@friedmud @loganharbour @GiudGiud