SurfaceMeshBySubdomainBuilder

SurfaceMeshBySubdomainBuilder prepares the geometric data structures used by PointInSubdomainCheckUO for per-subdomain in-out testing. It processes a source surface mesh, identified by the surface_mesh parameter, and groups its boundary elements into one SurfaceElementSet per subdomain ID. The per-subdomain sets are exposed for reuse by other objects in the simulation.

As a subclass of BoundaryMeshBuilder, it retrieves and validates the saved surface mesh: the mesh must be replicated (serial), and its dimension must be one less than the embedding mesh (e.g., a 2-D surface within a 3-D mesh). The KDTree used for nearest-neighbor queries is not built here; it is constructed by the consuming in-out tester (PointInSubdomainCheckUO) from these sets.

Usage

Set surface_mesh to the name under which the surface mesh was stored using the MeshGenerator save_with_name parameter. The replicated-mesh check is always performed. Because the boundary loops must be closed for a reliable in-out test, consider enabling check_watertightness when preparing a new mesh.

Builds one SurfaceElementSet per subdomain from a given surface mesh.

Input Parameters

surface_meshThe name of the surface mesh saved via the MeshGenerator's `save_with_name` parameter.
C++ Type:std::string
Controllable:No
Description:The name of the surface mesh saved via the MeshGenerator's `save_with_name` parameter.

Required Parameters

check_watertightnessFalseCheck if the mesh is watertight. If false, the mesh may not be suitable for In-Out tests.
Default:False
C++ Type:bool
Controllable:No
Description:Check if the mesh is watertight. If false, the mesh may not be suitable for In-Out tests.

Optional Parameters

allow_duplicate_execution_on_initialFalseIn the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).
Default:False
C++ Type:bool
Controllable:No
Description:In the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).
execute_onTIMESTEP_ENDThe list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html.
Default:TIMESTEP_END
C++ Type:ExecFlagEnum
Options:XFEM_MARK, FORWARD, ADJOINT, HOMOGENEOUS_FORWARD, ADJOINT_TIMESTEP_BEGIN, ADJOINT_TIMESTEP_END, NONE, INITIAL, LINEAR, LINEAR_CONVERGENCE, NONLINEAR, NONLINEAR_CONVERGENCE, POSTCHECK, TIMESTEP_END, TIMESTEP_BEGIN, MULTIAPP_FIXED_POINT_END, MULTIAPP_FIXED_POINT_BEGIN, MULTIAPP_FIXED_POINT_CONVERGENCE, MULTISYSTEM_FIXED_POINT_ITERATION_END, FINAL, CUSTOM, TRANSFER
Controllable:No
Description:The list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html.
execution_order_group0Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.
Default:0
C++ Type:int
Controllable:No
Description:Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.
force_postauxFalseForces the UserObject to be executed in POSTAUX
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in POSTAUX
force_preauxFalseForces the UserObject to be executed in PREAUX
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in PREAUX
force_preicFalseForces the UserObject to be executed in PREIC during initial setup
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in PREIC during initial setup

Execution Scheduling Parameters

control_tagsAdds user-defined labels for accessing object parameters via control logic.
C++ Type:std::vector<std::string>
Controllable:No
Description:Adds user-defined labels for accessing object parameters via control logic.
enableTrueSet the enabled status of the MooseObject.
Default:True
C++ Type:bool
Controllable:Yes
Description:Set the enabled status of the MooseObject.
use_displaced_meshFalseWhether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.

Advanced Parameters

prop_getter_suffixAn optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.
C++ Type:MaterialPropertyName
Unit:(no unit assumed)
Controllable:No
Description:An optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.
use_interpolated_stateFalseFor the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.
Default:False
C++ Type:bool
Controllable:No
Description:For the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.

Material Property Retrieval Parameters

Input Files

(modules/shifted_boundary_method/test/tests/subdomain_element_modifier/subdomain_point_query.i)
(modules/shifted_boundary_method/test/tests/subdomain_element_modifier/grain_marking.i)

(modules/shifted_boundary_method/test/tests/subdomain_element_modifier/subdomain_point_query.i)

# Exercises the PointInSubdomainCheckUO point-query accessors directly.
#
# Uses the same five-grain boundary mesh as grain_marking.i, but instead of
# reassigning element subdomains with SubdomainElementModifier, it evaluates the
# in-out test at each background element centroid:
#   - 'which_sub' records whichSubdomain(centroid): the grain (subdomain) ID that
#     contains the centroid, or the invalid-subdomain sentinel if none does.
#   - 'inside' records ifInside(centroid): 1 if the centroid lies in any grain,
#     0 otherwise.
# The resulting elemental fields are written to Exodus for comparison.

[Problem]
  solve = false
[]

[Mesh]
  [boundary_mesh]
    type = FileMeshGenerator
    file = 'grain_5_boundary.msh'
    save_with_name = 'boundary_mesh'
  []
  # Deliberately larger than the grain region [-0.6, 0.6] x [-0.4, 0.4] so that
  # border elements fall outside every grain. This exercises both the matched
  # branch (a grain contains the centroid) and the exhausted-loop branch
  # (no grain does) of whichSubdomain() and ifInside().
  [background_mesh]
    type = GeneratedMeshGenerator
    dim = 2
    xmin = -0.8
    xmax = 0.8
    ymin = -0.55
    ymax = 0.55
    nx = 10
    ny = 8
    subdomain_ids = 0
  []
  final_generator = background_mesh
[]

[UserObjects]
  [surface_builder]
    type = SurfaceMeshBySubdomainBuilder
    surface_mesh = boundary_mesh
  []
  [subdomain_tester]
    type = PointInSubdomainCheckUO
    builder = surface_builder
  []
[]

[AuxVariables]
  [which_sub]
    family = MONOMIAL
    order = CONSTANT
  []
  [inside]
    family = MONOMIAL
    order = CONSTANT
  []
[]

[AuxKernels]
  [which_sub]
    type = PointInSubdomainTestAux
    variable = which_sub
    subdomain_checker = subdomain_tester
    method = which_subdomain
    execute_on = INITIAL
  []
  [inside]
    type = PointInSubdomainTestAux
    variable = inside
    subdomain_checker = subdomain_tester
    method = if_inside
    execute_on = INITIAL
  []
[]

[Executioner]
  type = Steady
[]

[Outputs]
  exodus = true
[]

(modules/shifted_boundary_method/test/tests/subdomain_element_modifier/grain_marking.i)

# Marks a background mesh with grain (subdomain) IDs using SubdomainElementModifier.
#
# The boundary mesh 'grain_5_boundary.msh' holds five grain-boundary loops
# (subdomains 1-5) that tile the domain [-0.6, 0.6] x [-0.4, 0.4] and meet at
# interior corners. SubdomainElementModifier assigns each background element to
# the grain that contains it; elements straddling a grain corner are assigned to
# the grain occupying the largest active-area fraction (ties broken by lowest
# subdomain ID). The resulting per-subdomain (element block) assignment is written
# to Exodus for comparison.

[Problem]
  solve = false
[]

[Mesh]
  [boundary_mesh]
    type = FileMeshGenerator
    file = 'grain_5_boundary.msh'
    save_with_name = 'boundary_mesh'
  []
  [background_mesh]
    type = GeneratedMeshGenerator
    dim = 2
    xmin = -0.6
    xmax = 0.6
    ymin = -0.4
    ymax = 0.4
    nx = 9
    ny = 6
    subdomain_ids = 0
  []
  final_generator = background_mesh
  add_subdomain_ids = '1 2 3 4 5'
[]

# Unused variable so the Exodus output has a field to write; the test compares the
# per-element subdomain (block) assignment produced by the mesh modifier.
[Variables]
  [u]
  []
[]

[UserObjects]
  [surface_builder]
    type = SurfaceMeshBySubdomainBuilder
    surface_mesh = boundary_mesh
  []
  [subdomain_tester]
    type = PointInSubdomainCheckUO
    builder = surface_builder
  []
[]

[MeshModifiers]
  [assign_subdomains]
    type = SubdomainElementModifier
    subdomain_id_tester = subdomain_tester
    lambda = 0.5
    execute_on = INITIAL
  []
[]

[Executioner]
  type = Steady
[]

[Outputs]
  exodus = true
[]

Usage
Input Parameters
Input Files