how to set up Hydrostatic pressure distribution in interFoam?
hello foamer
I am simulating 2d hydraulic jump using interFoam. inlet velocity is subcritical condition and I know only velocity and water depth at inlet. this subcritical flow will be changed to supercritical flow when flow pass semi circular shaped weir. To make hydraulic jump, I want to specify Hydrostatic pressure distribution at outlet boundary condition. but in case of interfoam, we should set up "p_rgh "not "p". as far as i know, p_rgh is p  rgh but i don't understand what it mean exactly. anyway I want to input Hydrostatic pressure into boundary condition of p_rgh at outlet. how can I do it?? please help me. 
Hey, have you found an answer to your problem?

hey
Quote:
in my view, fixedvalue uniform 0 for p_rgh represent hydrostatic pressure the reason is that : we can see the mathematic definition of p_rgh in pEqn.H file. that is, p_rgh = p  rho*gh; "p" is total pressure "rho" is density of fluid and the meaning of "gh" exist in createFields.H file. that is, volScalarField gh("gh", g & mesh.C()); it mean dot product gravitational acceleration and cell centres. so rho*gh term represent hydrostatic pressure. when we set p_rgh to fixedvalue 0, its expression is mathematically like p_rgh = p  rho*gh = 0 "rho*gh" move to right side. it yields p = rho*gh "rho*gh" is hydrostatic pressure as i mentioned above. I hope it help you 
Thank you! Ok that makes sense.
So if I set p_rgh to fixedValue uniform 0, what value does the hydrostatic pressure have then? I want to define a permanent water level at a certain height as a BC, so I would need to set a certain hydrostatic pressure for this water level. How can I do that if I have to set p_rgh BC to fixedValue uniform 0? Do you know if that is possible? Is my thinking wrong? 
Hello,
I'm having similar problems here. Same as Max, I need to define a water level at the outlet, so I would need to give a certain pressure and not just let it calculate. And for p_rgh: When set to 0, then there is ONLY hydrostatic pressure at the outlet (no more dynamic pressure), right? What I'd like is to know/define the hydrostatic pressure and still have dynamic pressure :confused: 
If you use the totalPressure boundary type, the value is 0,but then the flow is considered as a free outflow.
To define a water level at the outlet (if I have the same patch at the boundary for water and air) I usually use the type calculated, then i set the initial fields of p_rgh with the utility setFields (where you define p_rgh as the hydrostatic pressure at the bottom, for example, for the water level 1m, p_rgh=10000). After setting the fields with setFields i change the type calculated in the initial conditions to fixedValue. I do the same for the alpha1 fields. I my case it works pretty well. 
re
sorry max and benji
to use fixedvalue, your geometry should be adjusted to locate free surface z=0. It is troublesome work. instead of that I tried to use totalpressure as Muller mentioned above. I split outlet patch because of fixed elevation. outlet_water { type totalPressure; p0 uniform 2943; U U; phi phi; rho rho; psi none; gamma 1; value uniform 0; } and p0 is calculated as water depth * rho * g (in my case, water depth is 0.3m) i checked it worked well. but I think Muller's approach is more clear. 
Thanks for your replies!
@matejmuller: I don't understand completely how you exactly do that. Please correct me if I'm wrong: 1. with p_rgh at the outlet set to "calculated", you use setFields (but without actually starting the calculation) similar to this (so p_rgh is the same in the whole system, =1000 but just in the bottom cells): Code:
boxToCell @wes1204: How do you define the other parameter for outlet_water? and what does your other outlet look like? Because if I set a value for p0 in outlet_water, I get a flux in the opposite direction :( 
The utility setFields only prescribes the initial values of the variables. When you change the boundary type calculated to fixedValue, you fix those values on the outlet boundary that setFields automatically prescribed. Don't bother with the dynamic pressure, the whole idea of p_rgh is that you don't have to define it, the solver calculates it from the velocities.
1. set boundary type on the outlet boundary patch of p_rgh to calculated outlet { type calculated; } 2. use setFields to prescribe the INITIAL VALUES of p_rgh in the internal field and on the boundaries (set the box coordinates in the file setFields only for the area with water) For example if you have a channel with horizontal dimensions 10x1 m and with the initial water level 0,5m : boxToCell { box (0 0 0) (10 1 0.5); fieldValues ( volScalarFieldValue p_rgh 5000 ); } 3. run setFields 4. change the boundary type calculated on the outlet boundary to fixedValue (you will see, that the setFields utility has prescribed the p_rgh values 5000 on the outlet boundary on every cell face that lies inside your box from setFields). outlet { type fixedValue; value nonuniform List<scalar> 1500 //number of cell faces// ( 5000 5000 5000 . . . ); 5. Do the same for alpha1 6. start simulation matej 
Hey matej, thanks a lot for your help!
I think I got it now, finally ;) So far, the results seem to make sense, although I get problems with my courantnumber pretty frequently now... Thanks again, Benji 
Hey,
I played with groovyBC and I basically did the same thing: p_rgh: Quote:
Quote:
So I have the solution to hold the water level at the outlet but the calculation is not working anyway. But my calculation fails after a few seconds when a small wave hits the outlet boundary. :( Does anyone know a solution for that problem? Thx  Max 
I have a similar problem, it doesn't matter whether I use groovyBC or not, after a few seconds the calculation fails :(
And there is something I don't understand: Why is p_rgh = hydrostatic pressure in this case? (It does not make sense, looking at the equation and the fact that hydrostatic pressure would not be constant over height....) Thanks for the help! 
p_rgh is not the hydrostatic pressure, it's the openfoams way to simplify things. p_rgh=prgh (where the g component is negative). You'll find a better explanation under this link (see drawing):
http://www.cfdonline.com/Forums/ope...rgh17a.html This method with the calculated boundary type always worked for me...maybe there is an error elsewhere (mesh, patches, time step..?). best regards, matej 
Thanks matej again for the reply!
Yes I figured the p_rgh and it also works, more or less... I set the outlet water level to z=0 which worked well for a rectangular channel. If I take a trapezeshaped channel with the same BC's and the calculation stops after ~40 seconds and I get some weird and really high velocities at the inlet, does anyone have an idea why this could be? I guess it might have to do sth with the now nonorthogonal cell shapes... 
I know this tread is a little old, but matej, what type of boundary condition do you use for U at the outlet when you fix alpha and p_rgh? I have tried zeroGradient, inletOutlet and pressureInletOutletVelocity, without much success. Just wondering what has worked for you.

InterFoam fixed height outlet approach
Hey,
I have found a solution that is working for me, very similar to the ones described here. It is capable of gently ensure a water level but still absorbs some surface waves. 1) Outlet is divided in 2 patches: outlet_top (air), outlet_bottom (water); 2) Outlet_top is all zeroGradient (U, alpha.water, p_rgh); 3) Outlet_bottom:
It works and also is quite nice to let go all the surface waves. BUT: it explodes if the water surface level goes below the top of the outlet_bottom patch; so... I set the max Z of the outlet_bottom patch always some cells bellow the desired WSL and, sometimes, I also increase a little bit the initial value of P_RGH_OUTLET; CONCLUSION:  it is a solution with a strong discontinuity (2 different patches) although the zeroGradient helps to smooth it;  it may fail suddenly;  maybe a U limiter/smoother could be applied to prevent those very high velocities when the water surface drops too much;  i guess it lacks a calculation of the dynamic pressure; Does any one tried something similar? Does anyone knows another solution that works (probably much better)? Cheers, Lourenço 
All times are GMT 4. The time now is 18:04. 