-
Notifications
You must be signed in to change notification settings - Fork 43
NinjaFoam Support
Natalie Wagenbrenner edited this page Aug 21, 2015
·
14 revisions
2.2.0 ✅
2.3.0 ✅
2.2.0
There is some issue with simpleFoam
when refineWallLayer
is used. The solver starts normally, but then diverges for some unapparent reason. Simulations run normally if refineWallLayer
is not used.
2.3.1 🔴
Several iterations into the simpleFoam
solver the following error occurs (sometimes):
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigFpe::sigHandler(int) at ??:?
#2 in "/lib/x86_64-linux-gnu/libc.so.6"
#3 double Foam::sumProd<double>(Foam::UList<double> const&, Foam::UList<double> const&) at ??:?
#4 Foam::PCG::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:?
#5 Foam::GAMGSolver::solveCoarsestLevel(Foam::Field<double>&, Foam::Field<double> const&) const at ??:?
#6 Foam::GAMGSolver::Vcycle(Foam::PtrList<Foam::lduMatrix::smoother> const&, Foam::Field<double>&, Foam::Field<double> const&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::PtrList<Foam::Field<double> >&, Foam::PtrList<Foam::Field<double> >&, unsigned char) const at ??:?
#7 Foam::GAMGSolver::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:?
#8 Foam::fvMatrix<double>::solveSegregated(Foam::dictionary const&) at ??:?
#9 Foam::fvMatrix<double>::solve(Foam::dictionary const&) at ??:?
#10
at ??:?
#11
at ??:?
#12 __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6"
#13
at ??:?
Floating point exception (core dumped)
Also exhibits the same divergence issue as 2.2.0.
2.4.0 🔴
There was a change in refineWallLayer.C
. See here for changes and new usage.
If building Paraview, you might need to first turn off CUDA support:
cd $WM_THIRD_PARTY_DIR
sed -i -e 's=CUDA_FOUND=OFF=g' ParaView-4.1.0/Plugins/SciberQuestToolKit/SciberQuest/CMakeLists.txt
2.1.1 ⚪
2.2.0 ⚪
2.2.1 ⚪
2.2.2 ✅
2.3.0 ✅
2.3.1 🔴
It is unclear when exactly the foam-apt-fix branch is needed. I cannot recreate the issue any more. I will investigate further.