PorousFlowAdvectiveFluxCalculatorSaturatedHeat

This UserObject implements the Kuzmin-Turek stabilization scheme for heat advection in the case of single-phase porous flow. Specifically, it computes and and given by (1) and (2) where is the permeability tensor, is the porepressure, is the fluid density, and is the acceleration due to gravity, is the fluid enthalpy, and is the fluid viscosity. Derivatives of these quantities with respect to the PorousFlow Variables (defined in the PorousFlowDictator) are also computed.

The computed and may then be used by the PorousFlowFluxLimitedTVDAdvection Kernel to simulate heat flow. See details on the Kuzmin-Turek stabilization scheme page.

Input Parameters

  • PorousFlowDictatorThe UserObject that holds the list of PorousFlow variable names

    C++ Type:UserObjectName

    Options:

    Description:The UserObject that holds the list of PorousFlow variable names

  • gravityGravitational acceleration vector downwards (m/s^2)

    C++ Type:libMesh::VectorValue

    Options:

    Description:Gravitational acceleration vector downwards (m/s^2)

Required Parameters

  • flux_limiter_typeVanLeerType of flux limiter to use. 'None' means that no antidiffusion will be added in the Kuzmin-Turek scheme

    Default:VanLeer

    C++ Type:MooseEnum

    Options:MinMod VanLeer MC superbee None

    Description:Type of flux limiter to use. 'None' means that no antidiffusion will be added in the Kuzmin-Turek scheme

  • fe_familyFE Family to use (eg Lagrange). You only need to specify this is your porous_flow_vars in your PorousFlowDictator have different families or orders

    C++ Type:MooseEnum

    Options:LAGRANGE MONOMIAL HERMITE SCALAR HIERARCHIC CLOUGH XYZ SZABAB BERNSTEIN

    Description:FE Family to use (eg Lagrange). You only need to specify this is your porous_flow_vars in your PorousFlowDictator have different families or orders

  • multiply_by_densityTrueIf true, then the advective flux will be multiplied by density, so it is a mass flux, which is the most common way of using PorousFlow. If false, then the advective flux will be a volume flux, which is common in poro-mechanics

    Default:True

    C++ Type:bool

    Options:

    Description:If true, then the advective flux will be multiplied by density, so it is a mass flux, which is the most common way of using PorousFlow. If false, then the advective flux will be a volume flux, which is common in poro-mechanics

  • phase0The index corresponding to the phase for this UserObject

    Default:0

    C++ Type:unsigned int

    Options:

    Description:The index corresponding to the phase for this UserObject

  • execute_onLINEARThe list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, FINAL, CUSTOM.

    Default:LINEAR

    C++ Type:ExecFlagEnum

    Options:NONE INITIAL LINEAR NONLINEAR TIMESTEP_END TIMESTEP_BEGIN FINAL CUSTOM

    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, FINAL, CUSTOM.

  • fe_orderFE Order to use (eg First). You only need to specify this is your porous_flow_vars in your PorousFlowDictator have different families or orders

    C++ Type:MooseEnum

    Options:CONSTANT FIRST SECOND THIRD FOURTH

    Description:FE Order to use (eg First). You only need to specify this is your porous_flow_vars in your PorousFlowDictator have different families or orders

  • blockThe list of block ids (SubdomainID) that this object will be applied

    C++ Type:std::vector

    Options:

    Description:The list of block ids (SubdomainID) that this object will be applied

Optional Parameters

  • enableTrueSet the enabled status of the MooseObject.

    Default:True

    C++ Type:bool

    Options:

    Description:Set the enabled status of the MooseObject.

  • 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

    Options:

    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).

  • 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

    Options:

    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.

  • control_tagsAdds user-defined labels for accessing object parameters via control logic.

    C++ Type:std::vector

    Options:

    Description:Adds user-defined labels for accessing object parameters via control logic.

  • seed0The seed for the master random number generator

    Default:0

    C++ Type:unsigned int

    Options:

    Description:The seed for the master random number generator

  • implicitTrueDetermines whether this object is calculated using an implicit or explicit form

    Default:True

    C++ Type:bool

    Options:

    Description:Determines whether this object is calculated using an implicit or explicit form

Advanced Parameters

Input Files

Child Objects