|
[Sponsors] |
laplacian fvm method "not Implemented" for modified interDyMFoam |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
June 20, 2019, 05:40 |
laplacian fvm method "not Implemented" for modified interDyMFoam
|
#1 |
New Member
Fabian Krieg
Join Date: Jun 2019
Posts: 2
Rep Power: 0 |
Hello all,
I'm trying to build the immersed boundary method from pimpleDyMIbFoam into the two phase solver interDyMFoam with foam-extend-4.1. I have changed all the needed headers and variablenames by comparing the structure of the solvers. Running the solver on the damBreak tutorial with a moving block(modelled as IB-object) inside I get the error (all the gdb variables at error-time are in the appended file): Code:
--> FOAM FATAL ERROR: Not implemented From function immersedBoundary::gradientInternalCoeffs() in file /opt/foam/foam-extend-4.1/src/finiteVolume/lnInclude/fvPatchField.H at line 473. FOAM aborting Code:
fvm::laplacian(rUAf, pcorr) == fvc::div(phi) another question, maybe same problem: what is the difference of rAUf and rUAf? Because they are used the same way in interDyMFoam and pimpleDyMIbFoam, but have different names. Do they mean the same and have the same dimensions? I read about rAUf of beeing the main diagonal elements of U, then inverted and interpolated. As later defined in pEqn.H: Code:
volScalarField rAU = 1.0/UEqn.A(); surfaceScalarField rUAf = fvc::interpolate(rAU) Some interesting effect besides, deleting all headers acessing the correctPhi.H header, pressure p and pd are calculated in the whole area, the IB-block deadCells of IB-method are calculated correctly, but velocity is only calculated in one phase. And Alpha values are not calculated. Thanks in advance for your answers! Best regards Fabian |
|
June 26, 2019, 18:36 |
Unkown case in MULES?
|
#2 |
New Member
Fabian Krieg
Join Date: Jun 2019
Posts: 2
Rep Power: 0 |
After some work it proved, that the nonOrthogonal Corrections in the pimple-Loop are problematic. If I removed them (in correctPhi.H-File) then the velocity-Field of the modified damBreak-Tutorial(interDyMFoam with IB) was calculated (for an orthogonal Mesh). So the error must be a tricky problem in the nonOrthogonal-Correction, unfortunately I couldn't find it:/ But by now the p- and U-Field are calculated correctly for orthogonal meshes and IB object is recognized correctly. So only the alpha isn't calculated.
Not further caring about the removed nonOrthogonalCorrection, I continued my work to add the IB method to the interDyMFoam solver. Running the modified solver(interDyMFoam with IB from pimpleDyMIbFoam) on my modified damBreak Tutorial, a new error occured: Code:
PIMPLE: iteration 1 MULES: Solving for alpha1 --> FOAM FATAL ERROR: incompatible fields Field<scalar> f1(240), Field<scalar> f2(0) and Field<scalar> f3(240) for operation f1 = f2 * f3 From function checkFields(const UList<Type1>&, const UList<Type2>&, const UList<Type3>&, const char*) in file /opt/foam/foam-extend-4.1/src/foam/lnInclude/FieldM.H at line 84. FOAM aborting Code:
phiPsi = phiBD + lambda*phiCorr; Another idea I had is that the interDyMFoam solver with IB doesn't distinguish correctly between the IB and ordinary Mesh. Because the dimension in the error message above f3(240) is the same as the number of IB-Cells (nIbCells: 240). I don't know how to solve this problem that is maybe an unknown case to MULES and I would be really happy if someone has an idea about how to solve that problem. Thanks in advance! Best regards Fabian |
|
Tags |
correctphi, interdymfoam, laplacian, rauf, ruaf |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Level set method in FVM | RakeshRR | Main CFD Forum | 0 | July 28, 2017 11:08 |
About the accuracy of DNS with spectral method and FVM method | huangxianbei | Main CFD Forum | 6 | May 25, 2014 12:25 |
FVM density based implicit method? | ANikzad | Main CFD Forum | 2 | May 24, 2014 09:18 |
comments on FDM, FEM, FVM, SM, SEM, DSEM, BEM | kenn | Main CFD Forum | 2 | July 18, 2004 19:28 |
hess-smith method and fvm method | yangqing | FLUENT | 0 | March 20, 2002 20:25 |