- **OpenFOAM**
(*http://www.cfd-online.com/Forums/openfoam/*)

- - **Small time step in interFoam**
(*http://www.cfd-online.com/Forums/openfoam/88429-small-time-step-interfoam.html*)

Small time step in interFoamHi all,
i have a question regarding the interFoam solver. Why the alpha equation is solved explicit? From alphaEqn.H we have: Code:
` for (int aCorr=0; aCorr<nAlphaCorr; aCorr++)` I'm running simulation of water and air in a microchannel (200micron long and 50 micron wide, 2 dimensional): the time step is very small (not higher than 1e-7 s) and the simulation takes a very long time. I also found very high velocities (spurious) at the interface. I'm able to reduce these velocities by reducing the Courant number but the simulation time increase more (i'm using adjustable time step). My question is: using an implcit MULES to solve the alpha equation (for expample is used in interPhaseChangeFoam) would not be better? Normally using an implicit solver allows you to have fewer restrictions on the time step, so why in interFoam an explicit is used? From my experience, simulations at the scale of millimeters do not give this kind of problem and the time step is well described by the CourantNumer's formula and i dont understand why decreasing the dimension should mean decrease the time step. Thanks andrea |

Ciao Andrea,
regarding the first part of your question I really don't know why MULES is solved explicitly in interfoam unlike in interPhaseChangeFoam...but you can change it to implicitly if you want and recompile the code :) @ 2nd part of your question: dt=Courant*dx/U according to this small dx decreases your time step Hope I could help you somehow, |

Hi Sabin,
thanks for reply. I tried to implement MULES::implicit following this http://www.cfd-online.com/Forums/ope...ensions-2.html. Unfortunately the results are not better, at least for my case. Of course if dx is small dt has to be small, but also the velocity has to be smaller. The point is that i injected the fluid from one side of my microchannel at U=1e-4 m/s and the velocities that i find at the interface are from 0.05 up 0.8 m/s!!...this is completely non-physical!! I known about the parasite currents but 4 order of magnitude higher than the inlet velocity, in my opinion, are too big. Increasing the dimension of the domain (from microns to millimiters) i also found some "not true" velocities at the interface but non more higher than 1 order of magnitude of the inlet velocity, and the results seem to be ok. So if someone else has experience with very small channel, i'm interesting to know how to solve problem (or at least limit) of these high velocities at the interface. Thanks andrea |

Hi,
are you starting your simulations from some already converged initial values or have you just created your case? Because if you start from some "bad" initial values I would recommand you to increase your velocity at the inlet little by little, the same trick for the turbulence model (if used). Regards, |

Hi,
Basically i start my simulation with a flat interface. On the wall i have fix contact angle, so in the first time steps the interface moves to the right position with some oscillation. Found very high velocity during this sort of relaxation i guess that is normal due to the inertial term, the problem is that the velocity remains big "until eternity" and with the correct contact angle, non only at beginning of the simulation. But of course i can try your suggestion. In that case how can i specify different velocity for different time step? How can i increase the velocity little by little?...i have fix value boundary condition at the inlet for U. Thanks andrea |

Hello,
so the easiest way is described by alberto on his home page: http://albertopassalacqua.com/?p=69 or you could use the groovyBC: http://openfoamwiki.net/index.php/Contrib_groovyBC I personaly prefer for this simple case "timeVaryingUniformFixedValue" as alberto explains it ;) Ciao, fammi sapere se funziona ;) |

Ciao,
The unsteady boundary condition works fine, unfortunately even this does not solve the problem. Here part of my log file: Code:
`MULES: Solving for alpha1` Regards andrea |

Hi,
try to switch from fvSolution > PISO > momentumPredictor yes; to no. Bye |

2 Attachment(s)
Hi,
that is not the solution. Again the time step is of the order of 1e-7s. I leave the simulation running all the night and after 54000s of "real" time of simulation, the simulated time is 0.04s. :( The velocity at the interface is again too big. See the attached picture. Regards andrea |

Dear Andrea,
All of those stories are about parasitic current which originally comes from the oscillation of curvature (or surface force). As my experience, reduce Courant number (till 0.1) and use smooth function for alpha1 can solve a bit. Regards, Duong |

Hi Duong,
I agree with you, i'm using a smooth function for alpha and my Co is 0.2. If i set Co=0.005 i'm able to reduce these velocities but the time step falls down to 1e-9/1e-10 s. Is the first time since i'm using OF that i have to work with such small domain dimension and the standard techniques to reduce spurious currents do not seem to work for this case. Problably would be interesting try to implement a new curvature calculation following other approaches (there are a lot of literature about that). Regards andrea |

Hi,
There is a thread on parasitic currents: http://www.cfd-online.com/Forums/ope...-currents.html This worked for some. Maybe it will work for you too. Pei |

Andrea, I've been struggling with this same problem from I started to use interFoam
http://www.cfd-online.com/Forums/ope...interfoam.html http://www.cfd-online.com/Forums/ope...-solver-6.html #113 I'd suggest you to run first with c_alpha=0, and div schemes like this divSchemes { div(rho*phi,U) Gauss upwind; div(phi,alpha) Gauss vanLeer; div(phirb,alpha) Gauss interfaceCompression; } so, in this way you won't have influence of the nonlinear part in the advection equation and the sharpness of the free surface will be assured only by the vanLeer scheme. As you showed in #1 when c_alpha <> 0 it influences phiAlpha and then rhoPhi. Finally even when alpha is smooth, if rhoPhi is noisy it will affect in momentum equation via convective term. The other way is to retain c_alpha <> 0 and try to go up with nAlphaCorr. Increasing this parameter should improve the solution of nonlinear advection equation via a fixed point iteration in alpha, but I'm not quite sure about the improvement of this method. I did some tests in 1D phase advection and the rule in not clear for me. Hope this could help you (and me). Regards. |

Hi Santiago,
I'm glad to hear that I'm not the only one with this kind of problems!! I tried to run my simulation using upwind and c_alpha=0 (and 3 nAlphaCorr). The simualtion is quite faster (delta t of the order of 1e-6 s) and also the velocities are smaller, but the interface is too diffuse (15-20 cells instead of 2-3). Using only the VanLeer scheme is not sufficient to keep the interface sharp in my opinion, but it seems that these parasite velocities come from the compression term in the alpha equation as you've suggested. I am still pretty confused about how to solve the problem. Regards andrea |

Andrea, glad to hear your parasitic velocities are small. My suggestion was to run with c_alpha=0 and nAlphaCorr=0, since the last one is only needed in case if non-linear term is activated. The other idea is c_alpha <> 0 and nAlphaCorr > 0. In case using c_alpha > 0 is useless the only choice is to change the div(phi,alpha) discretization scheme until have the sharpness you want obtain, one I've tried is gamma (the one from Hrv Thesis).
Regards. |

Hi Santiago,
Nice to learn new things every day! So, you said use Gamma scheme instead of Van Leer and c_alpha=0. Something like this: divSchemes { div(rho*phi,U) Gauss upwind; div(phi,alpha) Gauss Gamma01; div(phirb,alpha) Gauss interfaceCompression; } PISO { momentumPredictor no; nCorrectors 3; nNonOrthogonalCorrectors 1; nAlphaCorr 0; nAlphaSubCycles 2; cAlpha 0; } Regards andrea |

Quote:
- Anton |

Hi all,
sorry for the late response, but i was testing a bit all your advice. I tried different type of smoothing function, different schemes, different values for c_alpha (using zero is not the solution as suggested by akidess) and i also tried to add the density in the surface force calculation. For all cases i have not seen a great reduction of these spurious current (at most a factor of 1.2/1.5...). I have also read some literature and i have 2 questions for you: 1)the current curvature calculation is implemented over a 5 points stencil or 9 points stencil? (the normal vector is calculated at the cell faces from the interpolated gradient, so i think they are 5 points...values of alpha1 in cells (i,j) (i+1,j), (i-1,j), (i,j+1), (i,j-1) for an orthogonal mesh...but please correct me if i'm wrong) 2) The second question concerns this paper: "A balanced-force algorithm for continuous and sharp interfacial surface tension models within a volume tracking framework" (Francois et al. 2006, Journal of Computational Physics 213 (2006) 141–173), in which basically they say to reduce the spurious current until 10^(-18)/10^(-20) using a balance force algorithm. Does anyone of you have experience of that? would be difficult to implement in OF (hard question probably...)? thanks andrea |

Andrea !
I wonder if you finally made to run your model, I am dealing the sam problem how have you solved your problem ? |

HI Farhad,
well, actually i didn't solve the problem. Let's say that i am trying to live with it. The problem is worse if you work with small capillary numbers or very small grid cells. Smooth the color function in the curvature calculation helps a bit but it doesn't eliminate the problem. I suggest you to read this thread http://www.cfd-online.com/Forums/ope...-currents.html in which, based on the work done by Ali Q Raeini et al., a new version of interFoam has been proposed. At the moment i think it works just for the static case and not for dynamic. I don't know if someone has adavaced in the meantime. Maybe akidess could add his comments on that. good luck andrea |

All times are GMT -4. The time now is 16:20. |