You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need to customise the FluidProperties UserObject for water to avoid P going out of range, e.g. by using tabulated fluid properties to extend the range of Water97. Currently if using PorousFlowBrine through the PorousFlowFullySaturated action there is no option to specify the water_fp that is used in PorousFlowBrine, hence it uses the default (I think this is Water97) which does not cover my required P range. Can achieve the desired outcome by specifying everything manually, but would prefer to use the action for simplicity.
Design
Add water_fp as an optional param for PorousFlowFullySaturated when using fluid_properties_type = PorousFlowBrine. Pass water_fp to PorousFlowActionBase::addBrineMaterial.
Impact
Should have no impact on validity of existing input files
The text was updated successfully, but these errors were encountered:
It's possible that the water_fp param was added to PorousFlowBrine after the PorousFlowFullySaturated action was created and was never added there too?
Motivation
Need to customise the FluidProperties UserObject for water to avoid P going out of range, e.g. by using tabulated fluid properties to extend the range of Water97. Currently if using PorousFlowBrine through the PorousFlowFullySaturated action there is no option to specify the water_fp that is used in PorousFlowBrine, hence it uses the default (I think this is Water97) which does not cover my required P range. Can achieve the desired outcome by specifying everything manually, but would prefer to use the action for simplicity.
Design
Add water_fp as an optional param for PorousFlowFullySaturated when using fluid_properties_type = PorousFlowBrine. Pass water_fp to PorousFlowActionBase::addBrineMaterial.
Impact
Should have no impact on validity of existing input files
The text was updated successfully, but these errors were encountered: