- tally_scoreScore to report the relative error. If there is just a single score, this defaults to that value
C++ Type:MooseEnum
Controllable:No
Description:Score to report the relative error. If there is just a single score, this defaults to that value
- value_typemaxWhether to give the maximum or minimum tally relative error
Default:max
C++ Type:MooseEnum
Controllable:No
Description:Whether to give the maximum or minimum tally relative error
TallyRelativeError
Maximum/minimum tally relative error
Description
This postprocessor evaluates the maximum, minimum, or average relative error in the tally created by OpenMCCellAverageProblem. This postprocessor can be used to monitor statistical convergence of the tally.
Example Input Syntax
Below, the max_rel_err, min_rel_err and avg_rel_err postprocessors are used to evaluate the maximum, minimum and average tally relative error, respectively.
[Postprocessors<<<{"href": "../../syntax/Postprocessors/index.html"}>>>]
[max_rel_err]
type = TallyRelativeError<<<{"description": "Maximum/minimum tally relative error", "href": "TallyRelativeError.html"}>>>
value_type<<<{"description": "Whether to give the maximum or minimum tally relative error"}>>> = max
[]
[min_rel_err]
type = TallyRelativeError<<<{"description": "Maximum/minimum tally relative error", "href": "TallyRelativeError.html"}>>>
value_type<<<{"description": "Whether to give the maximum or minimum tally relative error"}>>> = min
[]
[avg_rel_err]
type = TallyRelativeError<<<{"description": "Maximum/minimum tally relative error", "href": "TallyRelativeError.html"}>>>
value_type<<<{"description": "Whether to give the maximum or minimum tally relative error"}>>> = average
[]
[power_1]
type = PointValue<<<{"description": "Compute the value of a variable at a specified location", "href": "PointValue.html"}>>>
variable<<<{"description": "The name of the variable that this postprocessor operates on."}>>> = kappa_fission
point<<<{"description": "The physical point where the solution will be evaluated."}>>> = '0 0 0'
[]
[power_2]
type = PointValue<<<{"description": "Compute the value of a variable at a specified location", "href": "PointValue.html"}>>>
variable<<<{"description": "The name of the variable that this postprocessor operates on."}>>> = kappa_fission
point<<<{"description": "The physical point where the solution will be evaluated."}>>> = '0 0 4'
[]
[power_3]
type = PointValue<<<{"description": "Compute the value of a variable at a specified location", "href": "PointValue.html"}>>>
variable<<<{"description": "The name of the variable that this postprocessor operates on."}>>> = kappa_fission
point<<<{"description": "The physical point where the solution will be evaluated."}>>> = '0 0 8'
[]
[std_dev_1]
type = PointValue<<<{"description": "Compute the value of a variable at a specified location", "href": "PointValue.html"}>>>
variable<<<{"description": "The name of the variable that this postprocessor operates on."}>>> = kappa_fission_std_dev
point<<<{"description": "The physical point where the solution will be evaluated."}>>> = '0 0 0'
[]
[std_dev_2]
type = PointValue<<<{"description": "Compute the value of a variable at a specified location", "href": "PointValue.html"}>>>
variable<<<{"description": "The name of the variable that this postprocessor operates on."}>>> = kappa_fission_std_dev
point<<<{"description": "The physical point where the solution will be evaluated."}>>> = '0 0 4'
[]
[std_dev_3]
type = PointValue<<<{"description": "Compute the value of a variable at a specified location", "href": "PointValue.html"}>>>
variable<<<{"description": "The name of the variable that this postprocessor operates on."}>>> = kappa_fission_std_dev
point<<<{"description": "The physical point where the solution will be evaluated."}>>> = '0 0 8'
[]
[]Input 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.