- boundaryThe list of boundary IDs from the mesh where this object applies
C++ Type:std::vector<BoundaryName>
Controllable:No
Description:The list of boundary IDs from the mesh where this object applies
- mobilityThe name of the mobility material property that will be used in the flux computation.
C++ Type:std::string
Controllable:No
Description:The name of the mobility material property that will be used in the flux computation.
- position_unitsUnits of position.
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Units of position.
- rThe reflection coefficient
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:The reflection coefficient
- variableThe name of the variable which this postprocessor integrates
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:The name of the variable which this postprocessor integrates
SideTotFluxIntegral
Returns the flux of a defined species at a boundary
Overview
SideTotFluxIntegral computes the surface integrated flux of a species on a boundary.
The surface flux is defined as:
Where:
the subscript represents the properties of the chosen species,
is the species flux,
is the normal vector of the boundary,
is the mobility coefficient,
is the species density,
is the electric field,
is the thermal velocity of the species,
is the Boltzmann constant,
is the species mass,
is the species temperature,
is defined such that the outflow is non-zero when the drift velocity is directed towards the wall and zero otherwise, and
is defined as the fraction of particles reflected by the surface.
When converting the density to molar logarithmic form and applying a scaling factor of the mesh, the following changes are applied to SideTotFluxIntegral:
Where:
is the molar density of the species in logarithmic form, and
is the scaling factor of the mesh.
The SideTotFluxIntegral object does not have a formalized test, yet. For this reason, users should beware of unforeseen bugs when using SideTotFluxIntegral. To report a bug or discuss future contributions to Zapdos, please refer to the Zapdos GitHub Discussions page. For standards on how to contribute to Zapdos and the MOOSE framework, please refer to the MOOSE Contributing page.
Example Input File Syntax
[Postprocessors]
[electrode_ion_current]
type = SideTotFluxIntegral
variable = ions
mobility = muions
r = 0.0
position_units = 1.0
field_property_name = electric_field
boundary = electrode
[]
[]
Input Parameters
- field_property_namefield_solver_interface_propertyName of the solver interface material property.
Default:field_solver_interface_property
C++ Type:std::string
Controllable:No
Description:Name of the solver interface material property.
- user_velocity-1Optional parameter if user wants to specify the thermal velocity
Default:-1
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Optional parameter if user wants to specify the thermal velocity
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
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.
- outputsVector of output names where you would like to restrict the output of variables(s) associated with this object
C++ Type:std::vector<OutputName>
Controllable:No
Description:Vector of output names where you would like to restrict the output of variables(s) associated with this object
- 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.