[KingKraut]

Dear all,

I have a problem with a custom solver that gives fine results on a mesh of a certain size (~3 Mio cells). When I try to run a simulation on a finer mesh on the same geometry (~6 Mio cells), the solver breaks down at a certain point with the following error message:

#0 Foam::error:rintStack(Foam::Ostream&) at ??:?
#1 Foam::sigFpe::sigHandler(int) at ??:?
#2
at sigaction.c:?
#3 void Foam::divide<Foam::fvPatchField, Foam::Vector<double> >(Foam::FieldField<Foam::fvPatchField, Foam::Vector<double> >&, Foam::FieldField<Foam::fvPatchField, Foam::Vector<double> > const&, Foam::FieldField<Foam::fvPatchField, double> const&) at ??:?
#4 Foam::tmp<Foam::GeometricField<Foam::Vector<double >, Foam::fvPatchField, Foam::volMesh> > Foam:perator/<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>(Foam::tmp<Foam::GeometricField<Foam ::Vector<double>, Foam::fvPatchField, Foam::volMesh> > const&, Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > const&) at ??:?
#5 Foam::simpleFilter:perator()(Foam::tmp<Foam::Geo metricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> > const&) const at ??:?
#6 Foam::incompressible::LESModels::dynamicSmagorinsk y::cD(Foam::GeometricField<Foam::SymmTensor<double >, Foam::fvPatchField, Foam::volMesh> const&) const at ??:?
#7 Foam::incompressible::LESModels::dynamicSmagorinsk y::updateSubGridScaleFields(Foam::GeometricField<F oam::SymmTensor<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
#8 Foam::incompressible::LESModels::dynamicSmagorinsk y::dynamicSmagorinsky(Foam::GeometricField<Foam::V ector<double>, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::transportModel&, Foam::word const&, Foam::word const&) at ??:?
#9 Foam::incompressible::LESModel::adddictionaryConst ructorToTable<Foam::incompressible::LESModels::dyn amicSmagorinsky>::New(Foam::GeometricField<Foam::V ector<double>, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::transportModel&, Foam::word const&) at ??:?
#10 Foam::incompressible::LESModel::New(Foam::Geometri cField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::transportModel&, Foam::word const&) at ??:?
#11 Foam::incompressible::turbulenceModel::addturbulen ceModelConstructorToTable<Foam::incompressible::LE SModel>::NewturbulenceModel(Foam::GeometricField<F oam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::transportModel&, Foam::word const&) at ??:?
#12 Foam::incompressible::turbulenceModel::New(Foam::G eometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::transportModel&, Foam::word const&) at ??:?
#13
at ??:?
#14 __libc_start_main at ??:?
#15
at ??:?

I have attached the both log_files with the error message attached for the larger mesh (log_heapFoam_Intermediate). The smaller case I only attached, to show, that it continues running. I also attached the according checkMesh files for both grids. They both lack a little in the mesh non-orthogonality. But I tackled that with some non-orthogonality correctors in the fvsolution file.

All the other input files (boundary conditions for k, nuSgs, U, p and so on) are completely identical for both cases! From different posts I found in the forum I deduced, that this error can be due to some erroneously chosen BCs (dividing by zero for example). However, since the BCs worked for the smaller grid, I think this should not be the reason? Anyway I played around a little there, too, but to no avail...
(I will attach these in a second post. right now)

I am really stuck here at the moment. Can anybody tell me in which direction I need to look for a fix?
By the way I tried the case with a simpler solver, too. icoFoam and pisoFoam fail, too...

I guess this is an issue with the mesh, which bothers me a lot... It was hard enough to produce this one with ICEM. Maybe there is a possibility to cure this, with some more changes in fvSchemes or vfSolution?

Thanks a lot to anyone looking into this! Any help is highly appreciated.
I hope I did not miss out any information. If so, please let me know!

Thanks a lot!

Johannes