Thanks a lot. I wonder if the partial elimination algorithm mentioned in Passalaqcua's paper was implemented in the current version?
kimy
帖子
-
The current version of twophaseeulerfoam -
The current version of twophaseeulerfoam@李东岳 yes. but I found some authors already refer the following paper with respect to current twophaseeulerfoam.
such as
-
The current version of twophaseeulerfoamThank 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 twophaseeulerfoamHi 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.
-
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.
-
source term only in boundary cell.Already solved.
-
bluecfdHello. 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 non-zero value in Uw means the wall cell index. But the order in patchArea needs to be modified
-
New scalar in phaseModel.c@bestucan Thanks for your attention.
-
New scalar in phaseModel.cI have already reached my goal in another way. Thanks for all helps.
-
New scalar in phaseModel.cThis is the solver file of openfoam_v1906
-
New scalar in phaseModel.c@bestucan Thanks a lot. What you mean is that you did not meet any problem in your OpenFOAM version? Could you please upload the whole modified solver files here (twophaseeulerfoam)? The files I uploaed above was copied from blueCFD (maybe openfoam 5). Additionally, I am also using HPC where openfoam-v1906 is loaded.
-
New scalar in phaseModel.c -
New scalar in phaseModel.c@bestucan Thanks. Your suggestions are very helpful. However, the solver met the same error mentioned before. I uploaded my solver and case files. Hope you can see them if you wish (I cannot upload). I modified the solver based on twophaseeulerfoam.
-
New scalar in phaseModel.cSelecting default blending method: none Selecting dragModel for (solids in water): SchillerNaumann Selecting swarmCorrection for (solids in water): none #0 Foam::error::printStack(Foam::Ostream&) at ??:? #1 Foam::sigSegv::sigHandler(int) at ??:? #2 ? in /lib64/libc.so.6 #3 ? at ??:? #4 __libc_start_main in /lib64/libc.so.6 #5 ? at ??:? Segmentation fault (core dumped)
-
New scalar in phaseModel.c@bestucan I am a little bit crazy because my files are totally same as yours.......Still error after run. Note that I did not change the default library into user's library (All of them I leave it as defualt "LIB = $(FOAM_LIBBIN)/liblibcompressibleTwoPhaseSystem"
). -
New scalar in phaseModel.c@bestucan Many thanks. The same error occurs, same as original when I run my case.
Could you please upload your phaseModel.C and H files here? -
New scalar in phaseModel.c@bestucan But why alphaMax() was originally defined in the phaseModel.H without any error?
scalar alphaMax() const { return alphaMax_; }
After I defined only scalar myBeta() in phaseModel.H, the following error occurs:
In file included from phaseModel/phaseModel.C:26:0: phaseModel/phaseModel.H:158:29: error: invalid declarator before 'd' tmp<volScalarField> d() const; ^ phaseModel/phaseModel.H:162:26: error: non-member function 'const Foam::PhaseCompressibleTurbulenceModel<Foam::phaseModel>& Foam::turbulence()' cannot have cv-qualifier turbulence() const;
-
New scalar in phaseModel.c@bestucan Many Thanks. I have a confusion that you defined the following two scalar and function in phaseModel.H
< scalar myBeta_; 195,196d193 < < scalar myBeta() const;
While in original file, according to the definition of alphaMax
scalar myBeta() const { return myBeta_; }
and you put this code in phaseModel.C ?
/home/can/.local/share/OpenFOAM/OpenFOAM-8/applications/solvers/multiphase/multiphaseEulerFoam/phaseSystems/phaseModel/phaseModel/phaseModel.C 88,89c88 < alphaMax_(fluid.subDict(phaseName).lookupOrDefault("alphaMax", 1.0)), < myBeta_(fluid.subDict(phaseName).lookupOrDefault("myBeta", 1.0)) --- > alphaMax_(fluid.subDict(phaseName).lookupOrDefault("alphaMax", 1.0)) 143,147d141 < } < < Foam::scalar Foam::phaseModel::myBeta() const < { < retu