- bound_valueThe value of bound for the variable
C++ Type:double
Controllable:No
Description:The value of bound for the variable
- bounded_variableThe variable to be bounded
C++ Type:NonlinearVariableName
Controllable:No
Description:The variable to be bounded
- variableThe name of the variable that this object applies to
C++ Type:AuxVariableName
Controllable:No
Description:The name of the variable that this object applies to
ConstantBoundsAux
Provides constant bound of a variable for the PETSc's variational inequalities solver
Description
ConstantBoundsAux
is used for setting bounds on a nonlinear variable specified through the parameter bounded_variable
. The bound type of upper
or lower
is set with bound_type
parameter. The bound_value
is used to specify the value of a bound. ConstantBoundsAux
expects a variable
parameter to be set (as do all AuxKernels
). This can be a dummy AuxVariable
; the ConstantBoundsAux
actually operates on NumericVectors
held by the nonlinear system and does nothing but return 0 for the value of the specified variable
.
Note that in order for these bounds to have an effect, the user has to specify the PETSc options -snes_type vinewtonssls
or -snes_type vinewtonrsls
. A warning will be generated if neither options are specified. The PETSc manual pages for the vinewtonssls
algorithm can be found here while the manual page for vinewtonrsls
can be found here.
MOOSE users can also enforce constraints through MOOSE using UpperBoundNodalKernel
and LowerBoundNodalKernel
. However, using these objects requires introduction of Lagrange multiplier variables that increase the size of the nonlinear system as well as render some preconditioning methods like algebraic multi-grid ineffective. The number of nonlinear iterations required to solve a constrained PDE defined by this input file with the various constraint algorithms is summarized below:
viewntonrsls
andConstantBoundsAux
: 22vinewtonssls
andConstantBoundsAux
: 53UpperBoundNodalKernel
andLowerBoundNodalKernel
: 25
Example Syntax
[Bounds]
[u_upper_bound]
type = ConstantBoundsAux
variable = bounds_dummy
bounded_variable = u
bound_type = upper
bound_value = 1
[]
[u_lower_bound]
type = ConstantBoundsAux
variable = bounds_dummy
bounded_variable = u
bound_type = lower
bound_value = 0
[]
[v_upper_bound]
type = ConstantBoundsAux
variable = bounds_dummy
bounded_variable = v
bound_type = upper
bound_value = 3
[]
[v_lower_bound]
type = ConstantBoundsAux
variable = bounds_dummy
bounded_variable = v
bound_type = lower
bound_value = -1
[]
[]
(../moose/test/tests/auxkernels/bounds/constant_bounds.i)Input Parameters
- blockThe list of blocks (ids or names) that this object will be applied
C++ Type:std::vector<SubdomainName>
Controllable:No
Description:The list of blocks (ids or names) that this object will be applied
- bound_typeupperType of bound. 'upper' refers to the upper bound. 'lower' refers to the lower value.
Default:upper
C++ Type:MooseEnum
Controllable:No
Description:Type of bound. 'upper' refers to the upper bound. 'lower' refers to the lower value.
- boundaryThe list of boundaries (ids or names) from the mesh where this object applies
C++ Type:std::vector<BoundaryName>
Controllable:No
Description:The list of boundaries (ids or names) from the mesh where this object applies
- check_boundary_restrictedTrueWhether to check for multiple element sides on the boundary in the case of a boundary restricted, element aux variable. Setting this to false will allow contribution to a single element's elemental value(s) from multiple boundary sides on the same element (example: when the restricted boundary exists on two or more sides of an element, such as at a corner of a mesh
Default:True
C++ Type:bool
Controllable:No
Description:Whether to check for multiple element sides on the boundary in the case of a boundary restricted, element aux variable. Setting this to false will allow contribution to a single element's elemental value(s) from multiple boundary sides on the same element (example: when the restricted boundary exists on two or more sides of an element, such as at a corner of a mesh
- execute_onLINEAR TIMESTEP_ENDThe list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, MULTIAPP_FIXED_POINT_END, MULTIAPP_FIXED_POINT_BEGIN, FINAL, CUSTOM, ALWAYS, PRE_DISPLACE.
Default:LINEAR TIMESTEP_END
C++ Type:ExecFlagEnum
Controllable:No
Description:The list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, MULTIAPP_FIXED_POINT_END, MULTIAPP_FIXED_POINT_BEGIN, FINAL, CUSTOM, ALWAYS, PRE_DISPLACE.
- 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
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.
Optional 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.
- seed0The seed for the master random number generator
Default:0
C++ Type:unsigned int
Controllable:No
Description:The seed for the master random number generator
- 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.