Let users specify which blocks to keep in BlockDeletionGenerator

[travismui]

Motivation

Sometimes you might only know which blocks you want to keep, or that list might be shorter than the blocks you need to remove from a given mesh. This can be done by a combination with ParsedSubdomainMeshGenerator, but the process could be simplified entirely within BlockDeletionGenerator.

Design

As suggested by @YaqiWang, follow the example in BoundaryDeletionGenerator for consistency:

  MooseEnum opt("keep remove", "remove");
  params.addParam<MooseEnum>("operation", opt, "Whether to remove or keep the listed boundaries");

Add a keep_blocks = true flag to BlockDeletionGenerator so that the user-defined blocks parameter can specify the blocks you want to keep and delete everything else from input.

Impact

New feature, added convenience.

[aprilnovak]

Is anyone working on this issue? This is a good one for training a student, we will take it if it's available :)

[travismui]

@aprilnovak I haven’t gotten around to this yet, so please feel free to take this one. Thanks!

[aprilnovak]

Thanks @travismui ! I don't have permissions to assign this to anyone, but you can assign to @MariaReji03

[YaqiWang]

Just to let you know that in BoundaryDeletionGenerator, we had this parameter

  MooseEnum opt("keep remove", "remove");
  params.addParam<MooseEnum>("operation", opt, "Whether to remove or keep the listed boundaries");

which you may want to use in BlockDepletionGenerator for code consistency.

[lindsayad]

I think @MariaReji03 will need to comment here before I can assign them. GitHub is not allowing me to assign them at present. Must only allow participants

[MariaReji03]

Hi, you can assign this one to me