- PorousFlowDictatorThe UserObject that holds the list of PorousFlow variable names
C++ Type:UserObjectName
Controllable:No
Description:The UserObject that holds the list of PorousFlow variable names
- SumQuantityUOUser Object of type=PorousFlowSumQuantity in which to place the total outflow from the line sink for each time step.
C++ Type:UserObjectName
Controllable:No
Description:User Object of type=PorousFlowSumQuantity in which to place the total outflow from the line sink for each time step.
- bottom_p_or_tFor function_of=pressure, this function is the pressure at the bottom of the borehole, otherwise it is the temperature at the bottom of the borehole.
C++ Type:FunctionName
Unit:(no unit assumed)
Controllable:No
Description:For function_of=pressure, this function is the pressure at the bottom of the borehole, otherwise it is the temperature at the bottom of the borehole.
- characterIf zero then borehole does nothing. If positive the borehole acts as a sink (production well) for porepressure > borehole pressure, and does nothing otherwise. If negative the borehole acts as a source (injection well) for porepressure < borehole pressure, and does nothing otherwise. The flow rate to/from the borehole is multiplied by |character|, so usually character = +/- 1, but you can specify other quantities to provide an overall scaling to the flow if you like.
C++ Type:FunctionName
Unit:(no unit assumed)
Controllable:No
Description:If zero then borehole does nothing. If positive the borehole acts as a sink (production well) for porepressure > borehole pressure, and does nothing otherwise. If negative the borehole acts as a source (injection well) for porepressure < borehole pressure, and does nothing otherwise. The flow rate to/from the borehole is multiplied by |character|, so usually character = +/- 1, but you can specify other quantities to provide an overall scaling to the flow if you like.
- variableThe name of the variable that this residual object operates on
C++ Type:NonlinearVariableName
Unit:(no unit assumed)
Controllable:No
Description:The name of the variable that this residual object operates on
PorousFlowPeacemanBorehole
A PorousFlowPeacemanBorehole is a special case of the general line sink in which a polyline (represented by a sequence of points) acts as a sink or source in the model. Please see sinks for an extended discussion and examples.
The function given by "bottom_p_or_t" is evaluated at the well bottom. If a file is read in using "point_file" to define the coordinates and weights of the PorousFlowPeacemanBorehole, the well bottom is assumed to be the last entry in this file and "bottom_p_or_t" will be evaluated at the z-coordinate of the last entry in "point_file". It is an error if the first entry in the "point_file" has a smaller z-coordinate than the last entry.
The wellbore pressure along the borehole can be built in two ways. By default, a single constant "unit_weight" (fluid density gravity) is used, exactly as described in sinks. If instead "unit_weight_fp" is supplied (together with "unit_weight_temperature" and "unit_weight_gravity"), the fluid unit weight is instead computed at each borehole point from a temperature-dependent fluid density, and integrated along the well — see sinks for the formula, its justification, and the deliberate approximation made in its Jacobian (the residual always uses the fluid density implied by the current nonlinear iterate's temperature, but the Jacobian does not differentiate the wellbore pressure with respect to temperature, since that dependence couples this borehole point's residual to temperature degrees of freedom in other elements along the well, which a DiracKernel cannot assemble into). unit_weight and unit_weight_fp are mutually exclusive, and unit_weight_fp is not compatible with function_of = temperature. These four new parameters are deliberately not named fp/gravity/temperature_variable (even though that would mirror convention elsewhere in PorousFlow) because those are common [GlobalParams] names used by unrelated Darcy kernels or fluid-properties materials; an input file that sets gravity or fp at the [GlobalParams] level would otherwise silently activate, or fail to validate, this mode on every PorousFlowPeacemanBorehole in the input.
To report the flow rate at each individual borehole point (rather than only the well-wide total available via "SumQuantityUO"), set "PointFluxUO" to a PorousFlowPointFluxQuantity UserObject, and read it out with a PorousFlowPlotPointFluxQuantity VectorPostprocessor.
Input Parameters
- PointFluxUOOptional UserObject of type=PorousFlowPointFluxQuantity in which to record the instantaneous flux (eg kg.s^-1 for fluid, J.s^-1 for heat) at each individual Dirac point of this line sink, as computed during the most recent residual evaluation. Use a PorousFlowPlotPointFluxQuantity VectorPostprocessor to output the recorded values. Unlike SumQuantityUO, this is not multiplied by the timestep size. Use a separate UserObject for each line sink.
C++ Type:UserObjectName
Controllable:No
Description:Optional UserObject of type=PorousFlowPointFluxQuantity in which to record the instantaneous flux (eg kg.s^-1 for fluid, J.s^-1 for heat) at each individual Dirac point of this line sink, as computed during the most recent residual evaluation. Use a PorousFlowPlotPointFluxQuantity VectorPostprocessor to output the recorded values. Unlike SumQuantityUO, this is not multiplied by the timestep size. Use a separate UserObject for each line sink.
- allow_moving_sourcesFalseIf true, allow Dirac sources to move, even if the mesh does not move, during the simulation.
Default:False
C++ Type:bool
Controllable:No
Description:If true, allow Dirac sources to move, even if the mesh does not move, during the simulation.
- 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
- fluid_phase0The fluid phase whose pressure (and potentially mobility, enthalpy, etc) controls the flux to the line sink. For p_or_t=temperature, and without any use_*, this parameter is irrelevant
Default:0
C++ Type:unsigned int
Controllable:No
Description:The fluid phase whose pressure (and potentially mobility, enthalpy, etc) controls the flux to the line sink. For p_or_t=temperature, and without any use_*, this parameter is irrelevant
- function_ofpressureModifying functions will be a function of either pressure and permeability (eg, for boreholes that pump fluids) or temperature and thermal conductivity (eg, for boreholes that pump pure heat with no fluid flow)
Default:pressure
C++ Type:MooseEnum
Controllable:No
Description:Modifying functions will be a function of either pressure and permeability (eg, for boreholes that pump fluids) or temperature and thermal conductivity (eg, for boreholes that pump pure heat with no fluid flow)
- line_baseLine base point x,y,z coordinates. This is the same format as a single-line point_file. Note this is only used if there is no point file specified.
C++ Type:std::vector<Real>
Unit:(no unit assumed)
Controllable:No
Description:Line base point x,y,z coordinates. This is the same format as a single-line point_file. Note this is only used if there is no point file specified.
- line_direction0 0 1Line direction. Note this is only used if there is only one point in the point_file.
Default:0 0 1
C++ Type:libMesh::VectorValue<Real>
Unit:(no unit assumed)
Controllable:No
Description:Line direction. Note this is only used if there is only one point in the point_file.
- line_length0Line length. Note this is only used if there is only one point in the point_file.
Default:0
C++ Type:Real
Unit:(no unit assumed)
Range:line_length>=0
Controllable:No
Description:Line length. Note this is only used if there is only one point in the point_file.
- mass_fraction_componentThe index corresponding to a fluid component. If supplied, the flux will be multiplied by the nodal mass fraction for the component
C++ Type:unsigned int
Controllable:No
Description:The index corresponding to a fluid component. If supplied, the flux will be multiplied by the nodal mass fraction for the component
- multiplying_var1.0Fluxes will be moultiplied by this variable
Default:1.0
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:Fluxes will be moultiplied by this variable
- point_fileThe file containing the coordinates of the points and their weightings that approximate the line sink. The physical meaning of the weightings depend on the scenario, eg, they may be borehole radii. Each line in the file must contain a space-separated weight and coordinate, viz r x y z. For boreholes, the last point in the file is defined as the borehole bottom, where the borehole pressure is bottom_pressure. If your file contains just one point, you must also specify the line_length and line_direction parameters. Note that you will get segementation faults if your points do not lie within your mesh!
C++ Type:std::string
Controllable:No
Description:The file containing the coordinates of the points and their weightings that approximate the line sink. The physical meaning of the weightings depend on the scenario, eg, they may be borehole radii. Each line in the file must contain a space-separated weight and coordinate, viz r x y z. For boreholes, the last point in the file is defined as the borehole bottom, where the borehole pressure is bottom_pressure. If your file contains just one point, you must also specify the line_length and line_direction parameters. Note that you will get segementation faults if your points do not lie within your mesh!
- point_not_found_behaviorERRORBy default (IGNORE), it is ignored if an added point cannot be located in the specified subdomains. If this option is set to ERROR, this situation will result in an error. If this option is set to WARNING, then a warning will be issued.
Default:ERROR
C++ Type:MooseEnum
Controllable:No
Description:By default (IGNORE), it is ignored if an added point cannot be located in the specified subdomains. If this option is set to ERROR, this situation will result in an error. If this option is set to WARNING, then a warning will be issued.
- re_constant0.28The dimensionless constant used in evaluating the borehole effective radius. This depends on the meshing scheme. Peacemann finite-difference calculations give 0.28, while for rectangular finite elements the result is closer to 0.1594. (See Eqn(4.13) of Z Chen, Y Zhang, Well flow models for various numerical methods, Int J Num Analysis and Modeling, 3 (2008) 375-388.)
Default:0.28
C++ Type:Real
Unit:(no unit assumed)
Controllable:No
Description:The dimensionless constant used in evaluating the borehole effective radius. This depends on the meshing scheme. Peacemann finite-difference calculations give 0.28, while for rectangular finite elements the result is closer to 0.1594. (See Eqn(4.13) of Z Chen, Y Zhang, Well flow models for various numerical methods, Int J Num Analysis and Modeling, 3 (2008) 375-388.)
- unit_weight(fluid_density*gravitational_acceleration) as a vector pointing downwards. Note that the borehole pressure at a given z position is bottom_p_or_t + unit_weight*(q - q_bottom), where q=(x,y,z) and q_bottom=(x,y,z) of the bottom point of the borehole. The analogous formula holds for function_of=temperature. If you don't want bottomhole pressure (or temperature) to vary in the borehole just set unit_weight=0. Typical value is = (0,0,-1E4), for water. Exactly one of 'unit_weight' or 'unit_weight_fp' must be given. Use 'unit_weight_fp' instead of 'unit_weight' if you want the fluid unit weight to vary along the borehole according to a temperature-dependent fluid density, rather than being a single constant value.
C++ Type:libMesh::VectorValue<Real>
Unit:(no unit assumed)
Controllable:No
Description:(fluid_density*gravitational_acceleration) as a vector pointing downwards. Note that the borehole pressure at a given z position is bottom_p_or_t + unit_weight*(q - q_bottom), where q=(x,y,z) and q_bottom=(x,y,z) of the bottom point of the borehole. The analogous formula holds for function_of=temperature. If you don't want bottomhole pressure (or temperature) to vary in the borehole just set unit_weight=0. Typical value is = (0,0,-1E4), for water. Exactly one of 'unit_weight' or 'unit_weight_fp' must be given. Use 'unit_weight_fp' instead of 'unit_weight' if you want the fluid unit weight to vary along the borehole according to a temperature-dependent fluid density, rather than being a single constant value.
- unit_weight_fpSinglePhaseFluidProperties UserObject used to evaluate the in-well fluid density from 'unit_weight_temperature' at each borehole point, in order to build a wellbore pressure profile that accounts for a thermal gradient along the borehole. Providing this parameter activates this temperature-dependent unit-weight mode instead of the constant 'unit_weight'. Not compatible with function_of=temperature, since in that mode bottom_p_or_t is a temperature, not a pressure, so there is no pressure profile to build. If given, 'unit_weight_temperature' and 'unit_weight_gravity' are also required. (Deliberately not named 'fp'/'gravity'/'temperature_variable', even though that mirrors convention elsewhere in PorousFlow, because those are common GlobalParams names: an input file that sets 'gravity' or 'fp' in [GlobalParams] for unrelated Darcy kernels or fluid materials would otherwise silently activate, or fail to validate, this mode on every PorousFlowPeacemanBorehole in the input.)
C++ Type:UserObjectName
Controllable:No
Description:SinglePhaseFluidProperties UserObject used to evaluate the in-well fluid density from 'unit_weight_temperature' at each borehole point, in order to build a wellbore pressure profile that accounts for a thermal gradient along the borehole. Providing this parameter activates this temperature-dependent unit-weight mode instead of the constant 'unit_weight'. Not compatible with function_of=temperature, since in that mode bottom_p_or_t is a temperature, not a pressure, so there is no pressure profile to build. If given, 'unit_weight_temperature' and 'unit_weight_gravity' are also required. (Deliberately not named 'fp'/'gravity'/'temperature_variable', even though that mirrors convention elsewhere in PorousFlow, because those are common GlobalParams names: an input file that sets 'gravity' or 'fp' in [GlobalParams] for unrelated Darcy kernels or fluid materials would otherwise silently activate, or fail to validate, this mode on every PorousFlowPeacemanBorehole in the input.)
- unit_weight_gravityGravitational acceleration, pointing downwards, in the units used elsewhere in this input file (eg (0,0,-9.81) for SI units and lengths in metres). Only used, and required, if 'unit_weight_fp' is given. Densities computed from 'unit_weight_fp' are always in kg/m^3, so if lengths in this input file are not metres, scale 'unit_weight_gravity' accordingly (eg (0,0,-9.81E-6) if pressures are in MPa and lengths in metres, matching the 'gravity' convention used by PorousFlow Darcy kernels).
C++ Type:libMesh::VectorValue<Real>
Unit:(no unit assumed)
Controllable:No
Description:Gravitational acceleration, pointing downwards, in the units used elsewhere in this input file (eg (0,0,-9.81) for SI units and lengths in metres). Only used, and required, if 'unit_weight_fp' is given. Densities computed from 'unit_weight_fp' are always in kg/m^3, so if lengths in this input file are not metres, scale 'unit_weight_gravity' accordingly (eg (0,0,-9.81E-6) if pressures are in MPa and lengths in metres, matching the 'gravity' convention used by PorousFlow Darcy kernels).
- unit_weight_pressure_unitPaThe unit of 'unit_weight_reference_pressure'. Only used if 'unit_weight_fp' is given.
Default:Pa
C++ Type:MooseEnum
Controllable:No
Description:The unit of 'unit_weight_reference_pressure'. Only used if 'unit_weight_fp' is given.
- unit_weight_reference_pressure101325The fixed pressure (in the units given by 'unit_weight_pressure_unit') at which the in-well fluid density is evaluated by 'unit_weight_fp'. Only used if 'unit_weight_fp' is given. Choose a value close to the expected wellbore pressure for the most accurate density.
Default:101325
C++ Type:Real
Unit:(no unit assumed)
Range:unit_weight_reference_pressure > 0
Controllable:No
Description:The fixed pressure (in the units given by 'unit_weight_pressure_unit') at which the in-well fluid density is evaluated by 'unit_weight_fp'. Only used if 'unit_weight_fp' is given. Choose a value close to the expected wellbore pressure for the most accurate density.
- unit_weight_temperatureThe (nonlinear or auxiliary) variable holding temperature, sampled at each borehole point to compute the in-well fluid density used to build the wellbore pressure profile. Must be a variable, not a constant value. This is unrelated to function_of=temperature (which instead selects whether the *outflow* driving this DiracKernel is a function of porepressure or temperature). Only used, and required, if 'unit_weight_fp' is given.
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:The (nonlinear or auxiliary) variable holding temperature, sampled at each borehole point to compute the in-well fluid density used to build the wellbore pressure profile. Must be a variable, not a constant value. This is unrelated to function_of=temperature (which instead selects whether the *outflow* driving this DiracKernel is a function of porepressure or temperature). Only used, and required, if 'unit_weight_fp' is given.
- unit_weight_temperature_unitKelvinThe unit of 'unit_weight_temperature'. Only used if 'unit_weight_fp' is given.
Default:Kelvin
C++ Type:MooseEnum
Controllable:No
Description:The unit of 'unit_weight_temperature'. Only used if 'unit_weight_fp' is given.
- use_enthalpyFalseMultiply the flux by the fluid enthalpy
Default:False
C++ Type:bool
Controllable:No
Description:Multiply the flux by the fluid enthalpy
- use_internal_energyFalseMultiply the flux by the fluid internal energy
Default:False
C++ Type:bool
Controllable:No
Description:Multiply the flux by the fluid internal energy
- use_mobilityFalseMultiply the flux by the fluid mobility
Default:False
C++ Type:bool
Controllable:No
Description:Multiply the flux by the fluid mobility
- use_relative_permeabilityFalseMultiply the flux by the fluid relative permeability
Default:False
C++ Type:bool
Controllable:No
Description:Multiply the flux by the fluid relative permeability
- weight_reporterreporter weight name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file C++ Type:ReporterName
Controllable:No
Description:reporter weight name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file - well_constant-1Usually this is calculated internally from the element geometry, the local borehole direction and segment length, and the permeability. However, if this parameter is given as a positive number then this number is used instead of the internal calculation. This speeds up computation marginally. re_constant becomes irrelevant
Default:-1
C++ Type:Real
Unit:(no unit assumed)
Controllable:No
Description:Usually this is calculated internally from the element geometry, the local borehole direction and segment length, and the permeability. However, if this parameter is given as a positive number then this number is used instead of the internal calculation. This speeds up computation marginally. re_constant becomes irrelevant
- x_coord_reporterreporter x-coordinate name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file C++ Type:ReporterName
Controllable:No
Description:reporter x-coordinate name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file - y_coord_reporterreporter y-coordinate name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file C++ Type:ReporterName
Controllable:No
Description:reporter y-coordinate name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file - z_coord_reporterreporter z-coordinate name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file C++ Type:ReporterName
Controllable:No
Description:reporter z-coordinate name of line sink. This uses the reporter syntax
/ . Each point must adhere to the same requirements as those that would be given if using point_file
Optional Parameters
- absolute_value_vector_tagsThe tags for the vectors this residual object should fill with the absolute value of the residual contribution
C++ Type:std::vector<TagName>
Controllable:No
Description:The tags for the vectors this residual object should fill with the absolute value of the residual contribution
- extra_matrix_tagsThe extra tags for the matrices this Kernel should fill
C++ Type:std::vector<TagName>
Controllable:No
Description:The extra tags for the matrices this Kernel should fill
- extra_vector_tagsThe extra tags for the vectors this Kernel should fill
C++ Type:std::vector<TagName>
Controllable:No
Description:The extra tags for the vectors this Kernel should fill
- matrix_onlyFalseWhether this object is only doing assembly to matrices (no vectors)
Default:False
C++ Type:bool
Controllable:No
Description:Whether this object is only doing assembly to matrices (no vectors)
- matrix_tagssystemThe tag for the matrices this Kernel should fill
Default:system
C++ Type:MultiMooseEnum
Controllable:No
Description:The tag for the matrices this Kernel should fill
- vector_tagsnontimeThe tag for the vectors this Kernel should fill
Default:nontime
C++ Type:MultiMooseEnum
Controllable:No
Description:The tag for the vectors this Kernel should fill
Contribution To Tagged Field Data 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.
- drop_duplicate_pointsTrueBy default points added to a DiracKernel are dropped if a point at the same locationhas been added before. If this option is set to false duplicate points are retainedand contribute to residual and Jacobian.
Default:True
C++ Type:bool
Controllable:No
Description:By default points added to a DiracKernel are dropped if a point at the same locationhas been added before. If this option is set to false duplicate points are retainedand contribute to residual and Jacobian.
- enableTrueSet the enabled status of the MooseObject.
Default:True
C++ Type:bool
Controllable:Yes
Description:Set the enabled status of the MooseObject.
- implicitTrueDetermines whether this object is calculated using an implicit or explicit form
Default:True
C++ Type:bool
Controllable:No
Description:Determines whether this object is calculated using an implicit or explicit form
- search_methodnearest_node_connected_sidesChoice of search algorithm. All options begin by finding the nearest node in the primary boundary to a query point in the secondary boundary. In the default nearest_node_connected_sides algorithm, primary boundary elements are searched iff that nearest node is one of their nodes. This is fast to determine via a pregenerated node-to-elem map and is robust on conforming meshes. In the optional all_proximate_sides algorithm, primary boundary elements are searched iff they touch that nearest node, even if they are not topologically connected to it. This is more CPU-intensive but is necessary for robustness on any boundary surfaces which has disconnections (such as Flex IGA meshes) or non-conformity (such as hanging nodes in adaptively h-refined meshes).
Default:nearest_node_connected_sides
C++ Type:MooseEnum
Controllable:No
Description:Choice of search algorithm. All options begin by finding the nearest node in the primary boundary to a query point in the secondary boundary. In the default nearest_node_connected_sides algorithm, primary boundary elements are searched iff that nearest node is one of their nodes. This is fast to determine via a pregenerated node-to-elem map and is robust on conforming meshes. In the optional all_proximate_sides algorithm, primary boundary elements are searched iff they touch that nearest node, even if they are not topologically connected to it. This is more CPU-intensive but is necessary for robustness on any boundary surfaces which has disconnections (such as Flex IGA meshes) or non-conformity (such as hanging nodes in adaptively h-refined meshes).
- 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.
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.
Material Property Retrieval Parameters
Input Files
- (modules/porous_flow/test/tests/dirackernels/bh_except10.i)
- (modules/porous_flow/test/tests/jacobian/line_sink01.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except02.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except03.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except05.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except04.i)
- (modules/porous_flow/test/tests/jacobian/line_sink03.i)
- (modules/porous_flow/test/tests/dirackernels/bh_variable_unit_weight.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except13.i)
- (modules/porous_flow/test/tests/dirackernels/injection_production.i)
- (modules/porous_flow/examples/multiapp_fracture_flow/3dFracture/fracture_only_aperture_changing.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except09.i)
- (modules/porous_flow/test/tests/dirackernels/bh03.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except01.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except06.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except11.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except08.i)
- (modules/porous_flow/test/tests/dirackernels/bh02reporter.i)
- (modules/combined/examples/geochem-porous_flow/forge/porous_flow.i)
- (modules/porous_flow/test/tests/dirackernels/bh04.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except15.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except18.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except16.i)
- (modules/porous_flow/test/tests/actions/basicthm_borehole.i)
- (modules/porous_flow/test/tests/dirackernels/bh07.i)
- (modules/porous_flow/test/tests/actions/fullsat_borehole.i)
- (modules/porous_flow/test/tests/dirackernels/bh02.i)
- (modules/porous_flow/examples/groundwater/ex02_abstraction.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except07.i)
- (modules/porous_flow/test/tests/dirackernels/bh05.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except14.i)
- (modules/porous_flow/test/tests/dirackernels/bh_except12.i)
- (modules/porous_flow/test/tests/dirackernels/bh_unit_weight.i)