- A_coupledArea of the coupled surface [m^2]
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Area of the coupled surface [m^2]
- normal_from_junctionDirection vector pointing from the junction to the coupled volume. This vector will be normalized.
C++ Type:libMesh::VectorValue<double>
Unit:(no unit assumed)
Controllable:No
Description:Direction vector pointing from the junction to the coupled volume. This vector will be normalized.
- pp_suffixSuffix to append to post-processor names
C++ Type:std::string
Controllable:No
Description:Suffix to append to post-processor names
- volume_junctionName of volume junction component on which to apply flux
C++ Type:std::string
Controllable:No
Description:Name of volume junction component on which to apply flux
VolumeJunctionCoupledFlux1Phase
This component couples a VolumeJunction1Phase to another application via a MultiApp by applying a numerical flux computed using the junction state and the external state.
The junction state is
where is the coupling area; see VolumeJunction1Phase for the definition of junction quantities.
The external state is defined by a pressure and a temperature , while assuming the velocity is zero:
where and .
The numerical flux vector is computed as
where is the 3-D numerical flux function and is the normal vector from the exterior application to the junction.
The following table gives the post-processors created by this component, where <suffix> is the suffix provided by "pp_suffix":
| Name | Description | Type | Transfer Direction |
|---|---|---|---|
mass_rate_<suffix> | VolumeJunctionCoupledFlux1PhasePostprocessor | To other app | |
energy_rate_<suffix> | VolumeJunctionCoupledFlux1PhasePostprocessor | To other app | |
p_<suffix> | Receiver | From other app | |
T_<suffix> | Receiver | From other app |
If this application is the main application, then the "multi_app" parameter should be provided, which creates MultiAppPostprocessorTransfer objects; otherwise the other application is responsible for creating the transfers.
Input Parameters
- multi_appIf provided, transfers occur with this MultiApp. The following would be transferred: mass flow rate, energy flow rate, temperature, and pressure at the junction.
C++ Type:MultiAppName
Controllable:No
Description:If provided, transfers occur with this MultiApp. The following would be transferred: mass flow rate, energy flow rate, temperature, and pressure at the junction.
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:No
Description:Set the enabled status of the MooseObject.