[Owais Shabbir]

Hi All,


I was trying to mesh two bodies over which the air will flow externally bounded by a box defined in blockMeshDict.

While meshing after the 2nd iteration of the surface refinement it shows the following error: (remaining error included in the photos)


Foam::error:rintStack(Foam::Ostream&) [1] ...[3] ...[3]... addr2line failed


Further Details: I have also run this with single processor and it just crashes down.

I have seen this problem on the community forum page describing it as bad maths and it is always linked to the solver not the snappyHexMesh. I would highly appreciate it if anyone could explain me why this error is generated and how to tackle this problem.

Thanks

[Owais Shabbir]

Here is the blockMesh and SnappyHexMeshDict files.


If anyone could look into it, it will be a massive help.



Thanks again

[Akanksha90]

Hi,
I also have similar issue and the funny Thing is with the same Setting on one Computer the SHM runs and meshes , whereas in other Computer that gives me this error " add2rline".

Have u found any solution yet?

[Owais Shabbir]

Hi,


I have not found any solution to it. But my meshing works if I use lower values of refinementSurfaces level in SHM.

if I keep mine at any value above (3 3), I get this error.

I think it is because of the computers low computational power because my geometry is quite complicated. I don't have access to any strong computer so I continue with the above mentioned values.

Hope this helps


OS

[Owais Shabbir]

Hi Akanksha,


BTW which OpenFoam version are you using on both PCs?

[Akanksha90]

Hi Owais,

Thank you for your Response. I am using V1812.

Well i understand what you mean by decreasing the refinement Level. It does make sense, when we have a finer blockMesh.
could you please tell me, how fine did you mesh your block?

Please correct me If I am wrong on this part - Our geometry mesh cell size are dependent upon the cell size of the block. So we Need to make a fine mesh with block first and then use the snappyhexdict for further refinement on surfaces or regions?

I am new with snappyhex and still in the understanding Phase.

[Owais Shabbir]

Hi,


I used (60 60 50) with simpleGrading (1 1 1).


I have even tried with (200 200 200) as well but didn't work.



I will give it a try with (5000 5000 5000) and see if it is the case.



Yesterday, I asked a colleague to run it on the cluster. And the problem was still there, so as i said before it might be the computational power that is missing its for sure not the case.



I even simplified my geometry to the maximum I could but still the same error showed up.



Best Regards
OS

[Akanksha90]

Hi Owais,

I read somewhere, that addr2line error can also come when the binutils dev package is not updated. I have to try it and then i can be sure.
Because in my Computer with less cores the meshing works but with the same Setting the mesh does not run on the other Computer which is not connected to the Internet.

Could be possible, due to some packages which are outdated.

[Owais Shabbir]

Hi,


So i gave a shot with 500 500 500 BMDict and it gave and error of

'It could be due to a stack violation caused by e.g. bad use of pointers or an out of date shared library'



So may be you are heading in the right direction.
P.S. I am using OF6

[Owais Shabbir]

Hi,

Good news. So i tried a different method this time. Before I used to follow the following commands:

blockMesh
surfaceFeatureExtract
decomposePar
mpirun -np 4 snappyHexMesh -overwrite -parallel > log.shm
reconstructParMesh -constant

But this time I made a change:
a) I turned on implicitFeatureSnap from SHM and the rest of them false.
> I did this because I learnt it is good when you don't have curvy features and geometry is easy to capture by it and works from my geometry.
>This helps and surfaceFeatureExtract cmd is not required anymore.

With this I have less number of bad cells from checkMesh but i wonder is it because I increased refinement or I used the implicitFeatureSnap option.

Best Regards,

OS