- source_variablesVariable(s) to transfer from.
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:Variable(s) to transfer from.
- variablesVariable(s) to store transferred values in.
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:Variable(s) to store transferred values in.
MultiAppMFEMShapeEvaluationTransfer
Allows transfers of MFEM variables between MFEM-based applications via local evaluation of shape functions at target nodal projection points. The variables may be defined on different meshes and FESpaces of different orders, but must share the same dimensionality, and both belong to an MFEMProblem in their respective applications.
General Description
MultiAppMFEMShapeEvaluationTransfer executes transfers in three steps:
Extraction of a vector of node positions in the
ParFiniteElementSpaceof the destinationmfem::ParGridFunction, using MFEMNodalProjector.Interpolation of the source
mfem::ParGridFunctionat this set of node locations, usingmfem::FindPointsGSLIBto perform the required gather/scatter operations to obtain a set of points on the local mesh partition, and perform shape function evaluations at these points.Projection of the evaluated source variable values onto the destination variable nodes, to set the destination variable degrees of freedom, using MFEMNodalProjector.
For transfers between identical variables defined on the same mesh, users are recommended to use MultiAppMFEMCopyTransfer for performance.
Features Supported
All MFEM to MFEM transfers executed from this class should be able to support:
transfers of scalar and vector variables
transfers between variables belonging to different finite element spaces and orders
transfers between complex variables
transfers between variables defined on submeshes and parent meshes
arbitrary number of parallel processes for both the source and target application
transfers between parent and child applications
transfers between sibling applications (child to child)
transfers from multiple variables to multiple variables
Input Parameters
- check_multiapp_execute_onTrueWhen false the check between the multiapp and transfer execute on flags is not performed.
Default:True
C++ Type:bool
Controllable:No
Description:When false the check between the multiapp and transfer execute on flags is not performed.
- displaced_source_meshFalseWhether or not to use the displaced mesh for the source mesh.
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not to use the displaced mesh for the source mesh.
- displaced_target_meshFalseWhether or not to use the displaced mesh for the target mesh.
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not to use the displaced mesh for the target mesh.
- execute_onSAME_AS_MULTIAPPThe 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:SAME_AS_MULTIAPP
C++ Type:ExecFlagEnum
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.
- from_multi_appThe name of the MultiApp to receive data from
C++ Type:MultiAppName
Controllable:No
Description:The name of the MultiApp to receive data from
- to_multi_appThe name of the MultiApp to transfer the data to
C++ Type:MultiAppName
Controllable:No
Description:The name of the MultiApp to transfer the data to
Optional Parameters
- _called_legacy_paramsTrue
Default:True
C++ Type:bool
Controllable:No
- 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.
- skip_coordinate_collapsingTrueWhether to skip coordinate collapsing (translation and rotation are still performed, only XYZ, RZ etc collapsing is skipped) when performing mapping and inverse mapping coordinate transformation operations. This parameter should only be set by users who really know what they're doing.
Default:True
C++ Type:bool
Controllable:No
Description:Whether to skip coordinate collapsing (translation and rotation are still performed, only XYZ, RZ etc collapsing is skipped) when performing mapping and inverse mapping coordinate transformation operations. This parameter should only be set by users who really know what they're doing.
- 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
Input Files
- (test/tests/mfem/transfers/mfem_parent_mfem_sub/mfem_parent_vector.i)
- (test/tests/mfem/transfers/mfem_parent_mfem_sub/mfem_parent_embedded_submesh.i)
- (test/tests/mfem/transfers/mfem_parent_mfem_sub/parent.i)
- (test/tests/mfem/transfers/mfem_sub_mfem_sub/parent.i)
- (test/tests/mfem/transfers/mfem_parent_mfem_sub/parent_complex.i)
- (test/tests/mfem/transfers/sibling_transfers/mfem_main_between_multiapp.i)