[unilord]

Hey everyone.

I am simulating a transient analysis of a centrifugal pump using the sliding mesh approach (dynamic mesh) for my masters thesis. I am using the results of a steady state analysis as initial conditions for this transient simulation. I ran around 0.46 seconds (4.7 rotations of the impeller) and I am facing an issue when postprocessing the data in paraview.


First of all, I have this error when I firstly open the paraview:

 ERROR: In vtkOpenFOAMReader.cxx, line 8816
vtkOpenFOAMReaderPrivate (0x634e420): Number of cells/points in mesh and field do not match: mesh = 0, field = 13952 in Up, li { white-space: pre-wrap; }

Second, I have not an interpolated result for the velocity. Only the results in the centroids.

I believe this is due to the fact that I am using a sliding mesh. If anyone has any idea of why this might be happening, I would be truly grateful. I believe it has to do with the fact that I am using a dynamic mesh.

Best Regards,
Pedro Gouveia

[bravecaveman777]

Originally Posted by aghora17

found the solution into some Allrun files.



you just need to run: snappyHexMesh -overwrite and it will take care of the problem.

It works, very thanks!

[ExtRas]

Dear foamers,

I got the same problem with the impeller tutorial of Openfoam 11 (.org). Mesh = 0, field = 320.

I prepared another case with a similar type of simulation (sliding mesh of a sixth of a fan, cyclic and NCC) and I got the same issue too.

The case is similar to the one presented by Pedro / Unilord two posts above.


Is it a bug ? Is there a workaround because it is quite annoying?

Best regards

Marc

PS: Ok it seams to have more answers here : Error in paraview results postprocessing regarding sliding mesh

[unilord]

Originally Posted by ExtRas

Dear foamers,

I got the same problem with the impeller tutorial of Openfoam 11 (.org). Mesh = 0, field = 320.

I prepared another case with a similar type of simulation (sliding mesh of a sixth of a fan, cyclic and NCC) and I got the same issue too.

The case is similar to the one presented by Pedro / Unilord two posts above.


Is it a bug ? Is there a workaround because it is quite annoying?

Best regards

Marc

PS: Ok it seams to have more answers here : Error in paraview results postprocessing regarding sliding mesh

Hey,

Yeah, that is my one man army thread ahahaha. But I did not actually find a solution, just a way to avoid it 😔