Thanks a lot. I wonder if the partial elimination algorithm mentioned in Passalaqcua's paper was implemented in the current version?
kimy
@kimy
Best posts made by kimy
Latest posts made by kimy

RE: The current version of twophaseeulerfoam

RE: The current version of twophaseeulerfoam
@李东岳 yes. but I found some authors already refer the following paper with respect to current twophaseeulerfoam.
such as

RE: The current version of twophaseeulerfoam
Thank you a lot. But I cannot find the document regarding Henry Weller but only Rusche.
So the solution algorithm of Passalacqua is not yet implemented in the current OPENFOAM? 
The current version of twophaseeulerfoam
Hi everyone, I would like to know the current version of twophaseeulerfoam is based on which researcher's algorithm?Alberto Passalacqua or Henrc Rusche? Thnak you.

RE: The influence of mesh on solution?
Thanks. I created two meshes with the same body size but different type of meshes,namely structured and unstructured, the results are different. Note that both of two cases are grid independent. Do you have any idea about that ? since I saw a thread you opened in cfd online.

The influence of mesh on solution?
Hi guys,
Do you have any idea about the influence of inflation layer and structured/unstructured mesh? I found there is some effect of those on the final solution, based on the calculation with the whole same settings, excepting the mesh.
The above figure shows the axial velocity of pipe bend exit. The black lines and blue lines represent unstructured and structured mesh respectively. Clearly, different shape can be observed.
Also I compared the results with different inflation layers setting. All of them have the same first layer thickness and body size. I only changed the number of layers or growth ratio.

RE: bluecfd
Hello. I usually use BlueCFD on windows. It is really convenient and easy, compared with linux. In fact, they are nearly the same rules. You can compile and create your own solver. But you should note that there are some codes are not consistent, compared with those of linux version.

source term only in boundary cell.
Hi guys,
I defined a Uw which has the same size of the total cell numbers to save the velocity only in the boundary cell. Due to the fact that the source term I need to use is Uw times the area of corresponding wall. Thus, I defined a patchArea (patchArea[faceI] = mesh.magSf().boundaryField()[patchID][faceI];) used to save that area. Note that the size of patchArea is also same as Uw, however the index is not corresponding to each other. Is there a way to rearrange the order of patchArea, to make the index consistent with Uw? I uploaded a output log file here, as you can see, the index with a nonzero value in Uw means the wall cell index. But the order in patchArea needs to be modified